All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	sebastian.hesselbarth@googlemail.com, w.sang@pengutronix.de,
	linux-i2c@vger.kernel.org,
	linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCHv3] I2C: MV64XXX: Add Device Tree support
Date: Mon, 16 Jul 2012 14:37:14 +0200	[thread overview]
Message-ID: <20120716123714.GG2489@lunn.ch> (raw)
In-Reply-To: <20120716142019.3f6cdc26@skate>

On Mon, Jul 16, 2012 at 02:20:19PM +0200, Thomas Petazzoni wrote:
> Le Mon, 16 Jul 2012 11:16:45 +0200,
> Andrew Lunn <andrew@lunn.ch> a ??crit :
> 
> > + - reg             : Offset and length of the register set for the device
> > + - compatible      : Should be "marvell,mv64xxx-i2c"
> > + - interrupts      : Te interrupt number
> 
>                         The
> 
> > +		i2c@11000 {
> > +			compatible = "marvell,mv64xxx-i2c";
> > +			reg = <0x11000 0x20>;
> > +			#address-cells = <1>;
> > +			#size-cells = <0>;
> > +			interrupts = <29>;
> > +			clock-frequency = <400000>;
> > +			timeout-ms = <1000>;
> > +			status = "disable";
> 
> This should be "disabled".

Thanks.

> The #ifdef machinery in the ->probe() function looks a bit ugly, but I
> guess this can be cleaned up once all platforms using this driver will
> have been converted to DT + clock framework.

Yes, it is ugly :-(

The ARM platforms are moving in the right direction. They all have
clock framework support and only mv78xx0 has nobody working on DT, as
far as i know.

I've no idea if anybody is still working on the powerpc platforms.
There are two _defconfig files that use it.

     Andrew

WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3] I2C: MV64XXX: Add Device Tree support
Date: Mon, 16 Jul 2012 14:37:14 +0200	[thread overview]
Message-ID: <20120716123714.GG2489@lunn.ch> (raw)
In-Reply-To: <20120716142019.3f6cdc26@skate>

On Mon, Jul 16, 2012 at 02:20:19PM +0200, Thomas Petazzoni wrote:
> Le Mon, 16 Jul 2012 11:16:45 +0200,
> Andrew Lunn <andrew@lunn.ch> a ??crit :
> 
> > + - reg             : Offset and length of the register set for the device
> > + - compatible      : Should be "marvell,mv64xxx-i2c"
> > + - interrupts      : Te interrupt number
> 
>                         The
> 
> > +		i2c at 11000 {
> > +			compatible = "marvell,mv64xxx-i2c";
> > +			reg = <0x11000 0x20>;
> > +			#address-cells = <1>;
> > +			#size-cells = <0>;
> > +			interrupts = <29>;
> > +			clock-frequency = <400000>;
> > +			timeout-ms = <1000>;
> > +			status = "disable";
> 
> This should be "disabled".

Thanks.

> The #ifdef machinery in the ->probe() function looks a bit ugly, but I
> guess this can be cleaned up once all platforms using this driver will
> have been converted to DT + clock framework.

Yes, it is ugly :-(

The ARM platforms are moving in the right direction. They all have
clock framework support and only mv78xx0 has nobody working on DT, as
far as i know.

I've no idea if anybody is still working on the powerpc platforms.
There are two _defconfig files that use it.

     Andrew

  reply	other threads:[~2012-07-16 12:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16  9:16 [PATCHv3] I2C: MV64XXX: Add Device Tree support Andrew Lunn
2012-07-16  9:16 ` Andrew Lunn
2012-07-16  9:16 ` Andrew Lunn
2012-07-16  9:16   ` Andrew Lunn
2012-07-16 12:20   ` Thomas Petazzoni
2012-07-16 12:20     ` Thomas Petazzoni
2012-07-16 12:37     ` Andrew Lunn [this message]
2012-07-16 12:37       ` Andrew Lunn
2012-07-20 10:35   ` Wolfram Sang
2012-07-20 10:35     ` Wolfram Sang
2012-07-20 11:17     ` Andrew Lunn
2012-07-20 11:17       ` Andrew Lunn

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=20120716123714.GG2489@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=sebastian.hesselbarth@googlemail.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=w.sang@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.