From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
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: Tue, 12 Aug 2014 23:47:30 +0200 [thread overview]
Message-ID: <20140812214723.GA3443@katana> (raw)
In-Reply-To: <CAMuHMdWqnMZQcRURufCxiGpbkK7ocjH8KnECxdWVPcxN-68J4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Tue, Aug 12, 2014 at 03:11:18PM +0200, Geert Uytterhoeven wrote:
> Hi,
>
> On r8a7790, DT device nodes and C/DT pinmux data for IIC<n> are called
> "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?
The 'i2c'-prefix describes the IP core handled by the rcar driver. This
core is named i2c in the datasheets.
The 'iic'-prefix describes the IP core handled by the sh-mobile-driver.
This core is named iic(b) in the datasheets.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-12 21:47 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 [this message]
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
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=20140812214723.GA3443@katana \
--to=wsa@the-dreams.de \
--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 \
/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).