When both CC1 and CC2 pins are simultaneously pulled up, it often leads
to the double Rp to Vbus cable being stuck in the SNK_ATTACH_WAIT state.
And the state machine fails to transition to the SNK_ATTACHED state.
Therefore, it is recommended to focus on transitioning the sink port to
the SNK_DEBOUNCED state instead. By doing so, the desired outcome can be
achieved more effectively.
[ 134.525750] VBUS on
[ 134.713240] CC1: 0 -> 3, CC2: 0 -> 3 [state TOGGLING, polarity 0, connected]
[ 134.713249] state change TOGGLING -> SNK_ATTACH_WAIT [rev3 NONE_AMS]
Change-Id: Ib21f4f0322a193678a5f22007a515b3b19772b40
Signed-off-by: Michael Wu <michael@allwinnertech.com>
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
Link: https://lore.kernel.org/linux-usb/20240312011300.75081-1-michael@allwinnertech.com/
The USB Type-C Cable and Connector Specification defines the wire
connections for the USB Type-C to USB 2.0 Standard-A cable assembly
(Release 2.2, Chapter 3.5.2).
The Notes says that Pin A5 (CC) of the USB Type-C plug shall be connected
to Vbus through a resister Rp.
However, there is a large amount of such double Rp connected to Vbus
non-standard cables which produced by UGREEN circulating on the market, and
it can affects the normal operations of the state machine easily,
especially to CC1 and CC2 be pulled up at the same time.
In fact, we can regard those cables as sink to avoid abnormal state.
Message as follow:
[ 58.900212] VBUS on
[ 59.265433] CC1: 0 -> 3, CC2: 0 -> 3 [state TOGGLING, polarity 0, connected]
[ 62.623308] CC1: 3 -> 0, CC2: 3 -> 0 [state TOGGLING, polarity 0, disconnected]
[ 62.625006] VBUS off
[ 62.625012] VBUS VSAFE0V
Change-Id: I415db22b0012ace9535039bc4c8e5ec113482e33
Signed-off-by: Michael Wu <michael@allwinnertech.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Link: https://lore.kernel.org/r/20230920063030.66312-1-michael@allwinnertech.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
(cherry picked from commit dbc1defec1aa7d8d80da3ea9e3ddafbcfca8f822)
This function is mainly used for ultra suspend mode, which wakes up the
system through the VDC interrupt of the PMIC by plugging in the charger.
Signed-off-by: shengfei Xu <xsf@rock-chips.com>
Change-Id: I9c5ab1aeb067f4d0290f9a153675c3b4b5887920
1.support set output range by user
2.fix csc process color space and range config
3.add adobe YUV/RGB and 2020 YUV/RGB support
Signed-off-by: Jianwei Fan <jianwei.fan@rock-chips.com>
Change-Id: I02ce6ae17c94f51b44d5b6096e1185e1fbb3e3e9
In upstream patch, runtime pm is used to avoid excessive unprepare/
prepare.
However, some DSI panels need to be powered off and on again before
reloading the initialization sequence. If set the auto_suspend and
delay time is set to 1s, the suspend/resume callback function cannot
be entered when sleeping/waking up quickly, the power of panel cannot
be restarted, causing this timing to be abnormal and causing the panel
to not work properly.
In kernel 5.10, pm_runtime has not been used in panel-simple, but it
still runs stably in panel applications. Considering the above
reasons, we chose to revert the submission of pm_runtime upstream.
Type: Fix
Redmine ID: 460825 468692
Associated modifications:
commit 3235b0f20a ("drm/panel: panel-simple: Use runtime pm to
avoid excessive unprepare / prepare")
Test: N/A
Signed-off-by: Zhibin Huang <zhibin.huang@rock-chips.com>
Change-Id: I348e1a860e528cf4bee7ce76de0ea13c18fddd90
This adds more step prints make easy to debug.
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
Change-Id: Icf48b7d9e0d254db2fc75d3fdf713f901549e0e9
when register 2 platform device use the same device node,
they will request the some pinctrl resource and cause
conflict. Don't use the same device node th register device
can avoid this issue.
Change-Id: I0a97bf50b80801ad09035554f2438c1c21580c1a
Signed-off-by: Zhang Yubing <yubing.zhang@rock-chips.com>
In DP spec 1.3, Condition of CR fail are outlined
in section 3.5.1.2.2.1, figure 3-20:
1. Maximum Voltage Swing reached
2. Same Voltage five times
The following conditions have been optimized:
1. Training of CDR still failed while maximum voltage swing has been applied and configured
2.Removed the redundant judgment for the maximum pre-emphasis level reached
Change-Id: I829437e0294663a6cb1f31feb91e1d6a468ed681
Signed-off-by: Guochun Huang <hero.huang@rock-chips.com>
