linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] arm: shmobile: r7s72100: add nodes for i2c controllers to dtsi
Date: Tue, 17 Dec 2013 22:13:09 +0000	[thread overview]
Message-ID: <20131217221309.GD1196@katana> (raw)
In-Reply-To: <1632121.4oJZuIln5n@avalon>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Hi,

On Tue, Dec 17, 2013 at 10:55:31PM +0100, Laurent Pinchart wrote:
> Hi Wolfram,
> 
> Thank you for the patch.
> 
> On Tuesday 17 December 2013 22:44:36 Wolfram Sang wrote:
> > From: Wolfram Sang <wsa@sang-engineering.com>
> > 
> > I decided to put the pinmuxing into the dtsi file since there is only
> > one pinmux posiibility which one probably wants to have when using the
> > bus.

I tried to explain here why the pin-groups are in the dtsi.

> > +		riic0_pins: i2c0 {
> > +			renesas,groups = "riic0_scl_p1_0", "riic0_sda_p1_1";
> > +			renesas,function = "riic0";
> > +		};
> > +
> > +		riic1_pins: i2c1 {
> > +			renesas,groups = "riic1_scl_p1_2", "riic1_sda_p1_3";
> > +			renesas,function = "riic1";
> > +		};
> > +
> > +		riic2_pins: i2c2 {
> > +			renesas,groups = "riic2_scl_p1_4", "riic2_sda_p1_5";
> > +			renesas,function = "riic2";
> > +		};
> > +
> > +		riic3_pins: i2c3 {
> > +			renesas,groups = "riic3_scl_p1_6", "riic3_sda_p1_7";
> > +			renesas,function = "riic3";
> > +		};
> 
> The SoC allows other options for the I2C pin groups. Instead of declaring all 
> possible groups here, I think we should thus only add the groups that are 
> really used to the board .dts files.

Really? Couldn't find any. This is why I included it here: since it is
the only option, people probably want to use it when they activate the
bus.

> > +		clock-frequency = <100000>;
> 
> Isn't that a board-specific property ?

It is meant as a sane default. Can be overridden.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-12-17 22:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 21:44 [PATCH 0/5] arm: shmobile: r7s72100: add native i2c support Wolfram Sang
2013-12-17 21:44 ` [PATCH 1/5] pinctrl: r7s72100: add riic groups Wolfram Sang
2013-12-17 21:47   ` Wolfram Sang
2013-12-17 21:48   ` Laurent Pinchart
2013-12-17 21:44 ` [PATCH 2/5] arm: shmobile: r7s72100: add i2c clocks Wolfram Sang
2013-12-18 11:38   ` Sergei Shtylyov
2013-12-18 11:43     ` Wolfram Sang
2013-12-18 11:53       ` Sergei Shtylyov
2013-12-18 12:15         ` Wolfram Sang
2013-12-18 13:49           ` Simon Horman
2013-12-18 14:02             ` Sergei Shtylyov
2013-12-18 14:44               ` Magnus Damm
2013-12-18 15:13                 ` Sergei Shtylyov
2013-12-18 21:00             ` Wolfram Sang
2013-12-17 21:44 ` [PATCH 3/5] arm: shmobile: r7s72100: add nodes for i2c controllers to dtsi Wolfram Sang
2013-12-17 21:55   ` Laurent Pinchart
2013-12-17 22:13     ` Wolfram Sang [this message]
2013-12-17 22:16       ` Laurent Pinchart
2013-12-17 21:44 ` [PATCH 4/5] arm: shmobile: genmai: adapt dts to use native i2c driver Wolfram Sang
2013-12-17 21:57   ` Laurent Pinchart
2013-12-18 11:41   ` Sergei Shtylyov
2013-12-17 21:44 ` [PATCH 5/5] i2c: riic: add driver Wolfram Sang
2013-12-18  8:42   ` Geert Uytterhoeven

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=20131217221309.GD1196@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;
as well as URLs for NNTP newsgroup(s).