From: Arnd Bergmann <arnd@arndb.de>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: gregkh@linuxfoundation.org, eric.piel@tremplin-utc.net,
jic23@cam.ac.uk, greg@kroah.com, akpm@linux-foundation.org,
broonie@opensource.wolfsonmicro.com, dmitry.torokhov@gmail.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca
Subject: Re: [PATCH 2/2] ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm
Date: Fri, 14 Sep 2012 08:26:06 +0000 [thread overview]
Message-ID: <201209140826.07069.arnd@arndb.de> (raw)
In-Reply-To: <1347551685-19781-3-git-send-email-anilkumar@ti.com>
On Thursday 13 September 2012, AnilKumar Ch wrote:
> Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
> lis331dlh accelerometer is connected to I2C2 bus. So this patch
> change the status to "okay" to use I2C2 bus. Also added all the
> required platform data to am335x-evm.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am335x-evm.dts | 42 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
> index 9fb59c5..9e5a878 100644
> --- a/arch/arm/boot/dts/am335x-evm.dts
> +++ b/arch/arm/boot/dts/am335x-evm.dts
> @@ -47,6 +47,15 @@
> };
> };
>
> + i2c2: i2c@4802a000 {
> + status = "okay";
> + clock-frequency = <400000>;
> +
> + lis331dlh: lis331dlh@18 {
> + reg = <0x18>;
> + };
> + };
Why do you put the "reg" property here
> dcan1: d_can@481d0000 {
> status = "okay";
> pinctrl-names = "default";
> @@ -61,6 +70,39 @@
> regulator-max-microvolt = <5000000>;
> regulator-boot-on;
> };
> +
> + lis3_reg: fixedregulator@1 {
> + compatible = "regulator-fixed";
> + regulator-name = "lis3_reg";
> + regulator-boot-on;
> + };
> +};
> +&lis331dlh {
> + compatible = "st,lis3lv02d-i2c";
and all the rest here? At least I would expect the "compatible" property
to be in the same place above.
Also, I think you should remove the "-i2c" postfix from the name, that
is already implied by the parent bus.
> + Vdd-supply = <&lis3_reg>;
> + Vdd_IO-supply = <&lis3_reg>;
> +
> + st,click-single-x;
> + st,click-single-y;
> + st,click-single-z;
> + st,click-thresh-x = <10>;
> + st,click-thresh-y = <10>;
> + st,click-thresh-z = <10>;
> + st,irq1-click;
> + st,irq2-click;
> + st,wakeup-x-lo;
> + st,wakeup-x-hi;
> + st,wakeup-y-lo;
> + st,wakeup-y-hi;
> + st,wakeup-z-lo;
> + st,wakeup-z-hi;
> + st,min-limit-x = <120>;
> + st,min-limit-y = <120>;
> + st,min-limit-z = <140>;
> + st,max-limit-x = <550>;
> + st,max-limit-y = <550>;
> + st,max-limit-z = <750>;
Is there a binding document that describes all these?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm
Date: Fri, 14 Sep 2012 08:26:06 +0000 [thread overview]
Message-ID: <201209140826.07069.arnd@arndb.de> (raw)
In-Reply-To: <1347551685-19781-3-git-send-email-anilkumar@ti.com>
On Thursday 13 September 2012, AnilKumar Ch wrote:
> Add lis331dlh device tree data to am335x-evm.dts. In AM335x EVM
> lis331dlh accelerometer is connected to I2C2 bus. So this patch
> change the status to "okay" to use I2C2 bus. Also added all the
> required platform data to am335x-evm.
>
> Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
> ---
> arch/arm/boot/dts/am335x-evm.dts | 42 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/arch/arm/boot/dts/am335x-evm.dts b/arch/arm/boot/dts/am335x-evm.dts
> index 9fb59c5..9e5a878 100644
> --- a/arch/arm/boot/dts/am335x-evm.dts
> +++ b/arch/arm/boot/dts/am335x-evm.dts
> @@ -47,6 +47,15 @@
> };
> };
>
> + i2c2: i2c at 4802a000 {
> + status = "okay";
> + clock-frequency = <400000>;
> +
> + lis331dlh: lis331dlh at 18 {
> + reg = <0x18>;
> + };
> + };
Why do you put the "reg" property here
> dcan1: d_can at 481d0000 {
> status = "okay";
> pinctrl-names = "default";
> @@ -61,6 +70,39 @@
> regulator-max-microvolt = <5000000>;
> regulator-boot-on;
> };
> +
> + lis3_reg: fixedregulator at 1 {
> + compatible = "regulator-fixed";
> + regulator-name = "lis3_reg";
> + regulator-boot-on;
> + };
> +};
> +&lis331dlh {
> + compatible = "st,lis3lv02d-i2c";
and all the rest here? At least I would expect the "compatible" property
to be in the same place above.
Also, I think you should remove the "-i2c" postfix from the name, that
is already implied by the parent bus.
> + Vdd-supply = <&lis3_reg>;
> + Vdd_IO-supply = <&lis3_reg>;
> +
> + st,click-single-x;
> + st,click-single-y;
> + st,click-single-z;
> + st,click-thresh-x = <10>;
> + st,click-thresh-y = <10>;
> + st,click-thresh-z = <10>;
> + st,irq1-click;
> + st,irq2-click;
> + st,wakeup-x-lo;
> + st,wakeup-x-hi;
> + st,wakeup-y-lo;
> + st,wakeup-y-hi;
> + st,wakeup-z-lo;
> + st,wakeup-z-hi;
> + st,min-limit-x = <120>;
> + st,min-limit-y = <120>;
> + st,min-limit-z = <140>;
> + st,max-limit-x = <550>;
> + st,max-limit-y = <550>;
> + st,max-limit-z = <750>;
Is there a binding document that describes all these?
Arnd
next prev parent reply other threads:[~2012-09-14 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 15:54 [PATCH 0/2] lis3: lis3lv02d_i2c: Add device tree support AnilKumar Ch
2012-09-13 15:54 ` AnilKumar Ch
2012-09-13 15:54 ` [PATCH 1/2] " AnilKumar Ch
2012-09-13 15:54 ` AnilKumar Ch
2012-09-13 15:54 ` [PATCH 2/2] ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm AnilKumar Ch
2012-09-13 15:54 ` AnilKumar Ch
2012-09-14 8:26 ` Arnd Bergmann [this message]
2012-09-14 8:26 ` Arnd Bergmann
2012-09-14 9:18 ` AnilKumar, Chimata
2012-09-14 9:18 ` AnilKumar, Chimata
2012-09-14 10:28 ` Arnd Bergmann
2012-09-14 10:28 ` Arnd Bergmann
[not found] ` <201209141028.38185.arnd-r2nGTMty4D4@public.gmane.org>
2012-09-14 11:16 ` AnilKumar, Chimata
2012-09-14 11:16 ` AnilKumar, Chimata
2012-09-14 15:29 ` Arnd Bergmann
2012-09-14 15:29 ` Arnd Bergmann
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=201209140826.07069.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=anilkumar@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.piel@tremplin-utc.net \
--cc=grant.likely@secretlab.ca \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@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: 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.