On Tue, Nov 26, 2013 at 01:05:53PM +, Charles Keepax wrote:
> On Fri, Nov 08, 2013 at 09:59:28AM -0700, Stephen Warren wrote:
> > That all said, I wonder if the I2C core shouldn't do something like the
> > following inside i2c_add_adapter():
> >
> > if (!adap->dev.of_node &&
Thank you very much!
I am sorry and will try to make it better next time.
On 11/28/2013 09:50 AM, Wolfram Sang wrote:
> On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
>> In order to find I2C devices in the device tree, the platform nodes
>> have to be known by the I2C core. This
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
> In order to find I2C devices in the device tree, the platform nodes
> have to be known by the I2C core. This requires setting the
> dev.of_node parameter of the adapter.
>
> Signed-off-by: Florian Meier
Fixed up for you and
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This requires setting the
dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier florian.me...@koalo.de
Fixed up
Thank you very much!
I am sorry and will try to make it better next time.
On 11/28/2013 09:50 AM, Wolfram Sang wrote:
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This
On Tue, Nov 26, 2013 at 01:05:53PM +, Charles Keepax wrote:
On Fri, Nov 08, 2013 at 09:59:28AM -0700, Stephen Warren wrote:
That all said, I wonder if the I2C core shouldn't do something like the
following inside i2c_add_adapter():
if (!adap-dev.of_node adap-dev.parent)
On Fri, Nov 08, 2013 at 09:59:28AM -0700, Stephen Warren wrote:
> On 11/08/2013 02:49 AM, Florian Meier wrote:
> > In order to find I2C devices in the device tree, the platform nodes
> > have to be known by the I2C core. Analogous to the i2c-omap driver
> > this requires setting the dev.of_node
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
> In order to find I2C devices in the device tree, the platform nodes
> have to be known by the I2C core. This requires setting the
> dev.of_node parameter of the adapter.
>
> Signed-off-by: Florian Meier
Malformed patch, please
On Mon, Nov 25, 2013 at 09:01:50AM +0100, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This requires setting the
dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier florian.me...@koalo.de
Malformed
On Fri, Nov 08, 2013 at 09:59:28AM -0700, Stephen Warren wrote:
On 11/08/2013 02:49 AM, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. Analogous to the i2c-omap driver
this requires setting the dev.of_node parameter
On 11/08/2013 09:59 AM, Stephen Warren wrote:
> On 11/08/2013 02:49 AM, Florian Meier wrote:
>> In order to find I2C devices in the device tree, the platform nodes
>> have to be known by the I2C core. Analogous to the i2c-omap driver
>> this requires setting the dev.of_node parameter of the
On 11/25/2013 01:01 AM, Florian Meier wrote:
> In order to find I2C devices in the device tree, the platform nodes
> have to be known by the I2C core. This requires setting the
> dev.of_node parameter of the adapter.
Acked-by: Stephen Warren
Tested-by: Stephen Warren
(Interestingly, I just
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This requires setting the
dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier
---
Since the general approach is not easy enough
(see [PATCH] i2c: Fallback to of_node of parent),
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This requires setting the
dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier florian.me...@koalo.de
---
Since the general approach is not easy enough
(see [PATCH] i2c: Fallback
On 11/25/2013 01:01 AM, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. This requires setting the
dev.of_node parameter of the adapter.
Acked-by: Stephen Warren swar...@wwwdotorg.org
Tested-by: Stephen Warren
On 11/08/2013 09:59 AM, Stephen Warren wrote:
On 11/08/2013 02:49 AM, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. Analogous to the i2c-omap driver
this requires setting the dev.of_node parameter of the adapter.
On 11/08/2013 02:49 AM, Florian Meier wrote:
> In order to find I2C devices in the device tree, the platform nodes
> have to be known by the I2C core. Analogous to the i2c-omap driver
> this requires setting the dev.of_node parameter of the adapter.
(CCing the I2C maintainers...)
> diff --git
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. Analogous to the i2c-omap driver
this requires setting the dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier
---
I don't know if this is really necessary, but for me it does
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. Analogous to the i2c-omap driver
this requires setting the dev.of_node parameter of the adapter.
Signed-off-by: Florian Meier florian.me...@koalo.de
---
I don't know if this is really necessary,
On 11/08/2013 02:49 AM, Florian Meier wrote:
In order to find I2C devices in the device tree, the platform nodes
have to be known by the I2C core. Analogous to the i2c-omap driver
this requires setting the dev.of_node parameter of the adapter.
(CCing the I2C maintainers...)
diff --git
20 matches
Mail list logo
