| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20231108104343.24192-1-krzysztof.kozlowski@linaro.org>
Date: Wed, 8 Nov 2023 11:43:26 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Andi Shyti <andi.shyti@...nel.org>,
Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Lee Jones <lee@...nel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Tomasz Figa <tomasz.figa@...il.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Linus Walleij <linus.walleij@...aro.org>,
Thierry Reding <thierry.reding@...il.com>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaehoon Chung <jh80.chung@...sung.com>,
Sam Protsenko <semen.protsenko@...aro.org>,
dri-devel@...ts.freedesktop.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-iio@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-gpio@...r.kernel.org, linux-pwm@...r.kernel.org,
linux-rtc@...r.kernel.org, linux-serial@...r.kernel.org,
alsa-devel@...a-project.org, linux-sound@...r.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: [PATCH 00/17] dt-bindings: samsung: add specific compatibles for existing SoC
Hi,
Merging
=======
I propose to take entire patchset through my tree (Samsung SoC), because:
1. Next cycle two new SoCs will be coming (Google GS101 and ExynosAutov920), so
they will touch the same lines in some of the DT bindings (not all, though).
It is reasonable for me to take the bindings for the new SoCs, to have clean
`make dtbs_check` on the new DTS.
2. Having it together helps me to have clean `make dtbs_check` within my tree
on the existing DTS.
3. No drivers are affected by this change.
4. I plan to do the same for Tesla FSD and Exynos ARM32 SoCs, thus expect
follow up patchsets.
If folks agree, please kindly Ack the patches.
Description
===========
Samsung Exynos SoCs reuse several devices from older designs, thus historically
we kept the old (block's) compatible only. This works fine and there is no bug
here, however guidelines expressed in
Documentation/devicetree/bindings/writing-bindings.rst state that:
1. Compatibles should be specific.
2. We should add new compatibles in case of bugs or features.
Add compatibles specific to each SoC in front of all old-SoC-like compatibles.
This will also help reviews of new code using existing DTS as template. No
functional impact on Linux drivers behavior.
Future
======
If reasonable, I will do similar work for Tesla FSD and ARMv7/ARM32 Exynos
bindings and DTS.
Best regards,
Krzysztof
Krzysztof Kozlowski (17):
dt-bindings: hwinfo: samsung,exynos-chipid: add specific compatibles
for existing SoC
dt-bindings: i2c: exynos5: add specific compatibles for existing SoC
dt-bindings: i2c: samsung,s3c2410-i2c: add specific compatibles for
existing SoC
dt-bindings: mmc: samsung,exynos-dw-mshc: add specific compatibles for
existing SoC
dt-bindings: pinctrl: samsung: add specific compatibles for existing
SoC
dt-bindings: rtc: s3c-rtc: add specific compatibles for existing SoC
dt-bindings: serial: samsung: add specific compatibles for existing
SoC
dt-bindings: samsung: exynos-pmu: add specific compatibles for
existing SoC
dt-bindings: gpu: arm,mali-midgard: add specific compatibles for
existing Exynos SoC
dt-bindings: iio: samsung,exynos-adc: add specific compatibles for
existing SoC
ASoC: dt-bindings: samsung-i2s: add specific compatibles for existing
SoC
dt-bindings: pwm: samsung: add specific compatibles for existing SoC
arm64: dts: exynos5433: add specific compatibles to several blocks
arm64: dts: exynos7: add specific compatibles to several blocks
arm64: dts: exynos7885: add specific compatibles to several blocks
arm64: dts: exynos850: add specific compatibles to several blocks
arm64: dts: exynosautov9: add specific compatibles to several blocks
.../bindings/gpu/arm,mali-midgard.yaml | 5 ++
.../hwinfo/samsung,exynos-chipid.yaml | 17 +++++-
.../devicetree/bindings/i2c/i2c-exynos5.yaml | 10 +++-
.../bindings/i2c/samsung,s3c2410-i2c.yaml | 22 ++++---
.../bindings/iio/adc/samsung,exynos-adc.yaml | 29 +++++----
.../mfd/samsung,exynos5433-lpass.yaml | 2 +-
.../bindings/mmc/samsung,exynos-dw-mshc.yaml | 25 +++++---
.../samsung,pinctrl-wakeup-interrupt.yaml | 24 +++++---
.../bindings/pinctrl/samsung,pinctrl.yaml | 3 +-
.../devicetree/bindings/pwm/pwm-samsung.yaml | 2 +
.../devicetree/bindings/rtc/s3c-rtc.yaml | 5 ++
.../bindings/serial/samsung_uart.yaml | 14 ++++-
.../bindings/soc/samsung/exynos-pmu.yaml | 6 ++
.../bindings/soc/samsung/exynos-usi.yaml | 2 +-
.../bindings/sound/samsung-i2s.yaml | 19 +++---
arch/arm64/boot/dts/exynos/exynos5433.dtsi | 60 ++++++++++++-------
arch/arm64/boot/dts/exynos/exynos7.dtsi | 18 +++---
arch/arm64/boot/dts/exynos/exynos7885.dtsi | 45 +++++++++-----
arch/arm64/boot/dts/exynos/exynos850.dtsi | 34 ++++++-----
arch/arm64/boot/dts/exynos/exynosautov9.dtsi | 6 +-
20 files changed, 233 insertions(+), 115 deletions(-)
--
2.34.1
Powered by blists - more mailing lists