From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa@the-dreams.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: ARM: shmobile: "i2c<m>" vs. "iic<n>" DT nodes and pinmux
Date: Fri, 22 Aug 2014 01:32:24 +0400 [thread overview]
Message-ID: <53F66568.6030709@cogentembedded.com> (raw)
In-Reply-To: <53F643F1.9060409@cogentembedded.com>
Hello.
On 08/21/2014 11:09 PM, Sergei Shtylyov wrote:
>> "iic<n>", with DT aliases from "i2c<m>" to the "iic<n>" DT nodes.
>> On r8a7791, DT device nodes and C/DT pinmux data for IIC<n> are called
>> "i2c<m>", with DT aliases from "i2c<m>" to the "i2c<m>" DT nodes.
>> In light of the proliferation of other members of the R-Car Gen 2 families, is
>> there a plan to make this consistent?
> I can probably look at this since the SH-Mobile driver (and/or hardware?)
> is clearly of better quality than R-Car one: I'm constantly getting -ENXIO and
> -EBUSY from the latter trying to read images from ADV7180 I2C video decoder.
Indeed, on Lager reading from the same chip seems to work flawlessy.
However, I was too optimistic about R8A7791: it doesn't have IIC controller
matching I2C2. :-/
So the only thing I can do is to fix inconsistent labels in
R8A7791/Koelsch DTs if Wolfram won't beat me to it.
WBR, Sergei
prev parent reply other threads:[~2014-08-21 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 13:11 ARM: shmobile: "i2c<m>" vs. "iic<n>" DT nodes and pinmux Geert Uytterhoeven
2014-08-12 21:43 ` Wolfram Sang
2014-08-12 21:47 ` Wolfram Sang
2014-08-13 7:19 ` Geert Uytterhoeven
[not found] ` <CAMuHMdVVKOS=o-KSx1q05y_sRx5RcOMiUg8mN4fGM=UyGv1uog-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-29 10:20 ` Wolfram Sang
[not found] ` <CAMuHMdWqnMZQcRURufCxiGpbkK7ocjH8KnECxdWVPcxN-68J4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-21 19:09 ` Sergei Shtylyov
2014-08-21 21:32 ` Sergei Shtylyov [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=53F66568.6030709@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=geert@linux-m68k.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).