LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Ben Dooks <ben-linux@fluff.org>,
linux-kernel@vger.kernel.org, nios2-dev@sopc.et.ntust.edu.tw,
devicetree-discuss@lists.ozlabs.org, linux-i2c@vger.kernel.org,
Albert Herranz <albert_herranz@yahoo.es>
Subject: Re: [PATCH v6] i2c-gpio: add devicetree support
Date: Fri, 25 Feb 2011 10:04:59 +0800 [thread overview]
Message-ID: <4D670E4B.6000407@wytron.com.tw> (raw)
In-Reply-To: <20110224162210.GC17735@angua.secretlab.ca>
Hi Grant,
On 02/25/2011 12:22 AM, Grant Likely wrote:
>> +Required properties:
>> +- compatible : should be "i2c-gpio".
>> +- gpios : should specify GPIOs used for SDA and SCL lines, in that order.
>> +Optional properties:
>> +- sda-is-open-drain : present if SDA gpio is open-drain.
>> +- scl-is-open-drain : present if SCL gpio is open-drain.
>> +- scl-is-output-only : present if the output driver for SCL cannot be
>> + turned off. this will prevent clock stretching from working.
>> +- speed-hz : SCL frequency.
>
> Hi Thomas,
>
> One nitpick; I just looked, and other i2c controllers are already
> using 'clock-frequency' instead of 'speed-hz' for the speed of the
> bus. I'd like to see this patch use the same terminology.
I studied 'clock-frequency' usage of existing i2c drivers before working
on this patch.
i2c-ibm_iic.c, i2c-mpc.c, i2c-ocores.c : use as bus clock frequency
input to the core.
i2c-cpm.c : use as i2c SCL output frequency.
Most other non-i2c drivers use clock-frequency as bus clock frequency
input, too.
I think the SCL freq usage in i2c-cpm.c is confusing. So I would suggest
we borrow 'speed-hz' from spi subsystem, which means the clock freq
output on the peripheral bus.
Best regards,
Thomas
next prev parent reply other threads:[~2011-02-25 2:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 15:56 [PATCH] " Thomas Chou
2011-01-31 3:26 ` Håvard Skinnemoen
2011-01-31 8:09 ` Grant Likely
2011-01-31 13:55 ` Jon Loeliger
2011-01-31 15:25 ` [PATCH 1/3] of: define dummy of_get_property if not CONFIG_OF Thomas Chou
2011-01-31 22:10 ` Grant Likely
2011-01-31 15:25 ` [PATCH 2/3] of: of_gpiochip_add is needed only for gpiolib Thomas Chou
2011-01-31 22:16 ` Grant Likely
2011-01-31 15:25 ` [PATCH 3/3 v2] i2c-gpio: add devicetree support Thomas Chou
2011-01-31 21:14 ` [3/3,v2] " Milton Miller
2011-01-31 21:29 ` Grant Likely
2011-02-03 2:26 ` [PATCH] " Thomas Chou
2011-02-03 4:24 ` Håvard Skinnemoen
2011-02-03 18:07 ` Grant Likely
2011-02-10 2:29 ` [PATCH v4] " Thomas Chou
2011-02-14 2:30 ` [PATCH v5] " Thomas Chou
2011-02-16 5:49 ` Grant Likely
2011-02-16 6:13 ` Thomas Chou
2011-02-23 1:12 ` Ben Dooks
2011-02-23 13:18 ` Thomas Chou
2011-02-24 4:00 ` [PATCH v6] " Thomas Chou
2011-02-24 16:22 ` Grant Likely
2011-02-25 2:04 ` Thomas Chou [this message]
2011-01-31 22:35 ` [PATCH] " Håvard Skinnemoen
2011-01-31 23:01 ` Grant Likely
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=4D670E4B.6000407@wytron.com.tw \
--to=thomas@wytron.com.tw \
--cc=albert_herranz@yahoo.es \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nios2-dev@sopc.et.ntust.edu.tw \
--subject='Re: [PATCH v6] i2c-gpio: add devicetree support' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).