Update TRAINING_PATTERN_SET then TRAINING_LANEx_SET in the
Clock Recovery phase of link training as this is the sequence
mandated in the display port specification.
CRs-Fixed: 1076516
Change-Id: I7aa157d9377799563180792fe5d31a22a7aff0e1
Signed-off-by: Tatenda Chipeperekwa <tatendac@codeaurora.org>
It is recommended to ensure that the interface timing engine is on
when configuring the hardware to switch to "IDLE pattern" state
as part of the shutdown sequence. In addition, it is also preferred
to issue a global software reset of the controller to ensure that
it's state machine is reset for any subsequent connections.
This updated sequence fixes link training failures seen during
multiple connect/disconnect use-cases.
Change-Id: I1984c1fc8c3e4a5f9c818240ec7e0323a68bfe3b
Signed-off-by: Chandan Uddaraju <chandanu@codeaurora.org>
Some sinks expect configure command before notifying hpd
as high in status or attention command. Do not wait for
hpd to go high to send configure command to sink. Once the
configure command has been sent to sink, sink may send attention
command back to source with hpd high. Configure source power on
if attention command is received with hpd high.
Change-Id: Ic5254da65f3720a8313881bc419ec912a0ed6997
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
In some cases with IPA3 received qmi_service_exit from
modem but still uses invalid qmi-handler to send QMI-msg
to modem which leads to crash. The fix is to add the
check before sending QMI msg to modem.
Change-Id: Iac48747a188b234cc640285e181984985fc3c012
Signed-off-by: Skylar Chang <chiaweic@codeaurora.org>
Add a new property to read the lpg-lut size for the
qpnp-pwm device tree nodes for pmicobalt.
CRs-Fixed: 1060896
Change-Id: I93bf7c406471b5877008e2000260adfa62336b93
Signed-off-by: Devesh Jhunjhunwala <deveshj@codeaurora.org>
Add support to read the qcom,lpg-lut-size property from
the device tree instead of using the value returned by the
of_get_address API.
CRs-Fixed: 1060896
Change-Id: I0f84baf29a141719dd44dabb67e9d599d9646d49
Signed-off-by: Devesh Jhunjhunwala <deveshj@codeaurora.org>
Yue Cao claims that current host rate limiting of challenge ACKS
(RFC 5961) could leak enough information to allow a patient attacker
to hijack TCP sessions. He will soon provide details in an academic
paper.
This patch increases the default limit from 100 to 1000, and adds
some randomization so that the attacker can no longer hijack
sessions without spending a considerable amount of probes.
Based on initial analysis and patch from Linus.
Note that we also have per socket rate limiting, so it is tempting
to remove the host limit in the future.
v2: randomize the count of challenge acks per second, not the period.
Fixes: 282f23c6ee ("tcp: implement RFC 5961 3.2")
Reported-by: Yue Cao <ycao009@ucr.edu>
Signed-off-by: Eric Dumazet <edumazet@google.com>
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yuchung Cheng <ycheng@google.com>
Cc: Neal Cardwell <ncardwell@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Acked-by: Yuchung Cheng <ycheng@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Change-Id: I1bf93d033e788c37899837f0c9e930bc4e20aa4c
Git-repo: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git
Git-commit: 75ff39ccc1bd5d3c455b6822ab09e533c551f758
[d-cagle@codeaurora.org: Resolve trivial merge conflict]
Signed-off-by: Dennis Cagle <d-cagle@codeaurora.org>
