From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-riscv <linux-riscv@lists.infradead.org>,
Fabio Estevam <festevam@gmail.com>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
"maintainer:BROADCOM BCM7XXX ARM ARCHITECTURE"
<bcm-kernel-feedback-list@broadcom.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
devicetree@vger.kernel.org, Ray Jui <rjui@broadcom.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-unisoc@lists.infradead.org,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Scott Branden <sbranden@broadcom.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v2 01/13] dt-bindings: gpio: add common schema for GPIO controllers
Date: Sun, 20 Sep 2020 21:39:15 +0200 [thread overview]
Message-ID: <20200920193915.GA31074@kozik-lap> (raw)
In-Reply-To: <CAL_JsqJCLgf6syqV=jNPHPyu02ygwWCDDV+U9VCm0qRpLkirSQ@mail.gmail.com>
On Fri, Sep 18, 2020 at 08:30:02AM -0600, Rob Herring wrote:
> On Thu, Sep 17, 2020 at 10:53 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >
> > Convert parts of gpio.txt bindings into common dtschema file for GPIO
> > controllers. The schema enforces proper naming of GPIO controller nodes
> > and GPIO hogs.
>
> Did you not see my previous reply about a common schema? We already
> have a common GPIO and hog schema in dtschema. Please add to it
> whatever is missing.
Indeed, I'll enhance the dt-schema.
The trouble is that each in-kernel YAML file still has to mention
possible gpio-hogs nodes. Is the proper solution to put them in common
YAML inside kernel sources?
>
> My goal is all common schema end up in dtschema, but I haven't pushed
> folks to do that yet. Ones I've done are there though. One issue is
> what's in dtschema should be GPL/BSD and the existing text bindings
> are default GPL, so there's a relicensing exercise. In some cases, the
> schema is there but I haven't copied over the descriptions.
Right, I'll skip the descriptions when posting to dt-schema.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-09-20 19:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 16:52 [PATCH v2 00/13] gpio: add common dtschema Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 01/13] dt-bindings: gpio: add common schema for GPIO controllers Krzysztof Kozlowski
2020-09-17 20:09 ` Laurent Pinchart
2020-09-18 7:52 ` Krzysztof Kozlowski
2020-09-18 14:18 ` Laurent Pinchart
2020-09-18 14:30 ` Rob Herring
2020-09-20 19:39 ` Krzysztof Kozlowski [this message]
2020-09-22 15:40 ` Rob Herring
2020-09-17 16:52 ` [PATCH v2 02/13] dt-bindings: gpio: include common schema in " Krzysztof Kozlowski
2020-09-17 20:13 ` Laurent Pinchart
2020-09-17 16:52 ` [PATCH v2 03/13] dt-bindings: gpio: pl061: add missing properties and include common schema Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 04/13] dt-bindings: gpio: fsl-imx-gpio: add i.MX ARMv6 and ARMv7 compatibles Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 05/13] dt-bindings: gpio: fsl-imx-gpio: add gpio-line-names Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 06/13] dt-bindings: gpio: gpio-vf610: fix iMX 7ULP compatible matching Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 07/13] dt-bindings: media: include common schema in GPIO controllers Krzysztof Kozlowski
2020-09-17 16:52 ` [PATCH v2 08/13] dt-bindings: mfd: " Krzysztof Kozlowski
2020-09-21 9:54 ` Charles Keepax
2020-09-17 16:52 ` [PATCH v2 09/13] dt-bindings: pinctrl: " Krzysztof Kozlowski
2020-09-17 19:03 ` Paul Cercueil
2020-09-17 20:12 ` Laurent Pinchart
2020-09-21 9:55 ` Charles Keepax
2020-09-17 16:52 ` [PATCH v2 10/13] ASoC: dt-bindings: zl38060: " Krzysztof Kozlowski
2020-09-17 16:59 ` Mark Brown
2020-09-17 16:52 ` [PATCH v2 11/13] arm64: dts: imx8mq-librem5: correct GPIO hog property Krzysztof Kozlowski
2020-09-17 16:53 ` [PATCH v2 12/13] arm64: dts: imx8mq-librem5: align GPIO hog names with dtschema Krzysztof Kozlowski
2020-09-17 16:53 ` [PATCH v2 13/13] ARM: dts: imx: " Krzysztof Kozlowski
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=20200920193915.GA31074@kozik-lap \
--to=krzk@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-unisoc@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sbranden@broadcom.com \
--cc=shawnguo@kernel.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).