From: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
To: Karol Lewandowski <k.lewandowsk-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Cc: Jean-Christophe PLAGNIOL-VILLARD
<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] i2c/gpio-i2c add: add DT support
Date: Mon, 13 Feb 2012 23:14:01 +0000 [thread overview]
Message-ID: <20120213231401.GE2999@freya.fluff.org> (raw)
In-Reply-To: <4F301E25.5060507-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
On Mon, Feb 06, 2012 at 07:38:29PM +0100, Karol Lewandowski wrote:
> On 05.02.2012 11:38, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> Hi!
>
> >+Device-Tree bindings for i2c gpio driver
> >+
> >+Required properties:
> >+ - compatible = "gpio-i2c";
>
> Driver name is "i2c-gpio" in file i2c-gpio.c. Previous version of
> patch adding DT-support (prepared by Thomas Chou[1]) used i2c-gpio -
> could we stick to that name?
>
> [1] https://lkml.org/lkml/2011/2/23/584
>
> >+ - gpios: sda and scl gpio
> >+
> >+
> >+Optional properties:
> >+ - gpio-i2c,sda_is_open_drain: sda as open drain
> >+ - gpio-i2c,scl_is_open_drain: scl as open drain
> >+ - gpio-i2c,scl_is_output_only: scl as output only
>
> Most of DT-properties I've seen used hyphen, not underscore. Could
> we stick to that convention?
>
> (Nitpick: I think that "is" in property names is redundant too.)
>
> >+ - udelay: half clock cycle time in us (may depend on each platform)
>
> Could we use "clock-frequency" as Grant have suggested during review
> of previous patch to i2c-gpio?
I'm with Grant on that, it would be nice to have a reasonably sane set of
default i2c dt bindings that everyone uses.
WARNING: multiple messages have this Message-ID (diff)
From: ben-i2c@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] i2c/gpio-i2c add: add DT support
Date: Mon, 13 Feb 2012 23:14:01 +0000 [thread overview]
Message-ID: <20120213231401.GE2999@freya.fluff.org> (raw)
In-Reply-To: <4F301E25.5060507@samsung.com>
On Mon, Feb 06, 2012 at 07:38:29PM +0100, Karol Lewandowski wrote:
> On 05.02.2012 11:38, Jean-Christophe PLAGNIOL-VILLARD wrote:
>
> Hi!
>
> >+Device-Tree bindings for i2c gpio driver
> >+
> >+Required properties:
> >+ - compatible = "gpio-i2c";
>
> Driver name is "i2c-gpio" in file i2c-gpio.c. Previous version of
> patch adding DT-support (prepared by Thomas Chou[1]) used i2c-gpio -
> could we stick to that name?
>
> [1] https://lkml.org/lkml/2011/2/23/584
>
> >+ - gpios: sda and scl gpio
> >+
> >+
> >+Optional properties:
> >+ - gpio-i2c,sda_is_open_drain: sda as open drain
> >+ - gpio-i2c,scl_is_open_drain: scl as open drain
> >+ - gpio-i2c,scl_is_output_only: scl as output only
>
> Most of DT-properties I've seen used hyphen, not underscore. Could
> we stick to that convention?
>
> (Nitpick: I think that "is" in property names is redundant too.)
>
> >+ - udelay: half clock cycle time in us (may depend on each platform)
>
> Could we use "clock-frequency" as Grant have suggested during review
> of previous patch to i2c-gpio?
I'm with Grant on that, it would be nice to have a reasonably sane set of
default i2c dt bindings that everyone uses.
next prev parent reply other threads:[~2012-02-13 23:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 10:38 [PATCH 1/4] i2c/gpio-i2c add: add DT support Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` [PATCH 2/4] ARM: at91s: sam9g20 add i2c " Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` [PATCH 3/4] ARM: at91: usb_a9g20 add DT i2c support Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` [PATCH 4/4] ARM: at91: sam9g45 add i2c DT support Jean-Christophe PLAGNIOL-VILLARD
2012-02-05 10:38 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <1328438337-21185-1-git-send-email-plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
2012-02-06 16:09 ` [PATCH 1/4] i2c/gpio-i2c add: add " Mark Brown
2012-02-06 16:09 ` Mark Brown
[not found] ` <20120206160907.GG10173-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-02-07 2:56 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-07 2:56 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20120207025624.GB15647-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-02-07 11:25 ` Mark Brown
2012-02-07 11:25 ` Mark Brown
2012-02-06 18:38 ` Karol Lewandowski
2012-02-06 18:38 ` Karol Lewandowski
[not found] ` <4F301E25.5060507-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-02-06 19:15 ` Jean Delvare
2012-02-06 19:15 ` Jean Delvare
2012-02-07 3:25 ` Jean-Christophe PLAGNIOL-VILLARD
2012-02-07 3:25 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20120207032533.GC15647-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-02-07 15:35 ` Karol Lewandowski
2012-02-07 15:35 ` Karol Lewandowski
2012-02-13 23:14 ` Ben Dooks [this message]
2012-02-13 23:14 ` Ben Dooks
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=20120213231401.GE2999@freya.fluff.org \
--to=ben-i2c-elnmno+kys3ytjvyw6ydsg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=k.lewandowsk-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.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.