From: Beomho Seo <beomho.seo@samsung.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
"warren@wwwdotorg.org" <warren@wwwdotorg.org>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH 2/2] DT: Add binding documentation for CM36651 proximity/light sensor
Date: Thu, 26 Sep 2013 11:35:25 +0900 [thread overview]
Message-ID: <52439D6D.6030104@samsung.com> (raw)
In-Reply-To: <20130920094010.GG17453@e106331-lin.cambridge.arm.com>
Thank you for review.
I revised on your advice.
I will send v3 patch in the course of today.
reply about your question inline
> On Mon, Sep 09, 2013 at 07:10:41AM +0100, Beomho Seo wrote:
>> This patch add device tree binding documentation for CM36651
>> proximity/light sensor.
>>
>> Signed-off-by: Beomho Seo <beomho.seo@samsung.com>
>> ---
>> .../devicetree/bindings/iio/light/cm36651.txt | 24
>> ++++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.txt | 1 +
>> 2 files changed, 25 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iio/light/cm36651.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> b/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> new file mode 100644
>> index 0000000..3a6ba38
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> @@ -0,0 +1,24 @@
>> +* Capella CM36651 I2C Proximity and Color Light sensor
>> +
>> +Required properties:
>> +- compatible: must be "capella,cm36651"
>> +- reg: the I2C address of the device
>> +- interrupts: interrupt to which the chip is connected
>
> Nit: I'd prefer something like the below:
>
> - interrupts: interrupt-specifier for the sole interrupt generated by
> the device.
>
>> +- vled-supply: regulator for the sensor device, as covered
>> + in ../../regulator/regulator.txt
>
> I assume by the name that this is the regulator for the LED that's used
> alongside the sensor, rather than for the sensor itself?
>
> Is the LED part of the CM36651 unit, or is it external? I couldn't find
> any documentation for the unit.
>
vled_suppy is the regulator for the IR LED. In order to cm36651 manual, IR_LED part of the cm36651 unit.
>> +
>> +Example:
>> +
>> + i2c_cm36651: i2c-gpio {
>> + /* ... */
>> +
>> + cm36651@18 {
>> + compatible = "capella,cm36651";
>> + reg = <0x18>;
>> + interrupt-parent = <&gpx0>;
>> + interrupts = <2 0>;
>> + vled-supply = <&ps_als_reg>;
>> + };
>> +
>> + /* ... */
>> + };
>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
>> b/Documentation/devicetree/bindings/vendor-prefixes.txt
>> index ec4d713..044796d 100644
>> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
>> @@ -17,6 +17,7 @@ brcm Broadcom Corporation
>> cavium Cavium, Inc.
>> chrp Common Hardware Reference Platform
>> cirrus Cirrus Logic, Inc.
>> +capella Capella Microsystems, Inc
>
> The vendor prefix looks OK to me. However, it should apper before cavium
> to maintain the ordering of the file.
>
> Thanks,
> Mark.
>
>> cortina Cortina Systems, Inc.
>> dallas Maxim Integrated Products (formerly Dallas Semiconductor)
>> davicom DAVICOM Semiconductor, Inc.
>> --
>> 1.7.9.5
>>
>> --
>> Beomho Seo, Assistant Engineer
>> System S/W Lab., S/W Platform Team, Software Center
>> Samsung Electronics
>>
>
--
Best Regards,
Beomho Seo, Assistant Engineer
System S/W Lab., S/W Platform Team, Software Center
Samsung Electronics
WARNING: multiple messages have this Message-ID (diff)
From: Beomho Seo <beomho.seo-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
Cc: "linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org"
<jic23-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>,
"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Pawel Moll <Pawel.Moll-5wv7dgnIgG8@public.gmane.org>,
"warren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org"
<warren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
"ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org"
<ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
Sylwester Nawrocki
<s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Jacek Anaszewski
<j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
Jaehoon Chung
<jh80.chung-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 2/2] DT: Add binding documentation for CM36651 proximity/light sensor
Date: Thu, 26 Sep 2013 11:35:25 +0900 [thread overview]
Message-ID: <52439D6D.6030104@samsung.com> (raw)
In-Reply-To: <20130920094010.GG17453-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
Thank you for review.
I revised on your advice.
I will send v3 patch in the course of today.
reply about your question inline
> On Mon, Sep 09, 2013 at 07:10:41AM +0100, Beomho Seo wrote:
>> This patch add device tree binding documentation for CM36651
>> proximity/light sensor.
>>
>> Signed-off-by: Beomho Seo <beomho.seo-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>> ---
>> .../devicetree/bindings/iio/light/cm36651.txt | 24
>> ++++++++++++++++++++
>> .../devicetree/bindings/vendor-prefixes.txt | 1 +
>> 2 files changed, 25 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/iio/light/cm36651.txt
>>
>> diff --git a/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> b/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> new file mode 100644
>> index 0000000..3a6ba38
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/iio/light/cm36651.txt
>> @@ -0,0 +1,24 @@
>> +* Capella CM36651 I2C Proximity and Color Light sensor
>> +
>> +Required properties:
>> +- compatible: must be "capella,cm36651"
>> +- reg: the I2C address of the device
>> +- interrupts: interrupt to which the chip is connected
>
> Nit: I'd prefer something like the below:
>
> - interrupts: interrupt-specifier for the sole interrupt generated by
> the device.
>
>> +- vled-supply: regulator for the sensor device, as covered
>> + in ../../regulator/regulator.txt
>
> I assume by the name that this is the regulator for the LED that's used
> alongside the sensor, rather than for the sensor itself?
>
> Is the LED part of the CM36651 unit, or is it external? I couldn't find
> any documentation for the unit.
>
vled_suppy is the regulator for the IR LED. In order to cm36651 manual, IR_LED part of the cm36651 unit.
>> +
>> +Example:
>> +
>> + i2c_cm36651: i2c-gpio {
>> + /* ... */
>> +
>> + cm36651@18 {
>> + compatible = "capella,cm36651";
>> + reg = <0x18>;
>> + interrupt-parent = <&gpx0>;
>> + interrupts = <2 0>;
>> + vled-supply = <&ps_als_reg>;
>> + };
>> +
>> + /* ... */
>> + };
>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
>> b/Documentation/devicetree/bindings/vendor-prefixes.txt
>> index ec4d713..044796d 100644
>> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
>> @@ -17,6 +17,7 @@ brcm Broadcom Corporation
>> cavium Cavium, Inc.
>> chrp Common Hardware Reference Platform
>> cirrus Cirrus Logic, Inc.
>> +capella Capella Microsystems, Inc
>
> The vendor prefix looks OK to me. However, it should apper before cavium
> to maintain the ordering of the file.
>
> Thanks,
> Mark.
>
>> cortina Cortina Systems, Inc.
>> dallas Maxim Integrated Products (formerly Dallas Semiconductor)
>> davicom DAVICOM Semiconductor, Inc.
>> --
>> 1.7.9.5
>>
>> --
>> Beomho Seo, Assistant Engineer
>> System S/W Lab., S/W Platform Team, Software Center
>> Samsung Electronics
>>
>
--
Best Regards,
Beomho Seo, Assistant Engineer
System S/W Lab., S/W Platform Team, Software Center
Samsung Electronics
next prev parent reply other threads:[~2013-09-26 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 6:10 [PATCH 2/2] DT: Add binding documentation for CM36651 proximity/light sensor Beomho Seo
2013-09-09 6:10 ` Beomho Seo
2013-09-20 9:40 ` Mark Rutland
2013-09-20 9:40 ` Mark Rutland
2013-09-26 2:35 ` Beomho Seo [this message]
2013-09-26 2:35 ` Beomho Seo
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=52439D6D.6030104@samsung.com \
--to=beomho.seo@samsung.com \
--cc=Pawel.Moll@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=j.anaszewski@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=s.nawrocki@samsung.com \
--cc=warren@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.