| Age | Commit message (Collapse) | Author |
|---|
|
Original change: https://partner-android-review.googlesource.com/c/kernel/private/devices/google/tangorpro/+/2748032
Change-Id: Id63815e00d209058b64913124fc79d0c6e51d311
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
There are two cases for the HES mistriggered events.
Case #1: H1S state 0 reported during the acc detection
[ 4164.863428] EV:H1S state 1
[ 4164.863633] H1S: accessory detection 0, mfg 0
[ 4164.863637] QUEUE EVENT 3
[ 4164.864567] POGO ACC IRQ triggered
[ 4164.864665] Pogo acc threaded irq running, acc_detect 0
[ 4164.864768] POGO ACC IRQ triggered
[ 4164.864816] Pogo acc threaded irq running, acc_detect 0
[ 4164.864961] POGO ACC IRQ triggered
[ 4164.864999] Pogo acc threaded irq running, acc_detect 1
[ 4164.865002] QUEUE EVENT 4
[ 4164.865082] EV:H1S state 0
[ 4164.865086] EV:ACC_GPIO_ACTIVE
[ 4164.865094] pending state change STANDBY -> STANDBY_ACC_DEBOUNCED @ 20 ms
[ 4164.867384] POGO ACC IRQ triggered
[ 4164.867434] Pogo acc threaded irq running, acc_detect 0
[ 4164.888241] [ 5805] state change STANDBY -> STANDBY_ACC_DEBOUNCED [delayed 20 ms] []
Case #2: H1S stays at 1 during the acc detection
[ 861.585046] EV:H1S state 1
[ 861.586088] POGO ACC IRQ triggered
[ 861.586189] Pogo acc threaded irq running, acc_detect 0
[ 861.586318] POGO ACC IRQ triggered
[ 861.586358] Pogo acc threaded irq running, acc_detect 0
[ 861.586391] POGO ACC IRQ triggered
[ 861.586430] Pogo acc threaded irq running, acc_detect 1
[ 861.586433] QUEUE EVENT 4
[ 861.586571] EV:ACC_GPIO_ACTIVE
[ 861.586584] pending state change STANDBY -> STANDBY_ACC_DEBOUNCED @ 20 ms
[ 861.588522] POGO ACC IRQ triggered
[ 861.588672] Pogo acc threaded irq running, acc_detect 0
[ 861.609863] [ 1063] state change STANDBY -> STANDBY_ACC_DEBOUNCED [delayed 20 ms] []
[ 865.464562] POGO ACC IRQ triggered
[ 865.464805] Pogo acc threaded irq running, acc_detect 1
[ 865.464818] QUEUE EVENT 4
[ 865.465221] EV:ACC_GPIO_ACTIVE
[ 865.465232] pending state change STANDBY_ACC_DEBOUNCED -> STANDBY_ACC_DEBOUNCED @ 20 ms
[ 865.471192] POGO ACC IRQ triggered
[ 865.471393] Pogo acc threaded irq running, acc_detect 0
[ 865.486007] [ 1072] state change STANDBY_ACC_DEBOUNCED -> STANDBY_ACC_DEBOUNCED [delayed 20 ms] []
[ 865.602370] POGO IRQ triggered
[ 865.602636] Pogo threaded irq running, pogo_gpio 0
For Case #1, run acc detaching process when the ACC_GPIO_ACTIVE event is
triggered.
For Case #2, disable acc regulator when the POGO IRQ is triggered (GPIO
active) and continue to normal dock detection.
Bug: 288341638
Change-Id: I6f5c45ff892cec8d59f45eb7694db879f1978361
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
SBMerger: 603054162
Change-Id: I1ff8144076c6fdb5b3aa47c3932af7f35bed286f
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
Bug: 316022384
Change-Id: Ic1afcacf8b14c950c4365d3ec3c6916bde1b714a
Signed-off-by: Victor Liu <victorliu@google.com>
|
|
Bug: 309375239
Change-Id: I84b81aad24768d61ff1a9577e1516be60c3b76c8
Signed-off-by: Jack Wu <wjack@google.com>
|
|
Bug: 306724827
Change-Id: I9aaeb554d0aaf03049972475f777e4d64472da45
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
Bug: 291970096
Test: build pass
Change-Id: I043c312e492962c1f1d6f8a432216cfebd527eb0
Signed-off-by: Rex Lin <rexcylin@google.com>
|
|
Bug: 270454537
Change-Id: I11874ea27a35ba8332bd91871ccd304fe88189df
Signed-off-by: Super Liu <supercjliu@google.com>
|
|
android13-gs-pixel-5.10-udc-qpr1
|
|
Enable hall only detection for EVT2 bezelback and wingboard.
DVT+ will have POR detection enabled.
Bug: 266240364
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
(cherry picked from https://partner-android-review.googlesource.com/q/commit:0d53d53eee2dd4d5d627b74149a8439b6e371b12)
Merged-In: I405838ac2ee9eb4cd23520ed81df4ab6f15386ba
Change-Id: I405838ac2ee9eb4cd23520ed81df4ab6f15386ba
|
|
Bug: 272608122
Change-Id: Id79270056d965acc45d171b36d3c3d505ba3f90e
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
* determine GKI_KERNEL_BRANCH from manifest
Bug: 277560840
Change-Id: I840713717323a6fe5d9427fa1fe368cb06e02b31
Signed-off-by: Robin Peng <robinpeng@google.com>
|
|
Bug: 284790341
Test: TH build pass.
Signed-off-by: Super Liu <supercjliu@google.com>
Change-Id: Iabbb07812ec284c38f4cbab7c047a7e45772376d
|
|
Bug: 277560840
Change-Id: Iac99643c10ebf4582a61cb7616474c436f5a3838
Signed-off-by: Wilson Sung <wilsonsung@google.com>
|
|
Enable it for DVT+
Bug: 250518260
Bug: 250518309
Change-Id: Ic1a9a4c7acde94279166d8517644d2597f3e3b14
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 47656f32716240c5b6fb739eb008435755b322a5)
|
|
This fix is for EVT2 only. When attaching to Pogo accessories while a
USB-C device is attached, data_active is cleared in
switch_to_hub_locked. Set it so that Type-C driver is able to callback
to pogo_transport when the USB-C device is removed.
Bug: 275001979
Change-Id: I62d4196d14a557b1ac3325afe6aef62650831bd5
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 4f13dee6124f082d35c716bf969e179f3fbbc11c)
|
|
For new state machine, While docking, signal docked after setting up
USB data path once the state machine reaches steady state. While
undocking, signal undocked before altering USB data path. This
ensures that userspace can close USB data pipes more gracefully.
Bug: 275150939
Change-Id: Iaa960fda6a68e885d077957b2eaac36e9ca36308
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
(cherry picked from commit 1756748937d7032afa3db27b859441916e7861e9)
|
|
Send KOBJ_CHANGE uevent when pogo_usb_active is updated
for the new state machine.
Bug: 275150939
Change-Id: Id95fd978931a78e446a77d3bcbbacb7f1ca26bd5
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
(cherry picked from commit 4dc9c727e29a483308a7e10b85b650955f721342)
|
|
For now, we only log the first bus suspend event after the lid is
closed.
Bug: 272608122
Change-Id: Id1736320426f06f0da2152672829cf62b36807e9
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit cefc0bae0add9608e3a8006c1167d4f2cc854d95)
|
|
Bug: 259305712
Change-Id: Ie2e6d0634828b009057d588a8b6240fc492b63d1
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 361181a1412706586297e1782c10f84450cf26dd)
|
|
Only enable the accessory detection if the device is not docking on the
audio dock.
Bug: 259305712
Change-Id: I7e9114c2307ef0e185f2e1499f98fb7bda0852d3
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 405fd572add94faab2acf349d747efef6693eb40)
|
|
Bug: 272500774
Change-Id: I585fc0fbd9972dc6a3d0c7b032c1a597a215f082
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 5b2cfba50b449e02b1a5cb90e9340174e89b84b8)
|
|
This feature is for debugging and testing purpose.
Command to enable force_pogo:
echo 1 > /sys/devices/platform/google,pogo/force_pogo
After enabling force_pogo, the docking action while USB-C connecting to
PC causes the data path to switch to pogo. Echo 0 to disable the
feature.
Bug: 272411364
Change-Id: Ie15184d66ffea36de4b005a8edd6ec6f13f6592e
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 29ad738dce7b92ff5525ef150f3824e0a5a8e625)
|
|
DWC3 does not detect the physical disconnection of SuperSpeed USB
accessories while Hub is enabled and Pogo Accessory keeps connected.
Toggle the hub-mux to force disconnecting all the USB devices.
Bug: 271669059
Change-Id: I200742ad7b0b9fb36df7b30f0f262e274b4041d7
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 7d692e4093410ae63bef96ff6e73001abd920633)
|
|
Bug: 250518260
Bug: 250518309
Change-Id: Ia057a13929f4ef6ad291af3545292811083dc3ae
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 1199631a48d79d5e56cf4041181d2ae6c9472330)
|
|
Register the notifier of adding/removing a USB device from the USB core.
Bug: 250518260
Change-Id: Icd7b47a48ee43c77622bf36bc0eb605197e8d92e
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit e2696396f54858838574a6fb388988e18a778024)
|
|
Bug: 268505211
Change-Id: Ief8f0e703650c002db30ac185d79dca56ba4777a
Signed-off-by: Jenny Ho <hsiufangho@google.com>
|
|
SBMerger: 478053055
Change-Id: I5d0d04b439ab893ce3cb0b5ce115d9bc378755fc
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
SBMerger: 478053055
Change-Id: I76017e12bfd191b06daafa97c2004153369001d7
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
Enable the pogo accessory detection in Android U. Note that it remains
disabled on DEV and EVT2.
Bug: 272390033
Change-Id: Ie61a9424b217374b32090b8f9f692a840a673c80
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 3f465745b9a1b5077c2cd101359a1d38c8e516d4)
|
|
There is a possibility that when doing the phy restart due to
orientation change, the USB phy is being turned on so that the memory
access causes Asychronous SError Interrupt. Fix this by moving the
orientation updating to a dedicated function and call it prior to the
enabling of the USB phy. Also remove the phy restart during
switch_to_usbc_locked as the updated orientation will be adopted in the
phy in enable_data_path_locked automatically.
Bug: 271689070
Change-Id: I68d95a3f0b0e200bb6503c073ebe708a2102502e
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit bb175cd05c76ba1951ed2c257b110c1d425baeb4)
|
|
There is a possibility that when doing the phy restart due to
orientation change, the USB phy is being turned on so that the memory
access causes Asychronous SError Interrupt. Fix this by moving the
orientation updating to a dedicated function and call it prior to the
enabling of the USB phy. Also remove the phy restart during
switch_to_usbc_locked as the updated orientation will be adopted in the
phy in enable_data_path_locked automatically.
Bug: 271689070
Change-Id: I68d95a3f0b0e200bb6503c073ebe708a2102502e
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
SBMerger: 478053055
Change-Id: I91a6c764cf9f1ae8e4bc96b4b0bd304bd01da2a9
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
SBMerger: 478053055
Change-Id: I52d9c4394d522fd4f234021e271840ebd4b966fd
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
android13-gs-pixel-5.10-tm-qpr2
|
|
When registering EXTCON, the last entry in the supported cable array
should be EXTCON_NONE. Otherwise, the cable array in the extcon device
might store the data from unexpected out-of-bound memory adjacent to
the supported cable array. This might cause null pointer dereference in
cable_name_show function in extcon.c.
Call trace:
cable_name_show+0xc0/0xcc
dev_attr_show+0x4c/0xa4
sysfs_kf_seq_show+0x114/0x224
kernfs_seq_show+0xa4/0x124
seq_read_iter+0x270/0x7b0
kernfs_fop_read_iter+0xbc/0x2a8
vfs_read+0x450/0x498
ksys_read+0xb0/0x144
Bug: 258382812
Change-Id: I0458c81c27ae90deedb81f37f085672e77194688
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
android13-gs-pixel-5.10-udc
|
|
Use the new property dma-cons for the DPU s2mpu.
This tells the driver that there is a consumer device that issues DMA
during boot, so it will link it as a consumer and will hold a
reference for it until the driver probes.
Bug: 262187119
Change-Id: I20a55c3cb2c8a3af1a0058fcaf1107c3face49cb
Signed-off-by: Mostafa Saleh <smostafa@google.com>
|
|
SBMerger: 478053055
Change-Id: I52154de56a7e6604469be8de824874977d88f8f8
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
SBMerger: 478053055
Change-Id: I7097d9d2393f65ed59ad6f21e2ee8b6cb53049f8
Signed-off-by: SecurityBot <android-nexus-securitybot@system.gserviceaccount.com>
|
|
android13-gs-pixel-5.10-tm-qpr2
|
|
Use the new property dma-cons for the DPU s2mpu.
This tells the driver that there is a consumer device that issues DMA
during boot, so it will link it as a consumer and will hold a
reference for it until the driver probes.
Bug: 262187119
Change-Id: I20a55c3cb2c8a3af1a0058fcaf1107c3face49cb
Signed-off-by: Mostafa Saleh <smostafa@google.com>
|
|
|
|
Bug: 251371792
Change-Id: I085423c60875709bbba23aabe2575604caadb946
Signed-off-by: Kyle Tso <kyletso@google.com>
(cherry picked from commit 0757fbcbebfd5828da57ab9d825ecf43754309da)
|
|
While docked, executing FRS causes the 12V from POGO pins
to be shorted to the USB-C VBUS pins. This OVP's the
USB-C accesory while shutting down POGO partner as well.
Disable FRS altogether till we have an API to disable
it in runtime.
Bug: 266645982
Change-Id: I57441e34a2d9f2d41944bea0f88df387ede34a38
Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
|
|
Bug: 251371792
Change-Id: I085423c60875709bbba23aabe2575604caadb946
Signed-off-by: Kyle Tso <kyletso@google.com>
|
|
into android13-gs-pixel-5.10-tm-qpr2
|
|
Remove the property
status = "okay";
from the following two nodes
tps65132_bias: lcd-bias@3e
rt4801_bias: lcd-bias@73
The kernel appears to assume the value "okay" if the property status is
absent.
Bug: 265256786
Fixes: 1da07fe ("arm64/dts: tangorpro: add lcd bias device tree entry")
Change-Id: I947e708b2e6ae7158658616ca84b95ba7904c93d
Signed-off-by: Daniel Mentz <danielmentz@google.com>
|
|
|
|
add image enhance function on CABC moving mode
Bug: 247038909
Test: check sysfs node and register
Change-Id: Idfebbaf4a27e8bf47b24e23256981b9bb5080064
Signed-off-by: gilliu <gilliu@google.com>
|
