linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Frank Li <Frank.Li@nxp.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
	Jingoo Han <jingoohan1@gmail.com>, Pavel Machek <pavel@ucw.cz>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-input@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-leds@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: backlight: convert zii,rave-sp-backlight.txt to yaml
Date: Wed, 9 Oct 2024 09:59:25 -0500	[thread overview]
Message-ID: <20241009145925.GA465237-robh@kernel.org> (raw)
In-Reply-To: <20241009142758.GB16179@aspen.lan>

On Wed, Oct 09, 2024 at 03:27:58PM +0100, Daniel Thompson wrote:
> On Tue, Oct 08, 2024 at 06:00:58PM -0400, Frank Li wrote:
> > Convert device tree binding doc zii,rave-sp-backlight.txt to yaml format.
> > Additional Changes:
> > - Remove mfd parent node at example.
> > - Ref to backlight's common.yaml
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> >  .../leds/backlight/zii,rave-sp-backlight.txt       | 23 --------------
> >  .../leds/backlight/zii,rave-sp-backlight.yaml      | 36 ++++++++++++++++++++++
> >  2 files changed, 36 insertions(+), 23 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.txt b/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.txt
> > deleted file mode 100644
> > index ff5c921386502..0000000000000
> > --- a/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.txt
> > +++ /dev/null
> > @@ -1,23 +0,0 @@
> > -Zodiac Inflight Innovations RAVE Supervisory Processor Backlight Bindings
> > -
> > -RAVE SP backlight device is a "MFD cell" device corresponding to
> > -backlight functionality of RAVE Supervisory Processor. It is expected
> > -that its Device Tree node is specified as a child of the node
> > -corresponding to the parent RAVE SP device (as documented in
> > -Documentation/devicetree/bindings/mfd/zii,rave-sp.txt)
> > -
> > -Required properties:
> > -
> > -- compatible: Should be "zii,rave-sp-backlight"
> > -
> > -Example:
> > -
> > -	rave-sp {
> > -		compatible = "zii,rave-sp-rdu1";
> > -		current-speed = <38400>;
> > -
> > -		backlight {
> > -			compatible = "zii,rave-sp-backlight";
> > -		};
> > -	}
> > -
> > diff --git a/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.yaml b/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.yaml
> > new file mode 100644
> > index 0000000000000..fe9dba8231bf1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/leds/backlight/zii,rave-sp-backlight.yaml
> > @@ -0,0 +1,36 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/leds/backlight/zii,rave-sp-backlight.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Zodiac Inflight Innovations RAVE Supervisory Processor Backlight
> > +
> > +maintainers:
> > +  - Lee Jones <lee@kernel.org>
> 
> How did you arrive at this maintainer list?
> 
> It's not the usual backlight group and it also doesn't match the
> maintainer for the mfd bindings.

It should be someone that has Zodiac h/w, not backlight maintainers 
either. If we can't identify anyone then maybe the platform should be 
removed.

Rob


  reply	other threads:[~2024-10-09 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 22:00 [PATCH 0/5] dt-bindings: mfd: convert zii,rave-sp.txt and child txt to yaml format Frank Li
2024-10-08 22:00 ` [PATCH 1/5] dt-bindings: input: convert zii,rave-sp-pwrbutton.txt to yaml Frank Li
2024-10-09  0:14   ` Rob Herring (Arm)
2024-10-08 22:00 ` [PATCH 2/5] dt-bindings: backlight: convert zii,rave-sp-backlight.txt " Frank Li
2024-10-09  0:14   ` Rob Herring (Arm)
2024-10-09 14:27   ` Daniel Thompson
2024-10-09 14:59     ` Rob Herring [this message]
2024-10-08 22:00 ` [PATCH 3/5] dt-bindings: nvmem: convert zii,rave-sp-eeprom.txt to yaml format Frank Li
2024-10-09  0:14   ` Rob Herring (Arm)
2024-10-08 22:01 ` [PATCH 4/5] dt-bindings: watchdog: convert zii,rave-sp-wdt.txt " Frank Li
2024-10-09  0:14   ` Rob Herring (Arm)
2024-10-08 22:01 ` [PATCH 5/5] dt-bindings: mfd: convert zii,rave-sp.txt " Frank Li
2024-10-09 15:02 ` [PATCH 0/5] dt-bindings: mfd: convert zii,rave-sp.txt and child txt " Rob Herring

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=20241009145925.GA465237-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.thompson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jingoohan1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pavel@ucw.cz \
    --cc=srinivas.kandagatla@linaro.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).