display controller and a bunch of small improvements for different boards,
-----BEGIN PGP SIGNATURE-----
iQFEBAABCAAuFiEE7v+35S2Q1vLNA3Lx86Z5yZzRHYEFAmWTQY8QHGhlaWtvQHNu
dGVjaC5kZQAKCRDzpnnJnNEdgR2KCACyLUswFY8NgdDsb7rifTJmuaUKCi47F6J8
PuRCXDgfeXIjBRaWu438uwAdBX1kbu6qbLF4c+jEOF+rReG6jCqIkiZS3mdQvA73
k1wkwQuEBv3cALZIrVh9ddOPDJQ8mtmwwalGhAbuCfrquj0V6NY8KSgkG+LFI5wl
/iPbgCT3/O3v5D1ckOmK7wYxcv7cZwiYGXlxnRIaeY4KeQXvapV5HgeXLG2tD66w
T9BHoC5xKAlh72WL3fCnPwH7Kuk4MIbed/9CK3TzGXfKwIEN+2L4LGclSsN426la
khgMXde4x+3mCz9Rj1v9iiU7B7vBro9pPMEaUts0FUePsaMVt42Z
=jAec
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEiK/NIGsWEZVxh/FrYKtH/8kJUicFAmWT3TMACgkQYKtH/8kJ
UidBmA//QJoH0AxK8i9oUlLxaOIhHyA3HsIjU+gXU7xwOWlvmd2jllgk6vXmj97c
1q1ocA6pBpE9RYW6yG+gfqewyzu3hNh6DihRhjewuxrVMYI8pZD0WMy7/8AMb7Fd
0PgYiNwYvPXlxPn5LUwIYA8qYoy9rVXFSAIkgoccS2vJEhdJBz/0X2dODFH1BHFe
0gCfX3C4dq4NKLrbr09TSpd8Wf++mOm03tD9WEtzbamjmU8Uxu0h42Vr93YpRKkD
8bJH6H9BVM1SdTxkbK/H/h+Gq1gjzTYhys5ANL4tBHQOcwFgL5QwLsOYCANyjYVZ
O47a7IFqrQq9A8cXlsOIfPyeYyKULI3CDZoNAcT6UveLsx+tKRFLMw9XU1pJDu3A
OsJfxXfgkXCxwX++dJ1Aer5VjdEBrwnxKcNl7ZEcflwjf9il3ysZ0oAerDSt2dxG
HxSuQtL/ZAhwKwOAJce5C9gEPT5Rl+QDoLxlP28YkgAh7m+ttmUkgF/GxtauSRjG
VQmkCPkBfEOHjbmBDU2W99Q8liCHEMqZAyn2nkfnFPpBD/g2Sw2AqvS6XwNq0l7r
Yz2rq6xtc+YCtxNnlhAu/CqOBNoE8yDFvBXBd/fq4WCcMfLT0/mOnR7PR2PB0A9j
YuDUEkFZInY8K8C+gDq0bNa3o+IuRT9e9Ncs+eTmgNKYXGX5uss=
=w3tt
-----END PGP SIGNATURE-----
Merge tag 'v6.8-rockchip-dts64-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip into soc/dt
One new boards, the CoolPi CM5 SoM and 4B SBC. Basic node for the rk3588
display controller and a bunch of small improvements for different boards,
* tag 'v6.8-rockchip-dts64-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip: (21 commits)
arm64: dts: rockchip: Fix led pinctrl of lubancat 1
arm64: dts: rockchip: correct gpio_pwrctrl1 typo on nanopc-t6
arm64: dts: rockchip: correct gpio_pwrctrl1 typo on rock-5b
arm64: dts: rockchip: support poweroff on the rock-5b
arm64: dts: rockchip: Support poweroff on Orange Pi 5
arm64: dts: rockchip: nanopc-t6 sdmmc beautification
arm64: dts: rockchip: Fix rk3588 USB power-domain clocks
arm64: dts: rockchip: configure eth pad driver strength for orangepi r1 plus lts
arm64: dts: rockchip: Support poweroff on NanoPC-T6
arm64: dts: rockchip: rk3308-rock-pi-s gpio-line-names cleanup
arm64: dts: rockchip: Add support for rk3588 based board Cool Pi CM5 EVB
dt-bindings: arm: rockchip: Add Cool Pi CM5
arm64: dts: rockchip: Add support for rk3588s based board Cool Pi 4B
dt-bindings: arm: rockchip: Add Cool Pi 4B
dt-bindings: vendor-prefixes: Add Cool Pi
arm64: dts: rockchip: add gpio-line-names to rk3328-rock-pi-e
arm64: dts: rockchip: make use gpio-keys for buttons on puma-haikou
arm64: dts: rockchip: expose BIOS Disable feedback pin on rk3399-puma
arm64: dts: rockchip: fix misleading comment in rk3399-puma-haikou.dts
arm64: dts: rockchip: Add vop on rk3588
...
Link: https://lore.kernel.org/r/3711719.VqM8IeB0Os@diego
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
This corrects the rate of the UTMI clock on IPQ6018 USB0. The SDHCI
controller on SC7280 gains missing markings for being cache-coherent.
For SC8180X a typo in assignment of PCIe refgen clocks is corrected, PCI
controllers are marked cache-coherent, and the USB SS PHY interrupts are
corrected to allow wakeup.
Similarly USB HS PHY and SS PHY interrupts are corrected to allow
wakeup on SDM670.
On SM8550 the X3 cluster idle state is properly described, and the
latency numbers are adjusted for all the idle states.
The PM8550 regulator supplies on X1E are corrected to match the driver
and binding, and the timer node is updated to avoid an unnecessary
validation error.
-----BEGIN PGP SIGNATURE-----
iQJJBAABCAAzFiEEBd4DzF816k8JZtUlCx85Pw2ZrcUFAmWQ4aIVHGFuZGVyc3Nv
bkBrZXJuZWwub3JnAAoJEAsfOT8Nma3FY6IQAMM8Fg9OFi+bvRXZ4BKoMbrqf+Zq
UlnKxvf4Q5n598VsAMCUyPZnMdzuFGY7GsUOHikVIfTzjTKXDW7/Fgj3ng2SMEaF
fnktiQRQcmiTt2pitihPQe2ygSqrXul0LnTXzQSmixmqrzhvGgvsNAPNBelGeXaK
tK5ciyphgzKfvftNU52aUICodxbinH6mZMBv9sXHxK4XNYS68S2dklOv9g3+2v0b
S9Sn8kYXlDjlvWkwXYZtX4C3UuOrqM/cCc2rAfqAvkH4tGx85xFhV8pL0jEwGCC1
ozJ8Bl4yntjG9z1JVKGynEjJJJk2D1HQfxDdB9r7du74qftP2aBNQVyPP8HhtpJG
sgsMEJbPvbUPZJquv34SFSyPUit1ik0KOfXPSMqGd7jAxqc8n2vO56o/tDrCydh2
/W4UB4vPHJZbylg3Cx1kIjJit8g5TrdDeikX3tEA3oiRhKh5qeMU4h0rfT6qc04K
AkPtqq3oK+Zv+xZNvT7umjE8/We9Fj7ZSiNd2e0eBlh/I7OwG29r/O76mKXQW9m7
f/WJYGOpkulA8l+1GMO0ffjrLtlgIz9TBV0qv0fnG4AluBUOiL6eBJUwMTWzeCm5
wEXsXjC/AxpFpaVliZW701sKq9v3O5O6Av77Uv1ZJVUfztMW0SVmU1ir4b5+M9vK
X7aEgrUQYW4tMbT4
=AB7G
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEiK/NIGsWEZVxh/FrYKtH/8kJUicFAmWT3NgACgkQYKtH/8kJ
Uif5mQ/8CDmtKdEF4iFUTyC2lU6A4lY4fKlRJT9EdqCiX5ySSSZKKg2jCvcEcDry
AmvBaNg4TG0KPx3e4iheJuk2vu/BrtxqZV2dSa7vPUYwEMAGpsmJ035zWfU2ZeQq
lrBSbYcepIVvlossh1UuLfdWqRRDD0AxcAnB2CdBtpckw6358fe/cO/AT/MSYDF1
PqPTBzO+rMhThrONLXdI2NO/FJ2nSz680IFlolQURxQHb4UO8VqzKcaZ98fF4sY2
kLjyhLBgfK/bqGUxSVPrCgEDFJvGxXYK0oIWk/MKPw8BhdTxm9eSMyMI5ojiKuDn
g01qaCEtgGsVbyc+EWiJkxtqQpqIaw0Zi6O4p/RAJiB3+UVKFGdHWbJ0HssBAz1I
miytdlRFPErMIyD+k8CKp+n6Y5iwlxyNTnx3y3iBkMe+PAt3FG+ZfXZotWNufWxT
WKsUjZJ+YZ6pjPoaI63NDAxzZrNgo6GQYJZ55LtEvMkuhfCvi5xaBywIJ6tuCK5I
SOa8fDMOriBBaNro5TfWAEnfF7uKBOiqnAn9WNi3/BLvqqB1jDqHCwJo/eZtYpQG
POyNs+Nt0IBLSJaWOFYHHkhTuw/Gq1lpVQ1jsGQNvEdnXlZmLMVQ/lEsbN/35sa2
W2f2wP0ALih3htYPNhnzYcHa57R2oJU6jeJ4v5xpxNXIXQxRzEo=
=1cPt
-----END PGP SIGNATURE-----
Merge tag 'qcom-arm64-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into soc/dt
A few more Qualcomm Arm64 DeviceTree updates for v6.8
This corrects the rate of the UTMI clock on IPQ6018 USB0. The SDHCI
controller on SC7280 gains missing markings for being cache-coherent.
For SC8180X a typo in assignment of PCIe refgen clocks is corrected, PCI
controllers are marked cache-coherent, and the USB SS PHY interrupts are
corrected to allow wakeup.
Similarly USB HS PHY and SS PHY interrupts are corrected to allow
wakeup on SDM670.
On SM8550 the X3 cluster idle state is properly described, and the
latency numbers are adjusted for all the idle states.
The PM8550 regulator supplies on X1E are corrected to match the driver
and binding, and the timer node is updated to avoid an unnecessary
validation error.
* tag 'qcom-arm64-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
arm64: dts: qcom: sc8180x: Fix up PCIe nodes
arm64: dts: qcom: sc8180x: Mark PCIe hosts cache-coherent
arm64: dts: qcom: x1e80100-qcp: Fix supplies for some LDOs in PM8550
arm64: dts: qcom: sm8550: Update idle state time requirements
arm64: dts: qcom: sm8550: Separate out X3 idle state
arm64: dts: qcom: ipq6018: fix clock rates for GCC_USB0_MOCK_UTMI_CLK
arm64: dts: qcom: x1e80100: align mem timer size cells with bindings
arm64: dts: qcom: sc7280: Mark SDHCI hosts as cache-coherent
arm64: dts: qcom: sc8180x: fix USB SS wakeup
arm64: dts: qcom: sdm670: fix USB SS wakeup
arm64: dts: qcom: sdm670: fix USB DP/DM HS PHY interrupts
Link: https://lore.kernel.org/r/20231231034108.3262678-1-andersson@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
The recently introduced changes to the SDX55 USB controller interrupt
flags prevents the USB controller from probing. These patches corrects
the PDC's interrupt-cells, so that appropriate interrupt controller
(which supports both-edge interrupts) can be used instead, which
resolves the issue.
The SDX55 PCIe PHY base address is also adjusted, from a mistake when
the node recently was transitioned to the modernized DeviceTree binding.
-----BEGIN PGP SIGNATURE-----
iQJJBAABCAAzFiEEBd4DzF816k8JZtUlCx85Pw2ZrcUFAmWQ35oVHGFuZGVyc3Nv
bkBrZXJuZWwub3JnAAoJEAsfOT8Nma3FDpQP/3tGAnkKGDTiN7s/K2LVS0nDwM17
lyAyp/g+k7ja9FH2uwZ+ImUVSLS9s7PhaK6H8PGF/KMF3S803UKOGY7ElNjnYWOb
+MPbfQY8bKAsfGctkd2vRiVjzb0XgKep+BCs7TObO4BLkUGaYgUrU7QKZd9RR4xC
1MXvJJZS2DMjmpJX52ZLbGYHryLMMyUl3NRCyGy8oxVRgeGBAySUFsdUXQmwrvfn
Smaax9rLmzEJEgqELjtlwTwHlvmQ7pDtYQ6OKkXHxXUuVdTWZbU0+7i5NTeW6YQv
TFkQKSRuVPCk+rmq5mF5HJ/uXUVD537THsanIVRJL7wYoo2sWzYGwQAcMPdMlP3M
+9izr6w1W/BSQEzrRyQ6otV2+FX5DnuNjJlI7e9t0nS9+qwpmkoGf4FrbS/sIEsh
1/JHUJCSvQ5ErOEZh6XuTMcbxjp4qbT+zGCFJIC4RXA9kOgPd8gEYw8M3nAhoyxo
l8pVHa5SdDBdL2UzTO08QErifyEj/6n0wY0tk5nkDhQb8sCRQpXT6lnw2zvk+Lj1
ZnU06IYg6sCOGgy2rk4K2B3RT6UOr3Vn/HowYtmt9ycka2jIPKUwdM0WmSYEVbTv
j72oFjdICUqwg2Eqycbj/ZjMYtFTFG1SG8d5CIZ6Ary6dHwvxWm5PxcEnsAhSOBB
VFh5WkS6TEVIlJ3m
=uLxU
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEiK/NIGsWEZVxh/FrYKtH/8kJUicFAmWT3KsACgkQYKtH/8kJ
UidbphAAn+4Nb4RzhHMh1NhLxSoIpxmyYqPb+NQb2NHbroU5VMrrkVLy7KEMojTa
A+sC/+9+xrzn/PSb38t6I5go+ObpPGGGqCoH8FLJ2kzyQMIMl+xrkqQ+T7kRqxSE
1OPq6zBDKl5osdc1ROFCHN7MUz7R50guVUxQjJpMWSsBnFpepKiKv4JvEKZnrMAt
nDjmymwEvdODLnCbtDdMB5czZQNLh4AtobI8iqsgGXwyoBNOQ1WY3PkRh+hTc7Ml
lmccfIizelBDpbCmrvmq94lKoF2JIdNS5kLUCV54iTAo88F2KVrhDu+NRaGAZI0o
ZDGDI3yf8Tn6G+epsTq/BPSm3mhjZNTLB/rfxE8ImQa/MM4aH4uEb7ekCRZarrLU
FCDs2Bkkzlz34/5Zx5Ht3Pd11/erfvOWShhfpYwJZ0T+iUlWF5xxIJefe2lHXKmP
5fwdaH+t5nEZAydS/BiqatGpcV4Kz5g2eQdeb16dzs7q1vr9YY33GlKqGROVxFua
fYlKu/UDjDIJa2VQdOq8NE3VN/FvyKa/4T9RQMIYJ+W7nhY4itOeoPsn5A94B+4x
zR0GLoa7jJZA4cd2sM+PGCnyjdLiRR7x5u6D10j1+3QSuGYVwhByo4e/DBzhAu39
jb8AoBQHyEAHpQOIYBSnntBoks7se8GcS2i5Cq8QBmYazfhG3P4=
=OFU8
-----END PGP SIGNATURE-----
Merge tag 'qcom-arm32-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into soc/dt
A few more Qualcomm Arm32 DeviceTree updates fr v6.8
The recently introduced changes to the SDX55 USB controller interrupt
flags prevents the USB controller from probing. These patches corrects
the PDC's interrupt-cells, so that appropriate interrupt controller
(which supports both-edge interrupts) can be used instead, which
resolves the issue.
The SDX55 PCIe PHY base address is also adjusted, from a mistake when
the node recently was transitioned to the modernized DeviceTree binding.
* tag 'qcom-arm32-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
ARM: dts: qcom: sdx55: Fix the base address of PCIe PHY
ARM: dts: qcom: sdx55: fix USB SS wakeup
ARM: dts: qcom: sdx55: fix USB DP/DM HS PHY interrupts
ARM: dts: qcom: sdx55: fix pdc '#interrupt-cells'
Link: https://lore.kernel.org/r/20231231033153.3262575-1-andersson@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
for 6.8, please pull the following:
- Rafal adds a Device Tree node for the BCM63138 high-speed UART used
for Bluetooth devices
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEm+Rq3+YGJdiR9yuFh9CWnEQHBwQFAmWMhRwACgkQh9CWnEQH
BwTjig//UDApRkCg3NVjVXR9tRQLJrpOS8H2/uKAQ8X4W7ZIn4nBZeavOoFabNFS
m7wOpyRcVJvqDbsdyx5SLUIgT01JCJgcBWmj5bq3Laue3AHeTznVfjpfcFOiLkXR
/aAVva2L1Dpo3mHgo3BSJy4ZYOI5s7dX/6PCpXqN9oxUHNCIXPyUepS/qFh+hQ3i
rmbZvtLsNtpsWOZCgcmRqWOrShoRh7GFIGmBffIuW3S69x+Lg2H+uYYb8lnHs0uC
1AFVszeyrUxnM1kngKMg0lRRENt0IJJi/4OL94vTYt3eY/HzvEMb4Tl8O4jkLi2N
dIN0SU4Epv65EUCeAKaMjrVxWITY3EQsDKsL2obuJ1Q///FmyeZ6+vE6HYHFruOg
uHKypGiz2PqDd43A1hk0K0EGi/DPVSFU+QJZ7TZJWH2DBd763UxTbnRZBO0Bk4KO
QvgSbwjOMOi226ETkppiks5mvJr17gfbL6/opGOmKD5p8vpqzdg5MGRvDSf/+r31
l7POet/HUxU9oiEjyYLI+BQV/9PsBQX1ZrMe4QRlQe+/xn6XlvIgLokdUc7kl1zT
ToqGKzxhI1fODet40QRGeNaYoM5Lmme5cgr7CZAivPPcO0RfEZ3IC1kseLFRh0WT
F2bL5N22BNnqyy7R1NGV/qQhM4OPpYOJDsf5UhyN1BOFPwS6iyQ=
=tHoM
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEiK/NIGsWEZVxh/FrYKtH/8kJUicFAmWT28YACgkQYKtH/8kJ
Uice0xAA1v2qyMcXQBHux0Wh/oL5upNZzu7/6eSffEI7nzL07dbkogHi7y0w/oWz
8HT3orv5rM1yjnDckCe+9lK3JSIL0P23Zw9odAVmkwz21VdRqPxcr5UvK2gSdopV
crI0tMci+NUyGHjTKKs5fAJJOcQkT/ONUQZXpi0aorE8VRqNdL2+uYwMMChcn9u/
5BOX1bF7l9JKaayoVSCTGcnlCv1Hk6AgvfsDVHC8ylyAA7OiRGkNKPTCuQe9/xRC
9yoT8pUITgqasUf6tFTuwRACVaYT4pjrLU3zc8afcjw/8GXt0GRgxL+TndISDtmk
cygr1nE+EnAA8Ph0Ye6+SunMrQosUzf9Sowtr9J+y/v3RbQ+uScIU0ivbJdVOGFO
cteirVVOLUppXFADFatevSxH8/Z/mmH9CyS4Wy97GrPXYzIVePm7sRlkEMY0G19s
YO8PvIKQ09NAQVFKgCktrs5PfHGGetgDG4Uwi5zrxaiQQrNeh/Qfm1WODFnw/qvK
nt8ubG2z7L/8Px+2tnI858y7ux6yEiQXJ+xmEeGdWMkthGveUv+Cs5vrukvn5zft
afi5JOxUxN4sLRVS6OxY8va8AFRaV8xvtDkWklPKuhACJYDw8Kl8aj0nWbsRZaDL
nC9Fz0StohyvlY5kI0W49YtdV8gFv89hw+C6Olla8kWvP4kQ/bM=
=oReX
-----END PGP SIGNATURE-----
Merge tag 'arm-soc/for-6.8/devicetree' of https://github.com/Broadcom/stblinux into soc/dt
This pull request contains Broadcom ARM-based SoCs Device Tree changes
for 6.8, please pull the following:
- Rafal adds a Device Tree node for the BCM63138 high-speed UART used
for Bluetooth devices
* tag 'arm-soc/for-6.8/devicetree' of https://github.com/Broadcom/stblinux:
ARM: dts: broadcom: Add BCM63138's high speed UART
Link: https://lore.kernel.org/r/20231228085822.3656546-1-florian.fainelli@broadcom.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
This enables the base drivers necessary to boot devices on the X1E
platform.
The GPU clock controller for SM8450/SM8550 is enabled and the SC8280XP
camera clock controller is enabled, to enable respective functionality
on these platforms.
-----BEGIN PGP SIGNATURE-----
iQJJBAABCAAzFiEEBd4DzF816k8JZtUlCx85Pw2ZrcUFAmWQ4w8VHGFuZGVyc3Nv
bkBrZXJuZWwub3JnAAoJEAsfOT8Nma3FekQQAIDooZmUIpsFcMbz2wnCj3l3SsxA
6wL0lmsW/HMeSYKjJdKyFkx+CQ9C7YKoRbj3JWIzYycnhe/CQTLJOrqg7i9vH5m5
SDlfh2mWhsbjVeDZy9c82rcnKaxyYH4SB35Yj2WehcLreDd01IA7LK7PDSGO9Xm6
vatos45gglK9/LeABILSM8hEobJbiCSz4ADB9M7pQKOv/cP5t9nHCjox3vXWe37t
Rse2OVa3solvJKPj6kyxiJ7HllK5+62DKJodD0Ary75XekjvYJ3+NSCg9dtvG2yz
WKmEWQcRrgybElmmw4GK8fi7pGNUiIsz2TstmOZyuGn3MtWr6W7Qr6Bbd7WOKUD1
BTGu1Ceqn8bBGlBSp4t9DUIlcgr4YxgRufdW6HxI6g2bcdsPEwi67KqixwcPik1q
w0vNiSX0OOgq3lLRdDrGjrh3tLeVDm5ymmAbqVWR9GxDtytBFljTv1Og7GuOGO05
qrVkURVSZMcqhgSWYppp4svvv+0J1lBroVqdRDESw4CDF6l3cLL11NxGLbLS8Kub
Re3kx7HAlIZt3MuCTVtGLdkJhWQ0Sd3niNQw9gKiOAIU8eihDluhSNozPOJwzqsi
Z0mWyRLZ6dpQyBOihA7OwF3aNwY4SQCruaE0FG5kEyMrR3s7JeycM41nLegDldZA
0awhhz2pD0WJRNy4
=gd3I
-----END PGP SIGNATURE-----
gpgsig -----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEiK/NIGsWEZVxh/FrYKtH/8kJUicFAmWT2PAACgkQYKtH/8kJ
UicnoRAAmTlKuwvNvBL10mtCvt3cX2d+gKbpzaUaWqoa8gA0nfugLXHXWs7kdnf3
CQ4FbVASha33WtjAOjLSJ7cx3n49e6SY/HH5VUt0Rn1B4XzONzd4pHtfdVvTx68c
VVnNEHsZp0tSY0a2XYtNBBxa2HkLk7Z8qCpSDu2gNcSJ27HO3USlOgiuXHHuq0g8
+b9b4f012VelKuao6l3ZZ9TLMVWLbvNpNwrQCTnOAtWC8e5p+2Tno72/H9vs+pUn
NTM5olUcGfrxW1mHZbvMp6TFvcC162xuSb0mlIA1fUodQUodBRjpwGPdzLVXVOAb
b0+3meiPe9x/RPXlbjcvK359FJL/wXY3oQqbpBEn6wssv5gfdR+hg5ZjVwbJxDrz
VDqiJ8Yi+IFWDAJY1Ckz1BD8m8xxOhY0MA8Dfd/VntTO2S8eeA07VtzC+zqhGKkr
XQlu/ZxAx+SPU6DvlIpU7ehdGyngH22tyb64vzbBOi+BxgQTJMv05XFMl3NfL8K1
UyBmHxt5BN2p8TD2lceaqQfB4qEXo16sMPCmUqeMBtuNjNZnOV9RnX0DLu8S3PnM
m5i/lPOrv6q7Se8uShP6SXX8aZdDXj38FTPYZk6sDcG7gf19DeG57X6aUweE1p3f
BHLRiuAMjUtxdjERz/idPmwZuEi5Kxk772iXE9dfigL4zXGYmeQ=
=L0cS
-----END PGP SIGNATURE-----
Merge tag 'qcom-arm64-defconfig-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux into soc/defconfig
A few more Qualcomm Arm64 defconfig updates for v6.8
This enables the base drivers necessary to boot devices on the X1E
platform.
The GPU clock controller for SM8450/SM8550 is enabled and the SC8280XP
camera clock controller is enabled, to enable respective functionality
on these platforms.
* tag 'qcom-arm64-defconfig-for-6.8-2' of https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux:
arm64: defconfig: Enable Qualcomm SC8280XP camera clock controller
arm64: defconfig: enable GPU clock controller for SM8[45]50
arm64: defconfig: Enable X1E80100 SoC base configs
Link: https://lore.kernel.org/r/20231231034648.3262882-1-andersson@kernel.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Drop empty and redundant maintainer entries for boards which were
removed to fix `scripts/get_maintainer.pl --self-test=sections` errors
like:
./MAINTAINERS:2021: warning: section without file pattern ARM/CIRRUS LOGIC EDB9315A MACHINE SUPPORT
[arnd: only remove the obviously stale ones for now]
Cc: Lennert Buytenhek <kernel@wantstofly.org>
Cc: Steve Sakoman <sakoman@gmail.com>
Cc: Mark F. Brown <mark.brown314@gmail.com>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Florian Fainelli <florian@openwrt.org>
Cc: Simtec Linux Team <linux@simtec.co.uk>
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link: https://lore.kernel.org/r/20231218134532.50599-1-krzysztof.kozlowski@linaro.org
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Currently, each trip point defined in the device tree corresponds to a
single hardware interrupt. This commit instead switches to using two
hardware interrupts, whose values are set dynamically using the
set_trips callback. Additionally, the critical temperature threshold is
handled specifically.
Setting interrupts in this way also fixes a long-standing lockdep
warning, which was caused by calling thermal_zone_get_trips with our
lock being held. Do note that this requires TMU initialization to be
split into two parts, as done by the parent commit: parts of the
initialization call into the thermal_zone_device structure and so must
be done after its registration, but the initialization is also
responsible for setting up calibration, which must be done before
thermal_zone_device registration, which will call set_trips for the
first time; if the calibration is not done in time, the interrupt values
will be silently wrong!
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-10-m.majewski2@samsung.com
The original driver did not use that macro and it allows us to make our
intentions slightly clearer.
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-9-m.majewski2@samsung.com
This will be needed in the future, as the thermal zone subsystem might
call our callbacks right after devm_thermal_of_zone_register. Currently
we just make get_temp return EAGAIN in such case, but this will not be
possible with state-modifying callbacks, for instance set_trips.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-8-m.majewski2@samsung.com
Exynos 4210 supports setting a base threshold value, which is added to
all trip points. This might be useful, but is not really necessary in
our usecase, so we always set it to 0 to simplify the code a bit.
Additionally, this change makes it so that we convert the value to the
calibrated one in a slightly different place. This is more correct
morally, though it does not make any change when single-point
calibration is being used (which is the case currently).
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-7-m.majewski2@samsung.com
We rewrite the initialization to enable the regulator as part of devm,
which allows us to not handle the struct instance manually.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> Link:
https://lore.kernel.org/r/20231201095625.301884-6-m.majewski2@samsung.com
Currently, if regulator is required in the SoC, but
devm_regulator_get_optional fails for whatever reason, the execution
will proceed without propagating the error. Meanwhile there is no
reason to output the error in case of -ENODEV.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-5-m.majewski2@samsung.com
The workqueue boilerplate is mostly one-to-one what the threaded
interrupts do.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-4-m.majewski2@samsung.com
We do not use the value, and only Exynos 7 defines this alias anyway.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-3-m.majewski2@samsung.com
It seems that the field has been removed in one of the previous commits,
but the description has been forgotten.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Mateusz Majewski <m.majewski2@samsung.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231201095625.301884-2-m.majewski2@samsung.com
The following warnings are shown during compilation:
tui.c: In function 'show_cooling_device':
tui.c:216:40: warning: format '%d' expects argument of type 'int', but
argument 7 has type 'long unsigned int' [-Wformat=]
216 | "%02d %12.12s%6d %6d",
| ~~^
| |
| int
| %6ld
......
219 | ptdata.cdi[j].cur_state,
| ~~~~~~~~~~~~~~~~~~~~~~~
| |
| long unsigned int
tui.c:216:44: warning: format '%d' expects argument of type 'int', but
argument 8 has type 'long unsigned int' [-Wformat=]
216 | "%02d %12.12s%6d %6d",
| ~~^
| |
| int
| %6ld
......
220 | ptdata.cdi[j].max_state);
| ~~~~~~~~~~~~~~~~~~~~~~~
| |
| long unsigned int
To fix this, the correct string format must be used for printing.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231204141335.2798194-1-fe@dev.tdt.de
Clean up the examples by adding newline separators, moving 'reg'
properties after 'compatible' and dropping unused labels.
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231130174114.13122-3-johan+linaro@kernel.org
The ADC Thermal Monitor is part of an SPMI PMIC, which in turn sits on
an SPMI bus.
Fixes: db03874b85 ("dt-bindings: thermal: qcom: add HC variant of adc-thermal monitor bindings")
Fixes: e8ffd6c075 ("dt-bindings: thermal: qcom: add adc-thermal monitor bindings")
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231130174114.13122-2-johan+linaro@kernel.org
This patch adds a thermal sensor controller support for the D1/T113s,
which is similar to the one on H6, but with only one sensor and
different scale and offset values.
Signed-off-by: Maxim Kiselev <bigunclemax@gmail.com>
Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231217210629.131486-3-bigunclemax@gmail.com
This macro has the advantage over SIMPLE_DEV_PM_OPS that we don't have to
care about when the functions are actually used, so the corresponding
__maybe_unused can be dropped.
Also make use of pm_ptr() to discard all PM related stuff if CONFIG_PM
isn't enabled.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231116112633.668826-3-u.kleine-koenig@pengutronix.de
amlogic_thermal_disable() returned zero unconditionally and
amlogic_thermal_remove() already ignores the return value.
Make it return no value and modify amlogic_thermal_suspend to not check
the value.
This patch introduces no semantic changes, but makes it more obvious for
a human reader that amlogic_thermal_suspend() cannot fail.
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231116112633.668826-2-u.kleine-koenig@pengutronix.de
Currently, the default mechanism is to trigger a shutdown after the
critical temperature is reached.
In some embedded cases, such behavior does not suit well, as the board may
be unattended in the field and rebooting may be a better approach.
The bootloader may also check the temperature and only allow the boot to
proceed when the temperature is below a certain threshold.
Introduce support for allowing a reboot to be triggered after the
critical temperature is reached.
If the "critical-action" devicetree property is not found, fall back to
the shutdown action to preserve the existing default behavior.
If a custom ops->critical exists, then it takes preference over
critical-actions.
Tested on a i.MX8MM board with the following devicetree changes:
thermal-zones {
cpu-thermal {
critical-action = "reboot";
};
};
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231129124330.519423-4-festevam@gmail.com
Introduce thermal_zone_device_critical_reboot() to trigger an
emergency reboot.
It is a counterpart of thermal_zone_device_critical() with the
difference that it will force a reboot instead of shutdown.
The motivation for doing this is to allow the thermal subystem
to trigger a reboot when the temperature reaches the critical
temperature.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231129124330.519423-3-festevam@gmail.com
Add some helper functions to make it easier introducing the support
for thermal reboot.
No functional change.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231129124330.519423-2-festevam@gmail.com
Document the critical-action property to describe the thermal action
the OS should perform after the critical temperature is reached.
The possible values are "shutdown" and "reboot".
The motivation for introducing the critical-action property is that
different systems may need different thermal actions when the critical
temperature is reached.
For example, in a desktop PC, it is desired that a shutdown happens
after the critical temperature is reached.
However, in some embedded cases, such behavior does not suit well,
as the board may be unattended in the field and rebooting may be a
better approach.
The bootloader may also benefit from this new property as it can check
the SoC temperature and in case the temperature is above the critical
point, it can trigger a shutdown or reboot accordingly.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231129124330.519423-1-festevam@gmail.com
Add the missing 'thermal-sensor-cells' property which is required for
every thermal sensor as it's used when using phandles.
And add the thermal-sensor.yaml reference.
In fact, it was a careless mistake when submitting the driver that
caused it to not work properly. So the fix is necessary, although it
will result in the ABI break.
Fixes: 72684d99a8 ("thermal: dt-bindings: add loongson-2 thermal")
Cc: Yinbo Zhu <zhuyinbo@loongson.cn>
Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/6d69362632271ab0af9a5fbfa3bc46a0894f1d54.1700817227.git.zhoubinbin@loongson.cn
This helps validating DTS files. Introduced changes:
1. Improved title
2. Simplified description (dropped "This describes the device tree...")
3. Dropped undocumented "reset-names" from example
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Reviewed-by: Rob Herring <robh@kernel.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20231117052214.24554-1-zajec5@gmail.com
The new cleanup.h facilities that arrived in v6.5-rc1 can replace the
the usage of devm semantics in acpi_nfit_init_interleave_set(). That
routine appears to only be using devm to avoid goto statements. The
new __free() annotation at variable declaration time can achieve the same
effect more efficiently.
There is no end user visible side effects of this patch, I was
motivated to send this cleanup to practice using the new helpers.
Suggested-by: Dave Jiang <dave.jiang@intel.com>
Suggested-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
Reviewed-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
Link: https://lore.kernel.org/r/20231017082905.1673316-1-michal.wilczynski@intel.com
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
This patch adds support for each available OTP variant of the device.
The OTP configuration cannot be read over I2C, so it is derived from
a compatible string instead.
Early revisions of the D0 order code require their OTP-enabled func-
tionality to be manually restored following a soft reset; this patch
accommodates this erratum as well.
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Link: https://lore.kernel.org/r/ZZMaZbdk6iAKUjlm@nixie71
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
This patch adds bindings for the D0 order code of the device. This
order code represents an OTP variant that enables a touch-and-hold
function in place of slider 1.
Also included is the ability to specify the 00 order code (default
option with no OTP customization) explicitly.
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/ZZMaW9RkQ9bKXOUn@nixie71
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
This patch adds support for slider gestures that can be expressed
by the device. Each gesture (e.g. tap or hold) can be mapped to a
unique keycode for either slider 0 or 1.
With this change, raw slider coordinates are reported only if the
slider has no keycodes defined. This prevents unwanted mouse cur-
sor movement when expressing axial gestures (e.g. swipe) and also
eliminates some unnecessary I2C traffic.
Different revisions of silicon use different tap and swipe timeout
step sizes. Apply an appropriate scaling factor depending on which
revision is found.
To facilitate this change, store the iqs269_ver_info struct in the
driver's private data so that other functions can use it after the
driver has probed.
Last but not least, a former reserved field in iqs269_ver_info now
contains useful information; give it a name (fw_num).
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Link: https://lore.kernel.org/r/ZZMaT46WQq1/Nrsb@nixie71
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
This patch adds bindings for slider gestures that can be expressed
by the device.
Signed-off-by: Jeff LaBundy <jeff@labundy.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/ZZMaPrbSi4IrzwKF@nixie71
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
When a 'DEL_CLIENT' message is received from the remote, the corresponding
server port gets deleted. A DEL_SERVER message is then announced for this
server. As part of handling the subsequent DEL_SERVER message, the name-
server attempts to delete the server port which results in a '-ENOENT' error.
The return value from server_del() is then propagated back to qrtr_ns_worker,
causing excessive error prints.
To address this, return 0 from control_cmd_del_server() without checking the
return value of server_del(), since the above scenario is not an error case
and hence server_del() doesn't have any other error return value.
Signed-off-by: Sarannya Sasikumar <quic_sarannya@quicinc.com>
Reviewed-by: Simon Horman <horms@kernel.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Maxime Chevallier says:
====================
Introduce PHY listing and link_topology tracking
Here's a V5 of the multi-PHY support series.
At a glance, besides some minor fixes and R'd-by from Andrew, one of the
thing this series does is remove the ASSERT_RTNL() from the
topo_add_phy/del_phy operations.
These operations will take a PHY device and put it into the list of
devices associated to a netdevice. The main thing to protect here is the
list itself, but since we use xarrays, my naive understanding of it is
that it contains its own protection scheme. There shouldn't be a need
for more locking, as the insertion/deletion paths are already hooked
into the PHY connection to a netdev, or disconnection from it.
Now for the rest of the cover :
As a remainder, this ongoing work aims ultimately at supporting complex
link topologies that involve multiplexing multiple PHYs/SFPs on a single
netdevice. As a first step, it's required that we are able to enumerate the
PHYs on a given ethernet interface.
By just doing so, we also improve already-existing use-cases, namely the
copper SFP modules support when a media-converter is used (as we have 2
PHYs on the link, but only one is referenced by net_device.phydev, which
is used on a variety of netlink commands).
The series is architectured as follows :
- The first patch adds the notion of phy_link_topology, which tracks
all PHYs attached to a netdevice.
- Patches 2, 3 and 4 adds some plumbing into SFP and phylib to be able
to connect the dots when building the topology tree, to know which PHY
is connected to which SFP bus, trying not to be too invasive on phylib.
- Patch 5 allows passing a PHY_INDEX to ethnl commands. I'm uncertain about
this, as there are at least 4 netlink commands ( 5 with the one introduced
in patch 7 ) that targets PHYs directly or indirectly, which to me makes
it worth-it to have a generic way to pass a PHY index to commands, however
the approach taken may be too generic.
- Patch 6 is the netlink spec update + ethtool-user.c|h autogenerated code
update (the autogenerated code triggers checkpatch warning though)
- Patch 7 introduces a new netlink command set to list PHYs on a netdevice.
It implements a custom DUMP and GET operation to allow filtered dumps,
that lists all PHYs on a given netdevice. I couldn't use most of ethnl's
plumbing though.
- Patch 8 is the netlink spec update + ethtool-user.c|h update for that
new command
- Patch 8,9,10 and 11 updates the PLCA, strset, cable-test and pse netlink
commands to use the user-provided PHY instead of net_device.phydev.
- Finally patch 12 adds some documentation for this whole work.
Examples
========
Here's a short overview of the kind of operations you can have regarding
the PHY topology. These tests were performed on a MacchiatoBin, which
has 3 interfaces :
eth0 and eth1 have the following layout:
MAC - PHY - SFP
eth2 has this more classic topology :
MAC - PHY - RJ45
finally eth3 has the following topology :
MAC - SFP
When performing a dump with all interfaces down, we don't get any
result, as no PHY has been attached to their respective net_device :
None
The following output is with eth0, eth2 and eth3 up, but no SFP module
inserted in none of the interfaces :
[{'downstream-sfp-name': 'sfp-eth0',
'drvname': 'mv88x3310',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 0,
'index': 1,
'name': 'f212a600.mdio-mii:00',
'upstream-type': 'mac'},
{'drvname': 'Marvell 88E1510',
'header': {'dev-index': 4, 'dev-name': 'eth2'},
'id': 21040593,
'index': 1,
'name': 'f212a200.mdio-mii:00',
'upstream-type': 'mac'}]
And now is a dump operation with a copper SFP in the eth0 port :
[{'downstream-sfp-name': 'sfp-eth0',
'drvname': 'mv88x3310',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 0,
'index': 1,
'name': 'f212a600.mdio-mii:00',
'upstream-type': 'mac'},
{'drvname': 'Marvell 88E1111',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 21040322,
'index': 2,
'name': 'i2c:sfp-eth0:16',
'upstream': {'index': 1, 'sfp-name': 'sfp-eth0'},
'upstream-type': 'phy'},
{'drvname': 'Marvell 88E1510',
'header': {'dev-index': 4, 'dev-name': 'eth2'},
'id': 21040593,
'index': 1,
'name': 'f212a200.mdio-mii:00',
'upstream-type': 'mac'}]
-- Note that this shouldn't actually work as the 88x3310 PHY doesn't allow
a 1G SFP to be connected to its SFP interface, and I don't have a 10G copper SFP,
so for the sake of the demo I applied the following modification, which
of courses gives a non-functionnal link, but the PHY attach still works,
which is what I want to demonstrate :
@@ -488,7 +488,7 @@ static int mv3310_sfp_insert(void *upstream, const struct sfp_eeprom_id *id)
if (iface != PHY_INTERFACE_MODE_10GBASER) {
dev_err(&phydev->mdio.dev, "incompatible SFP module inserted\n");
- return -EINVAL;
+ //return -EINVAL;
}
return 0;
}
Finally an example of the filtered DUMP operation that Jakub suggested
in V1 :
[{'downstream-sfp-name': 'sfp-eth0',
'drvname': 'mv88x3310',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 0,
'index': 1,
'name': 'f212a600.mdio-mii:00',
'upstream-type': 'mac'},
{'drvname': 'Marvell 88E1111',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 21040322,
'index': 2,
'name': 'i2c:sfp-eth0:16',
'upstream': {'index': 1, 'sfp-name': 'sfp-eth0'},
'upstream-type': 'phy'}]
And a classic GET operation allows querying a single PHY's info :
{'drvname': 'Marvell 88E1111',
'header': {'dev-index': 2, 'dev-name': 'eth0'},
'id': 21040322,
'index': 2,
'name': 'i2c:sfp-eth0:16',
'upstream': {'index': 1, 'sfp-name': 'sfp-eth0'},
'upstream-type': 'phy'}
Changed in V5:
- Removed the RTNL assertion in the topology ops
- Made the phy_topo_get_phy inline
- Fixed the PSE-PD multi-PHY support by re-adding a wrongly dropped
check
- Fixed some typos in the documentation
- Fixed reverse xmas trees
Changes in V4:
- Dropped the RFC flag
- Made the net_device integration independent to having phylib enabled
- Removed the autogenerated ethtool-user code for the YNL specs
Changes in V3:
- Added RTNL assertions where needed
- Fixed issues in the DUMP code for PHY_GET, which crashed when running it
twice in a row
- Added the documentation, and moved in-source docs around
- renamed link_topology to phy_link_topology
Changes in V2:
- Added the DUMP operation
- Added much more information in the reported data, to be able to reconstruct
precisely the topology tree
- renamed phy_list to link_topology
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
The newly introduced phy_link_topology tracks all ethernet PHYs that are
attached to a netdevice. Document the base principle, internal and
external APIs. As the phy_link_topology is expected to be extended, this
documentation will hold any further improvements and additions made
relative to topology handling.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
The ETH_SS_PHY_STATS command gets PHY statistics. Use the phydev pointer
from the ethnl request to allow query phy stats from each PHY on the
link.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Cable testing is a PHY-specific command. Instead of targeting the command
towards dev->phydev, use the request to pick the targeted PHY.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
PSE and PD configuration is a PHY-specific command. Instead of targeting
the command towards dev->phydev, use the request to pick the targeted
PHY device.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
PLCA is a PHY-specific command. Instead of targeting the command
towards dev->phydev, use the request to pick the targeted PHY.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
The PHY_GET command, supporting both DUMP and GET operations, is used to
retrieve the list of PHYs connected to a netdevice, and get topology
information to know where exactly it sits on the physical link.
Add the netlink specs corresponding to that command.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
As we have the ability to track the PHYs connected to a net_device
through the link_topology, we can expose this list to userspace. This
allows userspace to use these identifiers for phy-specific commands and
take the decision of which PHY to target by knowing the link topology.
Add PHY_GET and PHY_DUMP, which can be a filtered DUMP operation to list
devices on only one interface.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Update the spec to take the newly introduced phy-index as a generic
request parameter.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Some netlink commands are target towards ethernet PHYs, to control some
of their features. As there's several such commands, add the ability to
pass a PHY index in the ethnl request, which will populate the generic
ethnl_req_info with the relevant phydev when the command targets a PHY.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Knowing the bus name is helpful when we want to expose the link topology
to userspace, add a helper to return the SFP bus name.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>