All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lukasz Czerwinski <l.czerwinski@samsung.com>,
	jic23@cam.ac.uk, denis.ciocca@st.com, linux-iio@vger.kernel.org,
	Lee Jones <lee.jones@linaro.org>,
	devicetree@vger.kernel.org, Mark Rutland <Mark.Rutland@arm.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [RFC v2 PATCH 11/14] Documentation: Add st_magn binding documentation
Date: Tue, 01 Oct 2013 10:49:16 -0500	[thread overview]
Message-ID: <524AEEFC.8010201@gmail.com> (raw)
In-Reply-To: <524AF86D.7010200@kernel.org>

On 10/01/2013 11:29 AM, Jonathan Cameron wrote:
> On 09/27/13 17:32, Lukasz Czerwinski wrote:
>> This patch adds the document for STMicroeletronics Magnetic Sensors driver under
>> Documentation/devicetree/bindings/iio/.
>>
>> Signed-off-by: Lukasz Czerwinski <l.czerwinski@samsung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
>> ---
> 
> So right now we have two different approaches to documenting these bindings.  Lee
> proposed doing it on a per device name, here you are proposing a single file
> per type.
> 
> What is the prefered approach?
> 
> Lee/Lukasz why would you two favour one way or the other?
> 
> Device tree maintainers, which is preferred?

If the only difference is compatible string, then I think one doc is
fine and preferred by me.

Rob

> 
> Do we assume that any sane person looking up bindings will deploy
> grep to find where they are documented, or does it want to more
> or less be named after the part (in which case we'll get a lot
> of repetition).
> 
> Also, the question of whether _'s are acceptable in names
> to avoid breaking existing ABI for i2c devices is still open?
> I'm assuming that given the current situation and the fact
> that the word 'prefered' was used, we are better sticking
> with _'s? (that doesn't actually effect this patch, but does
> on the next two in this series and I'm being lazy).
> 
> 
>>  .../bindings/iio/magnetometer/st_magnometer.txt    |   33 ++++++++++++++++++++
>>  1 file changed, 33 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt b/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>> new file mode 100644
>> index 0000000..fb4f473
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>> @@ -0,0 +1,33 @@
>> +STMicroelectronics Magnetic Sensors
>> +
>> +Required properties:
>> +
>> +  - compatible : value should be one of the following:
>> +	(a) "st,lsm303dlhc" for magnetometer in LSM330DLHC
>> +	(b) "st,lsm303dlm" for magnetometer in LIS3DH
>> +	(c) "st,lis3mdl" for magnetometer in LSM330
>> +
>> +  - reg : the I2C address of the magnetometer
>> +
>> +Optional properties:
>> +
>> +  - st,drdy-int-pin : redirect DRDY on pin INT1 (1) or pin INT2 (2) (u8)
>> +
>> +  - interrupts : Interrupt numbers for the ST accelerometers, as an array
>> +	in case the magnetometer have more interrupt lines:
>> +	<DataReady irq>,
>> +	<Event irq>;
>> +
>> +  - interrupt-names : Array of strings associated with the interrupt numbers
>> +
>> +Example:
>> +
>> +lis3mdl@1c {
>> +	compatible = "st,lis3mdl";
>> +	reg = <0x1C>;
>> +
>> +	st,drdy-int-pin = /bits/ 8 <1>;
>> +	interrupt-parent = <&gpf0>;
>> +	interrupts = <5 0>, <6 0>;
>> +	interrupt-names = "drdy-int", "event-int";
>> +};
>>


WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Lukasz Czerwinski
	<l.czerwinski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
	jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org,
	denis.ciocca-qxv4g6HH51o@public.gmane.org,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Mark Rutland <Mark.Rutland-5wv7dgnIgG8@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	Ian Campbell
	<ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC v2 PATCH 11/14] Documentation: Add st_magn binding documentation
Date: Tue, 01 Oct 2013 10:49:16 -0500	[thread overview]
Message-ID: <524AEEFC.8010201@gmail.com> (raw)
In-Reply-To: <524AF86D.7010200-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On 10/01/2013 11:29 AM, Jonathan Cameron wrote:
> On 09/27/13 17:32, Lukasz Czerwinski wrote:
>> This patch adds the document for STMicroeletronics Magnetic Sensors driver under
>> Documentation/devicetree/bindings/iio/.
>>
>> Signed-off-by: Lukasz Czerwinski <l.czerwinski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>> Signed-off-by: Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>> ---
> 
> So right now we have two different approaches to documenting these bindings.  Lee
> proposed doing it on a per device name, here you are proposing a single file
> per type.
> 
> What is the prefered approach?
> 
> Lee/Lukasz why would you two favour one way or the other?
> 
> Device tree maintainers, which is preferred?

If the only difference is compatible string, then I think one doc is
fine and preferred by me.

Rob

> 
> Do we assume that any sane person looking up bindings will deploy
> grep to find where they are documented, or does it want to more
> or less be named after the part (in which case we'll get a lot
> of repetition).
> 
> Also, the question of whether _'s are acceptable in names
> to avoid breaking existing ABI for i2c devices is still open?
> I'm assuming that given the current situation and the fact
> that the word 'prefered' was used, we are better sticking
> with _'s? (that doesn't actually effect this patch, but does
> on the next two in this series and I'm being lazy).
> 
> 
>>  .../bindings/iio/magnetometer/st_magnometer.txt    |   33 ++++++++++++++++++++
>>  1 file changed, 33 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt b/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>> new file mode 100644
>> index 0000000..fb4f473
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/magnetometer/st_magnometer.txt
>> @@ -0,0 +1,33 @@
>> +STMicroelectronics Magnetic Sensors
>> +
>> +Required properties:
>> +
>> +  - compatible : value should be one of the following:
>> +	(a) "st,lsm303dlhc" for magnetometer in LSM330DLHC
>> +	(b) "st,lsm303dlm" for magnetometer in LIS3DH
>> +	(c) "st,lis3mdl" for magnetometer in LSM330
>> +
>> +  - reg : the I2C address of the magnetometer
>> +
>> +Optional properties:
>> +
>> +  - st,drdy-int-pin : redirect DRDY on pin INT1 (1) or pin INT2 (2) (u8)
>> +
>> +  - interrupts : Interrupt numbers for the ST accelerometers, as an array
>> +	in case the magnetometer have more interrupt lines:
>> +	<DataReady irq>,
>> +	<Event irq>;
>> +
>> +  - interrupt-names : Array of strings associated with the interrupt numbers
>> +
>> +Example:
>> +
>> +lis3mdl@1c {
>> +	compatible = "st,lis3mdl";
>> +	reg = <0x1C>;
>> +
>> +	st,drdy-int-pin = /bits/ 8 <1>;
>> +	interrupt-parent = <&gpf0>;
>> +	interrupts = <5 0>, <6 0>;
>> +	interrupt-names = "drdy-int", "event-int";
>> +};
>>

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-10-01 15:49 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 16:32 [RFC v2 PATCH 00/14] iio: STMicroelectronics DT and event support Lukasz Czerwinski
2013-09-27 16:32 ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 01/14] iio: st_common: New interrupt interface Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 15:34   ` Jonathan Cameron
2013-10-01 15:34     ` Jonathan Cameron
2013-10-01 16:22     ` Jonathan Cameron
2013-10-01 16:22       ` Jonathan Cameron
2013-10-21 11:59     ` Mark Rutland
2013-10-21 11:59       ` Mark Rutland
2013-10-21 11:48   ` Mark Rutland
2013-10-21 11:48     ` Mark Rutland
2013-09-27 16:32 ` [RFC v2 PATCH 02/14] iio: st_accel: Add dt bindings Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 15:40   ` Jonathan Cameron
2013-10-01 15:40     ` Jonathan Cameron
2013-10-21 11:37     ` Mark Rutland
2013-10-21 11:37       ` Mark Rutland
2013-09-27 16:32 ` [RFC v2 PATCH 03/14] iio: st_gyro: " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 04/14] iio: st_mang: " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 05/14] iio: st_pressure: " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 06/14] iio: st_common: Add threshold events support Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 16:09   ` Jonathan Cameron
2013-10-01 16:09     ` Jonathan Cameron
2013-09-27 16:32 ` [RFC v2 PATCH 07/14] iio: st_accel: Add event subsystem to st_accel driver Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 16:17   ` Jonathan Cameron
2013-10-01 16:17     ` Jonathan Cameron
2013-09-27 16:32 ` [RFC v2 PATCH 08/14] iio: iio_magn: Add event ops Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 16:21   ` Jonathan Cameron
2013-10-01 16:21     ` Jonathan Cameron
2013-09-27 16:32 ` [RFC v2 PATCH 09/14] iio: st_gyro: " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 10/14] iio: iio_press: " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-09-27 16:32 ` [RFC v2 PATCH 11/14] Documentation: Add st_magn binding documentation Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-01 16:29   ` Jonathan Cameron
2013-10-01 16:29     ` Jonathan Cameron
2013-10-01 15:49     ` Rob Herring [this message]
2013-10-01 15:49       ` Rob Herring
2013-10-22  6:55       ` Lee Jones
2013-10-22  6:55         ` Lee Jones
2013-10-21 11:16   ` Mark Rutland
2013-10-21 11:16     ` Mark Rutland
2013-09-27 16:32 ` [RFC v2 PATCH 12/14] Documentation: Add st_gyro " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-21 11:19   ` Mark Rutland
2013-10-21 11:19     ` Mark Rutland
2013-09-27 16:32 ` [RFC v2 PATCH 13/14] Documentation: Add st_pressure " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski
2013-10-21 11:23   ` Mark Rutland
2013-10-21 11:23     ` Mark Rutland
2013-09-27 16:32 ` [RFC v2 PATCH 14/14] Documentation: Add st_accel " Lukasz Czerwinski
2013-09-27 16:32   ` Lukasz Czerwinski

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=524AEEFC.8010201@gmail.com \
    --to=robherring2@gmail.com \
    --cc=Mark.Rutland@arm.com \
    --cc=denis.ciocca@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ian.campbell@citrix.com \
    --cc=jic23@cam.ac.uk \
    --cc=jic23@kernel.org \
    --cc=l.czerwinski@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=swarren@wwwdotorg.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 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.