From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> To: Linus Walleij <linus.walleij@linaro.org> Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-unisoc@lists.infradead.org, "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Orson Zhai <orsonzhai@gmail.com> Subject: Re: [PATCH v2 1/4] dt-bindings: gpio: Add devicetree binding for RDA Micro GPIO controller Date: Mon, 21 Oct 2019 11:45:51 +0530 [thread overview] Message-ID: <20191021061551.GA12001@Mani-XPS-13-9360> (raw) In-Reply-To: <CACRpkdY3OC675EjZ4PYhYxnk1XWh4EO-a3JJBha2rdBttySUNQ@mail.gmail.com> Hi Linus, On Wed, Oct 16, 2019 at 02:27:44PM +0200, Linus Walleij wrote: > On Tue, Oct 15, 2019 at 7:30 PM Manivannan Sadhasivam > <manivannan.sadhasivam@linaro.org> wrote: > > > Add YAML devicetree binding for RDA Micro GPIO controller. > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> > > First: this looks awesome to me, > > Second: since this is kind of a first... could we move the standard GPIOchip > YAML business into a generic gpiochip .yaml file? > > We currently only have pl061-gpio.yaml and this would duplicate a lot > of the stuff from that yaml file. > > If you look at how > display/panel/panel-common.yaml > is used from say > display/panel/ti,nspire.yaml > > Could we do something similar and lift out all the generics from > gpio-pl061.yaml to > gpio-common.yaml > and reference that also in the new binding? > > If it seems hard, tell me and I can take a stab at it. > Eventhough I really want to help you here, I'm running out of time (and you know why). Let's consider merging this, and I'll come back at it later. Thanks, Mani > Yours, > Linus Walleij
WARNING: multiple messages have this Message-ID (diff)
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> To: Linus Walleij <linus.walleij@linaro.org> Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com>, linux-unisoc@lists.infradead.org, Orson Zhai <orsonzhai@gmail.com>, Linux ARM <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v2 1/4] dt-bindings: gpio: Add devicetree binding for RDA Micro GPIO controller Date: Mon, 21 Oct 2019 11:45:51 +0530 [thread overview] Message-ID: <20191021061551.GA12001@Mani-XPS-13-9360> (raw) In-Reply-To: <CACRpkdY3OC675EjZ4PYhYxnk1XWh4EO-a3JJBha2rdBttySUNQ@mail.gmail.com> Hi Linus, On Wed, Oct 16, 2019 at 02:27:44PM +0200, Linus Walleij wrote: > On Tue, Oct 15, 2019 at 7:30 PM Manivannan Sadhasivam > <manivannan.sadhasivam@linaro.org> wrote: > > > Add YAML devicetree binding for RDA Micro GPIO controller. > > > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> > > First: this looks awesome to me, > > Second: since this is kind of a first... could we move the standard GPIOchip > YAML business into a generic gpiochip .yaml file? > > We currently only have pl061-gpio.yaml and this would duplicate a lot > of the stuff from that yaml file. > > If you look at how > display/panel/panel-common.yaml > is used from say > display/panel/ti,nspire.yaml > > Could we do something similar and lift out all the generics from > gpio-pl061.yaml to > gpio-common.yaml > and reference that also in the new binding? > > If it seems hard, tell me and I can take a stab at it. > Eventhough I really want to help you here, I'm running out of time (and you know why). Let's consider merging this, and I'll come back at it later. Thanks, Mani > Yours, > Linus Walleij _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-21 6:16 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-15 17:30 [PATCH v2 0/4] Add GPIO support for RDA8810PL SoC Manivannan Sadhasivam 2019-10-15 17:30 ` Manivannan Sadhasivam 2019-10-15 17:30 ` [PATCH v2 1/4] dt-bindings: gpio: Add devicetree binding for RDA Micro GPIO controller Manivannan Sadhasivam 2019-10-15 17:30 ` Manivannan Sadhasivam 2019-10-16 12:27 ` Linus Walleij 2019-10-16 12:27 ` Linus Walleij 2019-10-21 6:15 ` Manivannan Sadhasivam [this message] 2019-10-21 6:15 ` Manivannan Sadhasivam 2019-10-15 17:30 ` [PATCH v2 2/4] ARM: dts: Add RDA8810PL GPIO controllers Manivannan Sadhasivam 2019-10-15 17:30 ` Manivannan Sadhasivam 2019-10-15 17:30 ` [PATCH v2 3/4] gpio: Add RDA Micro GPIO controller support Manivannan Sadhasivam 2019-10-15 17:30 ` Manivannan Sadhasivam 2019-10-15 17:33 ` Manivannan Sadhasivam 2019-10-15 17:33 ` Manivannan Sadhasivam 2019-10-16 12:41 ` Linus Walleij 2019-10-16 12:41 ` Linus Walleij 2019-10-19 16:05 ` Manivannan Sadhasivam 2019-10-19 16:05 ` Manivannan Sadhasivam 2019-10-21 0:57 ` Linus Walleij 2019-10-21 0:57 ` Linus Walleij 2019-10-21 6:19 ` Manivannan Sadhasivam 2019-10-21 6:19 ` Manivannan Sadhasivam 2019-10-15 17:30 ` [PATCH v2 4/4] MAINTAINERS: Add entry for RDA Micro GPIO driver and binding Manivannan Sadhasivam 2019-10-15 17:30 ` Manivannan Sadhasivam
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=20191021061551.GA12001@Mani-XPS-13-9360 \ --to=manivannan.sadhasivam@linaro.org \ --cc=bgolaszewski@baylibre.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-unisoc@lists.infradead.org \ --cc=orsonzhai@gmail.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.