linux-kernel - Re: [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 06 Nov 2014 19:15:00 +0100
From:	Matthias Klein <matthias.klein@...ux.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	linux-rpi-kernel@...ts.infradead.org, lee@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/