From: Thor Thayer <tthayer@opensource.altera.com> To: linux-hwmon@vger.kernel.org Subject: Re: [RFC 1/8] dt-bindings: mfd: Add Altera Arria10 System Resource Chip bindings Date: Mon, 18 Apr 2016 07:51:08 -0700 [thread overview] Message-ID: <5714F569.807@opensource.altera.com> (raw) In-Reply-To: <1459278791-3646-1-git-send-email-tthayer@opensource.altera.com> Hi Lee, On 04/18/2016 02:43 AM, Lee Jones wrote: On Fri, 15 Apr 2016, Thor Thayer wrote: On 03/30/2016 06:35 AM, Lee Jones wrote: On Tue, 29 Mar 2016, ttha...@opensource.altera.com wrote: From: Thor Thayer <ttha...@opensource.altera.com> To: linux-hwmon@vger.kernel.org The Altera Arria10 Devkit System Resource chip is a Multi-Function Device, it has two subdevices: - GPIO - HWMON This patch adds documentation for the Altera A10-SR DT bindings. Signed-off-by: Thor Thayer <ttha...@opensource.altera.com> --- .../devicetree/bindings/mfd/altera-a10sr.txt | 35 ++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 Documentation/devicetree/bindings/mfd/altera-a10sr.txt diff --git a/Documentation/devicetree/bindings/mfd/altera-a10sr.txt b/Documentation/devicetree/bindings/mfd/altera-a10sr.txt new file mode 100644 index 0000000..564c761 --- /dev/null +++ b/Documentation/devicetree/bindings/mfd/altera-a10sr.txt @@ -0,0 +1,35 @@ +* Altera Arria10 Development Kit System Resource Chip + +Required parent device properties: +- compatible : "altr,altr_a10sr" +- spi-max-frequency : Maximum SPI frequency. +- reg : the SPI Chip Select address for the Arria10 System Resource chip DT bindings are much easier to read in the following format: - compatible : "altr,altr_a10sr" - spi-max-frequency : Maximum SPI frequency. - reg : the SPI Chip Select address for the Arria10 System Resource chip ... also, sentences start with an uppercase char. +The A10SR consists of this varied group of sub-devices: + +Device Description +------ ---------- +altr_a10sr_gpio GPIO Controller +altr_a10sr_hwmon Hardware Monitor + +The LEDs are implemented entirely in the device tree using +the gpio-led framework. This is a Linuxisum and should not live in DT bindings. +Example: + + a10-sr: a10-sr@0 { Nodes should be named after their device 'type'. Does this device really start a address 0? I see in the documentation on device trees there are a number of categories I can use. GPIO is easy because it is one of the categories but I'm not sure about the new device I'm adding since the a10sr is a new device. It's always difficult with MFDs as they are by their very nature, more than one device. But how about 'resource-manager'? OK. Yes, that would be a good name. Thanks. I believe I should only call out the name and address on the SPI bus like: a10sr@0 { Correct. + compatible = "altr,altr-a10sr"; + reg = <0>; + spi-max-frequency = <100000>; + + a10sr_gpio: a10sr_gpio { Device type only please. and this would be a10sr_gpio: gpio-controller { Does that seem correct? Also correct. No address though? Thank you. It is at a fixed address inside the SPI device. When making this binding I followed the format of other gpio controllers like the tps65086 and lp3943 which didn't have an address. Thanks for the clarification. + compatible = "altr,a10sr-gpio"; + gpio-controller; + #gpio-cells = <2>; + ngpios = <16>; + }; + + a10sr_hwmon: a10sr_hwmon { Device type only please. I need to revisit where this will live (hwmon does not seem to be the correct place) so it will change but I can follow the format above if it is correct. Thanks for reviewing. + compatible = "altr,a10sr-hwmon"; + }; + }; -- To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Thor Thayer <tthayer@opensource.altera.com> To: Lee Jones <lee.jones@linaro.org> Cc: linus.walleij@linaro.org, gnurou@gmail.com, jdelvare@suse.com, linux@roeck-us.net, robh+dt@kernel.org, pawell.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, dinguyen@opensource.altera.com, linux-gpio@vger.kernel.org, linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [RFC 1/8] dt-bindings: mfd: Add Altera Arria10 System Resource Chip bindings Date: Mon, 18 Apr 2016 09:55:37 -0500 [thread overview] Message-ID: <5714F569.807@opensource.altera.com> (raw) In-Reply-To: <20160418074335.GA3346@x1> Hi Lee, On 04/18/2016 02:43 AM, Lee Jones wrote: > On Fri, 15 Apr 2016, Thor Thayer wrote: >> On 03/30/2016 06:35 AM, Lee Jones wrote: >>> On Tue, 29 Mar 2016, tthayer@opensource.altera.com wrote: >>> >>>> From: Thor Thayer <tthayer@opensource.altera.com> >>>> >>>> The Altera Arria10 Devkit System Resource chip is a Multi-Function >>>> Device, it has two subdevices: >>>> - GPIO >>>> - HWMON >>>> >>>> This patch adds documentation for the Altera A10-SR DT bindings. >>>> >>>> Signed-off-by: Thor Thayer <tthayer@opensource.altera.com> >>>> --- >>>> .../devicetree/bindings/mfd/altera-a10sr.txt | 35 ++++++++++++++++++++ >>>> 1 file changed, 35 insertions(+) >>>> create mode 100644 Documentation/devicetree/bindings/mfd/altera-a10sr.txt >>>> >>>> diff --git a/Documentation/devicetree/bindings/mfd/altera-a10sr.txt b/Documentation/devicetree/bindings/mfd/altera-a10sr.txt >>>> new file mode 100644 >>>> index 0000000..564c761 >>>> --- /dev/null >>>> +++ b/Documentation/devicetree/bindings/mfd/altera-a10sr.txt >>>> @@ -0,0 +1,35 @@ >>>> +* Altera Arria10 Development Kit System Resource Chip >>>> + >>>> +Required parent device properties: >>>> +- compatible : "altr,altr_a10sr" >>>> +- spi-max-frequency : Maximum SPI frequency. >>>> +- reg : the SPI Chip Select address for the Arria10 System Resource chip >>> >>> DT bindings are much easier to read in the following format: >>> >>> - compatible : "altr,altr_a10sr" >>> - spi-max-frequency : Maximum SPI frequency. >>> - reg : the SPI Chip Select address for the Arria10 System Resource chip >>> >>> ... also, sentences start with an uppercase char. >>> >>>> +The A10SR consists of this varied group of sub-devices: >>>> + >>>> +Device Description >>>> +------ ---------- >>>> +altr_a10sr_gpio GPIO Controller >>>> +altr_a10sr_hwmon Hardware Monitor >>>> + >>>> +The LEDs are implemented entirely in the device tree using >>>> +the gpio-led framework. >>> >>> This is a Linuxisum and should not live in DT bindings. >>> >>>> +Example: >>>> + >>>> + a10-sr: a10-sr@0 { >>> >>> Nodes should be named after their device 'type'. >>> >>> Does this device really start a address 0? >>> >> >> I see in the documentation on device trees there are a number of >> categories I can use. GPIO is easy because it is one of the >> categories but I'm not sure about the new device I'm adding since >> the a10sr is a new device. > > It's always difficult with MFDs as they are by their very nature, more > than one device. But how about 'resource-manager'? > OK. Yes, that would be a good name. Thanks. >> I believe I should only call out the name and address on the SPI bus like: >> >> a10sr@0 { > > Correct. > >>>> + compatible = "altr,altr-a10sr"; >>>> + reg = <0>; >>>> + spi-max-frequency = <100000>; >>>> + >>>> + a10sr_gpio: a10sr_gpio { >>> >>> Device type only please. >>> >> >> and this would be a10sr_gpio: gpio-controller { >> >> Does that seem correct? > > Also correct. No address though? > Thank you. It is at a fixed address inside the SPI device. When making this binding I followed the format of other gpio controllers like the tps65086 and lp3943 which didn't have an address. Thanks for the clarification. >>>> + compatible = "altr,a10sr-gpio"; >>>> + gpio-controller; >>>> + #gpio-cells = <2>; >>>> + ngpios = <16>; >>>> + }; >>>> + >>>> + a10sr_hwmon: a10sr_hwmon { >>> >>> Device type only please. >>> >> I need to revisit where this will live (hwmon does not seem to be >> the correct place) so it will change but I can follow the format >> above if it is correct. >> >> Thanks for reviewing. >> >>>> + compatible = "altr,a10sr-hwmon"; >>>> + }; >>>> + }; >>> >
next prev parent reply other threads:[~2016-04-18 14:51 UTC|newest] Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-03-29 19:13 [RFC] Addition of Altera Arria10 System Resource Chip tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-29 19:13 ` [RFC 1/8] dt-bindings: mfd: Add Altera Arria10 System Resource Chip bindings tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-30 11:35 ` Lee Jones 2016-03-30 11:36 ` Lee Jones 2016-03-31 14:06 ` Rob Herring 2016-03-31 18:21 ` Thor Thayer 2016-03-31 18:21 ` Thor Thayer 2016-04-01 8:14 ` Lee Jones 2016-04-01 8:14 ` Lee Jones 2016-04-01 20:21 ` Thor Thayer 2016-04-01 20:21 ` Thor Thayer 2016-03-29 19:13 ` [RFC 2/8] MAINTAINERS: Addition of Altera Arria10 System Resource Chip tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-30 8:19 ` Lee Jones 2016-03-30 8:19 ` Lee Jones 2016-03-29 19:13 ` [RFC 3/8] mfd: altr_a10sr: Add Altera Arria10 DevKit " tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-30 11:51 ` Lee Jones 2016-03-30 11:51 ` Lee Jones 2016-03-30 14:52 ` Thor Thayer 2016-03-30 14:52 ` Thor Thayer 2016-03-30 14:52 ` Lee Jones 2016-03-30 14:52 ` Lee Jones 2016-03-30 16:10 ` Mark Brown 2016-03-31 9:10 ` Lee Jones 2016-03-31 9:11 ` Lee Jones 2016-03-29 19:13 ` [RFC 4/8] gpio: altera-a10sr: Add A10 System Resource Chip GPIO support tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx [not found] ` <1459278791-3646-5-git-send-email-tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org> 2016-03-30 8:18 ` Lee Jones 2016-03-30 8:18 ` Lee Jones 2016-04-01 12:17 ` Linus Walleij 2016-04-01 20:34 ` Thor Thayer 2016-04-01 20:34 ` Thor Thayer 2016-04-08 11:39 ` Linus Walleij 2016-03-29 19:13 ` [RFC 5/8] ARM: socfpga: dts: Add Devkit A10-SR fields for Arria10 tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-30 17:42 ` Dinh Nguyen 2016-03-30 17:42 ` Dinh Nguyen 2016-03-31 18:28 ` Thor Thayer 2016-03-31 18:28 ` Thor Thayer 2016-03-29 19:13 ` [RFC 6/8] ARM: socfpga: dts: Add LED framework to A10-SR GPIO tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx 2016-03-29 19:13 ` [RFC 7/8] hwmon: Altera Arria10 System Resource Chip - HW Monitor tthayer 2016-03-29 19:13 ` tthayer 2016-03-29 20:16 ` Guenter Roeck 2016-03-29 21:43 ` Thor Thayer 2016-03-29 21:43 ` Thor Thayer 2016-03-29 22:29 ` Mark Brown 2016-03-29 22:30 ` Guenter Roeck 2016-03-30 8:17 ` Lee Jones 2016-03-30 8:18 ` Lee Jones 2016-03-29 19:13 ` [RFC 8/8] ARM: socfpga: dts: Add Devkit Arria10-SR HWMON tthayer 2016-03-29 19:13 ` tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx [not found] ` <1459278791-3646-1-git-send-email-tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org> 2016-03-30 8:14 ` [RFC] Addition of Altera Arria10 System Resource Chip Lee Jones 2016-03-30 8:14 ` Lee Jones 2016-03-30 14:27 ` [RFC 7/8] hwmon: Altera Arria10 System Resource Chip - HW Monitor Thor Thayer 2016-03-30 14:31 ` Thor Thayer 2016-04-15 16:57 ` [RFC 1/8] dt-bindings: mfd: Add Altera Arria10 System Resource Chip bindings Thor Thayer 2016-04-15 17:02 ` Thor Thayer 2016-04-18 7:43 ` Lee Jones 2016-04-18 7:44 ` Lee Jones 2016-04-18 7:45 ` Lee Jones 2016-04-18 7:46 ` Lee Jones 2016-04-18 14:51 ` Thor Thayer [this message] 2016-04-18 14:55 ` Thor Thayer 2016-04-18 15:07 ` Thor Thayer 2016-04-18 15:12 ` Thor Thayer 2016-04-19 7:23 ` Lee Jones 2016-04-19 7:25 ` Lee Jones 2016-04-19 14:38 ` Thor Thayer 2016-04-19 14:38 ` Thor Thayer 2016-04-20 1:48 ` Guenter Roeck 2016-04-20 1:48 ` Guenter Roeck
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=5714F569.807@opensource.altera.com \ --to=tthayer@opensource.altera.com \ --cc=linux-hwmon@vger.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: 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.