On 22/08/2025 22:40, Rob Herring wrote:
quoted
---
.../bindings/{mfd => embedded-controller}/google,cros-ec.yaml | 2 +-
.../gateworks-gsc.yaml => embedded-controller/gw,gsc.yaml} | 2 +-
.../{mfd => embedded-controller}/kontron,sl28cpld.yaml | 2 +-
.../devicetree/bindings/gpio/kontron,sl28cpld-gpio.yaml | 2 +-
.../devicetree/bindings/hwmon/kontron,sl28cpld-hwmon.yaml | 2 +-
.../bindings/interrupt-controller/kontron,sl28cpld-intc.yaml | 2 +-
Documentation/devicetree/bindings/pwm/google,cros-ec-pwm.yaml | 2 +-
.../devicetree/bindings/pwm/kontron,sl28cpld-pwm.yaml | 2 +-
Documentation/devicetree/bindings/remoteproc/mtk,scp.yaml | 4 ++--
.../devicetree/bindings/sound/google,cros-ec-codec.yaml | 2 +-
.../devicetree/bindings/watchdog/kontron,sl28cpld-wdt.yaml | 2 +-
MAINTAINERS | 4 ++--
12 files changed, 14 insertions(+), 14 deletions(-)
rename Documentation/devicetree/bindings/{mfd => embedded-controller}/google,cros-ec.yaml (99%)
rename Documentation/devicetree/bindings/{mfd/gateworks-gsc.yaml => embedded-controller/gw,gsc.yaml} (98%)
rename Documentation/devicetree/bindings/{mfd => embedded-controller}/kontron,sl28cpld.yaml (97%)
Who's the maintainer for the 'embedded-controller' directory? Fine if
me, just need to know.
It does not have corresponding driver subsystem, then I guess you.
Placing above bindings, whose drivers are MFD, in the MFD subdirectory
made it obvious. Now it will be a bit less obvious, but that's the
drawback of organizing bindings per hardware, not per Linux subsystem.
Other candidates:
Documentation/devicetree/bindings/platform/*
Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml
Documentation/devicetree/bindings/misc/ge-achc.yaml ?
Indeed, I'll move these as well.
Best regards,
Krzysztof