lkml.org 
[lkml]   [2014]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+

Am 06.11.2014 um 06:29 schrieb Stephen Warren:
> I guess we should have separate device trees for those, since there are
> some differences in the GPIO and I2C channel usage. That'd leave us with:
>
> bcm2835-rpi-b.dts (Pin3=GPIO0, Pin5=GPIO1, Pin13=GPIO21, I2C-0)
> bcm2835-rpi-b-rev2.dts (Pin3=GPIO1, Pin5=GPIO2, Pin13=GPIO27, 12C-1)
I think for these differences separate device trees are not needed.
These pins are all at the moment configured as ALT0. Both I2C buses are
configured for I2C,
therefore I doesn't matter which one is wired to the gpio header.

But for clarity it would be better to have a separate device tree for
each model.


When a gpio signal (which is configured in device tree as ALT0) is used
as e.g. plain gpio output, does the kernel the reconfiguration from ALT0
to gpio output?
Or must the gpio signal be configured as output in the device tree?

Is is possible to set at the brcm,function/brcm,pins gpio definition
also the voltage level of an gpio output for e.g. the LAN_RUN signal?


How do we want to continue?
Is my patch OK, or should I try to write a device tree for every model
where every gpio signal is defined?


Best regards,
Matthias



\
 
 \ /
  Last update: 2014-11-06 19:21    [W:0.129 / U:0.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site