From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: r8a7743: Add IIC cores to dtsi
Date: Thu, 10 Aug 2017 13:24:11 +0200 [thread overview]
Message-ID: <20170810112411.GA4380@katana> (raw)
In-Reply-To: <20170810080121.GE16647@verge.net.au>
> > >+ i2c6: i2c at e60b0000 {
> >
> > I'd use iic0 as the label.
>
> I have no preference here other than that we try to be consistent
> in DT for different R-Car SoCs. Wolfram, do you have an opinion on this?
Back then, for M2-W, I decided to go with the schematics/datasheets.
And those mentioned i2c6 rather than iic0. For that reason, the comment
"/* The memory map in the User's Manual maps the cores to bus numbers */"
exists in r8a7791.dtsi. Dunno the manual of this SoC here.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170810/bb3d03e1/attachment.sig>
next prev parent reply other threads:[~2017-08-10 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 12:46 [PATCH 2/2] ARM: dts: r8a7743: Add IIC cores to dtsi Biju Das
2017-08-09 8:56 ` Simon Horman
2017-08-09 9:17 ` Sergei Shtylyov
2017-08-09 9:21 ` Biju Das
2017-08-10 8:01 ` Simon Horman
2017-08-10 11:24 ` Wolfram Sang [this message]
2017-08-10 13:49 ` Chris Paterson
2017-08-11 8:48 ` Simon Horman
2017-08-14 14:15 ` Geert Uytterhoeven
2017-08-22 12:20 ` Sergei Shtylyov
2017-08-14 9:53 ` [PATCH v2] ARM: dts: r8a7743: add " Biju Das
2017-08-22 9:10 ` Chris Paterson
2017-08-22 12:23 ` Sergei Shtylyov
2017-08-30 7:32 ` Simon Horman
2017-08-30 7:46 ` Chris Paterson
2017-09-06 13:52 ` [PATCH v3] ARM: dts: r8a7743: Add " Chris Paterson
2017-09-11 7:25 ` Simon Horman
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=20170810112411.GA4380@katana \
--to=wsa@the-dreams.de \
--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