From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
"Tim Harvey" <tharvey@gateworks.com>,
"Michael Walle" <mwalle@kernel.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Jean Delvare" <jdelvare@suse.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Lee Jones" <lee@kernel.org>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Mathieu Poirier" <mathieu.poirier@linaro.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Cheng-Yi Chiang" <cychiang@chromium.org>,
"Tzung-Bi Shih" <tzungbi@kernel.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Tinghan Shen" <tinghan.shen@mediatek.com>,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-hwmon@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-sound@vger.kernel.org,
linux-watchdog@vger.kernel.org,
"Mathew McBride" <matt@traverse.com.au>
Subject: Re: [PATCH v2] dt-bindings: mfd: Move embedded controllers to own directory
Date: Fri, 22 Aug 2025 15:40:27 -0500 [thread overview]
Message-ID: <20250822204027.GA319356-robh@kernel.org> (raw)
In-Reply-To: <20250822075712.27314-2-krzysztof.kozlowski@linaro.org>
On Fri, Aug 22, 2025 at 09:57:13AM +0200, Krzysztof Kozlowski wrote:
> Move ChromeOS Embedded Controller, Gateworks System Controller and
> Kontron sl28cpld Board Management Controller to new subdirectory
> "embedded-controller" matching their purpose. MFD is coming from Linux
> and does not really fit the actual purpose of this hardware.
>
> Rename Gateworks GSC filename to match compatible, as preferred for
> bindings.
>
> Acked-by: Michael Walle <mwalle@kernel.org> # for sl28cpld
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>
> Cc: Mathew McBride <matt@traverse.com.au>
>
> Lee,
> Can you take it via MFD?
>
> Changes in v2:
> 1. Correct remaining paths in other schemas ($ref and descriptions)
> ---
> .../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.
Other candidates:
Documentation/devicetree/bindings/platform/*
Documentation/devicetree/bindings/misc/olpc,xo1.75-ec.yaml
Documentation/devicetree/bindings/misc/ge-achc.yaml ?
Rob
next prev parent reply other threads:[~2025-08-23 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:57 [PATCH v2] dt-bindings: mfd: Move embedded controllers to own directory Krzysztof Kozlowski
2025-08-22 9:22 ` Linus Walleij
2025-08-22 20:40 ` Rob Herring [this message]
2025-08-23 8:58 ` Krzysztof Kozlowski
[not found] ` <175682479961.2401991.17056649550187344851.b4-ty@kernel.org>
2025-09-02 15:20 ` (subset) " Krzysztof Kozlowski
2025-09-03 7:39 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250822204027.GA319356-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=cychiang@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=matt@traverse.com.au \
--cc=matthias.bgg@gmail.com \
--cc=mwalle@kernel.org \
--cc=tglx@linutronix.de \
--cc=tharvey@gateworks.com \
--cc=thierry.reding@gmail.com \
--cc=tinghan.shen@mediatek.com \
--cc=tzungbi@kernel.org \
--cc=ukleinek@kernel.org \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).