From: valentin.longchamp@keymile.com (Valentin Longchamp)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: kirkwood: add kirkwood-km_fixedeth DTS file
Date: Thu, 15 May 2014 17:07:48 +0200 [thread overview]
Message-ID: <5374D844.7070300@keymile.com> (raw)
In-Reply-To: <20140515130831.GC32684@lunn.ch>
On 05/15/2014 03:08 PM, Andrew Lunn wrote:
>> + i2c at 0 {
>> + compatible = "i2c-gpio";
>> + gpios = < &gpio0 8 GPIO_ACTIVE_HIGH /* sda */
>> + &gpio0 9 GPIO_ACTIVE_HIGH>; /* scl */
>> + i2c-gpio,delay-us = <2>; /* ~100 kHz */
>> + };
>
> Hi Valentin
>
> Anything interesting on the i2c bus?
Well yes, but this is then board specific (for all the Keymile variants of the
reference design). Since all these variants are not mainlined, I have added
nothing yet, but this may come later since we are currently reworking our I2C
bus support/topology.
>
> Does this SoC not have the hardware i2c? I don't see a node for it
> here.
>
The SoC does have the hardware I2C, but we don't use it and use the above
bitbang one instead. I was not in the company when this was chosen/designed. The
main reason is that the Kirkwood's one is not fast enough (clk < 96 kHz) for our
usage (we have A LOT of different things on this BUS, some must be quick - the
bus speed gets changed from (uuuurrghhh) userpace - and this is a NIGHTMARE,
believe me).
Valentin
prev parent reply other threads:[~2014-05-15 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:48 [PATCH 0/3] Update the Keymile kirkwood DTS files Valentin Longchamp
2014-05-15 9:48 ` [PATCH 1/3] ARM: dts: kirkwood: resynch 98dx4122 dtsi Valentin Longchamp
2014-05-15 10:35 ` Sebastian Hesselbarth
2014-05-15 11:11 ` Valentin Longchamp
2014-05-15 13:24 ` Jason Cooper
2014-05-15 9:48 ` [PATCH 2/3] ARM: dts: kirkwood: enable the PCIe for km_kirkwood Valentin Longchamp
2014-05-15 9:48 ` [PATCH 3/3] ARM: dts: kirkwood: add kirkwood-km_fixedeth DTS file Valentin Longchamp
2014-05-15 10:43 ` Sebastian Hesselbarth
2014-05-15 11:04 ` Valentin Longchamp
2014-05-15 13:08 ` Andrew Lunn
2014-05-15 15:07 ` Valentin Longchamp [this message]
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=5374D844.7070300@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=linux-arm-kernel@lists.infradead.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 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).