From: Feng Kan <fkan@apm.com> To: Mark Rutland <mark.rutland@arm.com> Cc: "patches@apm.com" <patches@apm.com>, "linus.walleij@linaro.org" <linus.walleij@linaro.org>, "gnurou@gmail.com" <gnurou@gmail.com>, "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH V5 2/3] Documentation: gpio: Add APM X-Gene SoC GPIO controller DTS binding Date: Tue, 8 Jul 2014 15:54:55 -0700 [thread overview] Message-ID: <CAL85gmDug-RHV+6gttLkDg+rM5PPHGew9KuX4SNbk9V3qE01=g@mail.gmail.com> (raw) In-Reply-To: <20140630125339.GA21390@leverpostej> On Mon, Jun 30, 2014 at 5:53 AM, Mark Rutland <mark.rutland@arm.com> wrote: > On Thu, Jun 26, 2014 at 11:59:46PM +0100, Feng Kan wrote: >> Documentation for APM X-Gene SoC GPIO controller DTS binding. >> >> Signed-off-by: Feng Kan <fkan@apm.com> >> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com> >> --- >> .../devicetree/bindings/gpio/gpio-xgene.txt | 20 ++++++++++++++++++++ >> 1 file changed, 20 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> >> diff --git a/Documentation/devicetree/bindings/gpio/gpio-xgene.txt b/Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> new file mode 100644 >> index 0000000..bd5fd85 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> @@ -0,0 +1,20 @@ >> +APM X-Gene SoC GPIO controller bindings >> + >> +This is a gpio controller that is part of the flash controller. >> +This gpio controller controls a total of 48 gpios. >> + >> +Required properties: >> +- compatible: "apm,xgene-gpio" for X-Gene GPIO controller >> +- reg: Physical base address and size of the controller's registers > > There is just the one bank? Internally there are three banks. Due to the fact the address space is meshed, It was agreed that we turn this into one simple node. > >> +- #gpio-cells: Should be two. >> + - first cell is the pin number >> + - second cell is used to specify optional parameters (unused) > > Why is there an unused cell? > > Why not just make this a single cell if the binding defines no valid > parameters? I will update documentation to indicate second cell is used for active low and active high setting since that is the behavior of the default of_xlate function. All it is seems to be doing is flipping the value of the gpio. I initially did this because I did not want to use additional attributes and followed the example documentation of number of other gpio driver. > >> +- gpio-controller: Marks the device node as a GPIO controller. > > No interrupts? Yes, no interrupts in this block. > > Thanks, > Mark. > >> + >> +Example: >> + gpio0: gpio0@1701c000 { >> + compatible = "apm,xgene-gpio"; >> + reg = <0x0 0x1701c000 0x0 0x40>; >> + gpio-controller; >> + #gpio-cells = <2>; >> + }; >> -- >> 1.9.1 >> >> -- >> To unsubscribe from this list: send the line "unsubscribe devicetree" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >>
WARNING: multiple messages have this Message-ID (diff)
From: fkan@apm.com (Feng Kan) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V5 2/3] Documentation: gpio: Add APM X-Gene SoC GPIO controller DTS binding Date: Tue, 8 Jul 2014 15:54:55 -0700 [thread overview] Message-ID: <CAL85gmDug-RHV+6gttLkDg+rM5PPHGew9KuX4SNbk9V3qE01=g@mail.gmail.com> (raw) In-Reply-To: <20140630125339.GA21390@leverpostej> On Mon, Jun 30, 2014 at 5:53 AM, Mark Rutland <mark.rutland@arm.com> wrote: > On Thu, Jun 26, 2014 at 11:59:46PM +0100, Feng Kan wrote: >> Documentation for APM X-Gene SoC GPIO controller DTS binding. >> >> Signed-off-by: Feng Kan <fkan@apm.com> >> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com> >> --- >> .../devicetree/bindings/gpio/gpio-xgene.txt | 20 ++++++++++++++++++++ >> 1 file changed, 20 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> >> diff --git a/Documentation/devicetree/bindings/gpio/gpio-xgene.txt b/Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> new file mode 100644 >> index 0000000..bd5fd85 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/gpio/gpio-xgene.txt >> @@ -0,0 +1,20 @@ >> +APM X-Gene SoC GPIO controller bindings >> + >> +This is a gpio controller that is part of the flash controller. >> +This gpio controller controls a total of 48 gpios. >> + >> +Required properties: >> +- compatible: "apm,xgene-gpio" for X-Gene GPIO controller >> +- reg: Physical base address and size of the controller's registers > > There is just the one bank? Internally there are three banks. Due to the fact the address space is meshed, It was agreed that we turn this into one simple node. > >> +- #gpio-cells: Should be two. >> + - first cell is the pin number >> + - second cell is used to specify optional parameters (unused) > > Why is there an unused cell? > > Why not just make this a single cell if the binding defines no valid > parameters? I will update documentation to indicate second cell is used for active low and active high setting since that is the behavior of the default of_xlate function. All it is seems to be doing is flipping the value of the gpio. I initially did this because I did not want to use additional attributes and followed the example documentation of number of other gpio driver. > >> +- gpio-controller: Marks the device node as a GPIO controller. > > No interrupts? Yes, no interrupts in this block. > > Thanks, > Mark. > >> + >> +Example: >> + gpio0: gpio0 at 1701c000 { >> + compatible = "apm,xgene-gpio"; >> + reg = <0x0 0x1701c000 0x0 0x40>; >> + gpio-controller; >> + #gpio-cells = <2>; >> + }; >> -- >> 1.9.1 >> >> -- >> To unsubscribe from this list: send the line "unsubscribe devicetree" in >> the body of a message to majordomo at vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >>
next prev parent reply other threads:[~2014-07-08 22:54 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-26 22:59 [PATCH V5 0/3] gpio: Add APM X-Gene SoC platform GPIO driver Feng Kan 2014-06-26 22:59 ` Feng Kan 2014-06-26 22:59 ` [PATCH V5 1/3] gpio: Add APM X-Gene SoC GPIO controller support Feng Kan 2014-06-26 22:59 ` Feng Kan 2014-07-04 21:20 ` Linus Walleij 2014-07-04 21:20 ` Linus Walleij 2014-07-04 21:22 ` Linus Walleij 2014-07-04 21:22 ` Linus Walleij 2014-06-26 22:59 ` [PATCH V5 2/3] Documentation: gpio: Add APM X-Gene SoC GPIO controller DTS binding Feng Kan 2014-06-26 22:59 ` Feng Kan 2014-06-30 12:53 ` Mark Rutland 2014-06-30 12:53 ` Mark Rutland 2014-07-04 21:28 ` Linus Walleij 2014-07-04 21:28 ` Linus Walleij 2014-07-07 18:52 ` Feng Kan 2014-07-07 18:52 ` Feng Kan 2014-07-07 21:26 ` Linus Walleij 2014-07-07 21:26 ` Linus Walleij 2014-07-07 21:54 ` Anton Vorontsov 2014-07-07 21:54 ` Anton Vorontsov 2014-07-08 22:54 ` Feng Kan [this message] 2014-07-08 22:54 ` Feng Kan 2014-06-26 22:59 ` [PATCH V5 3/3] arm64:dts: Add APM X-Gene SoC GPIO controller DTS entries Feng Kan 2014-06-26 22:59 ` Feng Kan 2014-06-28 3:14 ` [PATCH V5 0/3] gpio: Add APM X-Gene SoC platform GPIO driver Alexandre Courbot 2014-06-28 3:14 ` Alexandre Courbot
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='CAL85gmDug-RHV+6gttLkDg+rM5PPHGew9KuX4SNbk9V3qE01=g@mail.gmail.com' \ --to=fkan@apm.com \ --cc=devicetree@vger.kernel.org \ --cc=gnurou@gmail.com \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=patches@apm.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.