From: antoine.tenart@free-electrons.com (Antoine Ténart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: dts: berlin: enable i2c0 and i2c2
Date: Wed, 4 Jun 2014 19:37:01 +0200 [thread overview]
Message-ID: <20140604173701.GC12859@kwain> (raw)
In-Reply-To: <20140604170340.GI6892@lunn.ch>
On Wed, Jun 04, 2014 at 07:03:40PM +0200, Andrew Lunn wrote:
> On Wed, Jun 04, 2014 at 06:48:41PM +0200, Antoine T?nart wrote:
> >
> > On Tue, Jun 03, 2014 at 10:05:22AM +0200, Andrew Lunn wrote:
> > > On Tue, Jun 03, 2014 at 09:33:10AM +0200, Antoine T?nart wrote:
> > > > Enable the I2C0 and I2C2 for the Marvell Berlin BG2G DMP. I2C1 and I2C3
> > > > are also working on this board, but no devices seemed to be there.
> > >
> > > Does this mean that IC0 and I2C2 have devices on them? Could you also
> > > add nodes for the devices?
> >
> > No devices I can add for now. I you prefer we can drop this patch, keep
> > the other one and enable i2c nodes for the BG2Q DMP when they will be
> > needed.
>
> I was just wondering how you tested it, without having any devices?
I tested with the i2ctools. I could see one device on each bus at the
address it should be. I also tested the pin muxing configurations.
I don't have lots of information on these I2C buses, at least my test
results match what I know.
> Is it that the devices on the bus don't have mainline drivers?
Not with I2C support.
Antoine
--
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: "Antoine Ténart" <antoine.tenart@free-electrons.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
devicetree@vger.kernel.org,
"Antoine Ténart" <antoine.tenart@free-electrons.com>,
linux-kernel@vger.kernel.org,
alexandre.belloni@free-electrons.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org,
sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH 2/2] ARM: dts: berlin: enable i2c0 and i2c2
Date: Wed, 4 Jun 2014 19:37:01 +0200 [thread overview]
Message-ID: <20140604173701.GC12859@kwain> (raw)
In-Reply-To: <20140604170340.GI6892@lunn.ch>
On Wed, Jun 04, 2014 at 07:03:40PM +0200, Andrew Lunn wrote:
> On Wed, Jun 04, 2014 at 06:48:41PM +0200, Antoine Ténart wrote:
> >
> > On Tue, Jun 03, 2014 at 10:05:22AM +0200, Andrew Lunn wrote:
> > > On Tue, Jun 03, 2014 at 09:33:10AM +0200, Antoine Ténart wrote:
> > > > Enable the I2C0 and I2C2 for the Marvell Berlin BG2G DMP. I2C1 and I2C3
> > > > are also working on this board, but no devices seemed to be there.
> > >
> > > Does this mean that IC0 and I2C2 have devices on them? Could you also
> > > add nodes for the devices?
> >
> > No devices I can add for now. I you prefer we can drop this patch, keep
> > the other one and enable i2c nodes for the BG2Q DMP when they will be
> > needed.
>
> I was just wondering how you tested it, without having any devices?
I tested with the i2ctools. I could see one device on each bus at the
address it should be. I also tested the pin muxing configurations.
I don't have lots of information on these I2C buses, at least my test
results match what I know.
> Is it that the devices on the bus don't have mainline drivers?
Not with I2C support.
Antoine
--
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: "Antoine Ténart" <antoine.tenart@free-electrons.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "Antoine Ténart" <antoine.tenart@free-electrons.com>,
sebastian.hesselbarth@gmail.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
alexandre.belloni@free-electrons.com, jszhang@marvell.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: dts: berlin: enable i2c0 and i2c2
Date: Wed, 4 Jun 2014 19:37:01 +0200 [thread overview]
Message-ID: <20140604173701.GC12859@kwain> (raw)
In-Reply-To: <20140604170340.GI6892@lunn.ch>
On Wed, Jun 04, 2014 at 07:03:40PM +0200, Andrew Lunn wrote:
> On Wed, Jun 04, 2014 at 06:48:41PM +0200, Antoine Ténart wrote:
> >
> > On Tue, Jun 03, 2014 at 10:05:22AM +0200, Andrew Lunn wrote:
> > > On Tue, Jun 03, 2014 at 09:33:10AM +0200, Antoine Ténart wrote:
> > > > Enable the I2C0 and I2C2 for the Marvell Berlin BG2G DMP. I2C1 and I2C3
> > > > are also working on this board, but no devices seemed to be there.
> > >
> > > Does this mean that IC0 and I2C2 have devices on them? Could you also
> > > add nodes for the devices?
> >
> > No devices I can add for now. I you prefer we can drop this patch, keep
> > the other one and enable i2c nodes for the BG2Q DMP when they will be
> > needed.
>
> I was just wondering how you tested it, without having any devices?
I tested with the i2ctools. I could see one device on each bus at the
address it should be. I also tested the pin muxing configurations.
I don't have lots of information on these I2C buses, at least my test
results match what I know.
> Is it that the devices on the bus don't have mainline drivers?
Not with I2C support.
Antoine
--
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-04 17:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 7:33 [PATCH 0/2] ARM: berlin: BG2Q I2C support Antoine Ténart
2014-06-03 7:33 ` Antoine Ténart
2014-06-03 7:33 ` [PATCH 1/2] ARM: dts: berlin: add I2C nodes for BG2Q Antoine Ténart
2014-06-03 7:33 ` Antoine Ténart
2014-06-16 11:22 ` Sebastian Hesselbarth
2014-06-16 11:22 ` Sebastian Hesselbarth
2014-06-16 11:22 ` Sebastian Hesselbarth
2014-06-03 7:33 ` [PATCH 2/2] ARM: dts: berlin: enable i2c0 and i2c2 Antoine Ténart
2014-06-03 7:33 ` Antoine Ténart
2014-06-03 8:05 ` Andrew Lunn
2014-06-03 8:05 ` Andrew Lunn
2014-06-03 8:05 ` Andrew Lunn
2014-06-04 16:48 ` Antoine Ténart
2014-06-04 16:48 ` Antoine Ténart
2014-06-04 16:48 ` Antoine Ténart
2014-06-04 17:03 ` Andrew Lunn
2014-06-04 17:03 ` Andrew Lunn
2014-06-04 17:03 ` Andrew Lunn
2014-06-04 17:37 ` Antoine Ténart [this message]
2014-06-04 17:37 ` Antoine Ténart
2014-06-04 17:37 ` Antoine Ténart
2014-06-16 11:23 ` Sebastian Hesselbarth
2014-06-16 11:23 ` Sebastian Hesselbarth
2014-06-16 11:23 ` Sebastian Hesselbarth
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=20140604173701.GC12859@kwain \
--to=antoine.tenart@free-electrons.com \
--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 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.