From: Noralf Tronnes <notro@tronnes.org>
To: Matthias Klein <matthias.klein@linux.com>,
linux-rpi-kernel@lists.infradead.org, swarren@wwwdotorg.org,
lee@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+
Date: Thu, 06 Nov 2014 20:36:30 +0100 [thread overview]
Message-ID: <545BCDBE.9020200@tronnes.org> (raw)
In-Reply-To: <1415231123-920-1-git-send-email-matthias.klein@linux.com>
Den 06.11.2014 00:45, skrev Matthias Klein:
> The model B and B+ differ in the GPIO lines for ACT and PWR leds, and the
> I2S interface.
>
> Signed-off-by: Matthias Klein <matthias.klein@linux.com>
> ---
> Changes in v2:
> - move the common parts between the B and B+ model into the new bcm2835-rpi.dtsi file
>
> - add the I2S signals to the B+ file which fix the problem that USB is not working
> with the current bcm2835-rpi-b.dts file on the B+.
> ---
<snip>
> +&gpio {
> + pinctrl-names = "default";
> +
> + gpioout: gpioout {
> + brcm,pins = <6>;
> + brcm,function = <1>; /* GPIO out */
> + };
> +
> + alt0: alt0 {
> + brcm,pins = <0 1 2 3 4 5 7 8 9 10 11 14 15 40 45>;
> + brcm,function = <4>; /* alt0 */
> + };
> +
> + alt3: alt3 {
> + brcm,pins = <48 49 50 51 52 53>;
> + brcm,function = <7>; /* alt3 */
> + };
> +};
AFAIK these pins will always be configured regardless of whether they
are used by a driver or not.
Could we do something like this for SPI and I2C, configuring only when
needed?
&gpio {
spi_pins: spi_pins {
brcm,pins = <7 8 9 10 11>;
brcm,function = <4>; /* alt0 */
};
i2c0_pins: i2c0_pins {
brcm,pins = <0 1>;
brcm,function = <4>;
};
i2c1_pins: i2c1_pins {
brcm,pins = <2 3>;
brcm,function = <4>;
};
};
&spi {
pinctrl-names = "default";
pinctrl-0 = <&spi_pins>;
};
&i2c0 {
pinctrl-names = "default";
pinctrl-0 = <&i2c0_pins>;
clock-frequency = <100000>;
};
&i2c1 {
pinctrl-names = "default";
pinctrl-0 = <&i2c1_pins>;
clock-frequency = <100000>;
};
> +
> +&i2c0 {
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
> +&i2c1 {
> + status = "okay";
> + clock-frequency = <100000>;
> +};
> +
Should the I2C busses be enabled by default? On Raspian, i2c is disabled
by blacklisting the module (/etc/modprobe.d/raspi-blacklist.conf).
At least i2c0 should be left disabled due to the HAT EEPROM and camera.
The bus number has also changed with revisions:
http://www.raspberrypi.org/forums/viewtopic.php?p=603950#p603950
next prev parent reply other threads:[~2014-11-06 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 23:45 [PATCH v2] ARM: bcm2835: add device tree for Raspberry Pi model B+ Matthias Klein
2014-11-06 5:11 ` Stephen Warren
2014-11-18 21:15 ` Matthias Klein
2014-11-06 5:29 ` Stephen Warren
2014-11-06 18:15 ` Matthias Klein
2014-11-06 19:01 ` Stephen Warren
2014-11-06 19:36 ` Noralf Tronnes [this message]
2014-11-07 4:22 ` Stephen Warren
2014-11-07 16:20 ` Noralf Tronnes
[not found] ` <CAE8Q9tBDxq9W=Vh0LRCRNR+Dj+5PrWyzK+GBdMDM=1kq84mFTA@mail.gmail.com>
2014-11-07 17:12 ` Gordon Hollingworth
2014-11-08 6:17 ` Stephen Warren
2014-11-08 8:03 ` Gordon Hollingworth
2014-11-08 6:12 ` Stephen Warren
2014-11-19 15:29 ` Lee Jones
2014-11-19 17:08 ` Stephen Warren
2014-11-19 17:29 ` Lee Jones
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=545BCDBE.9020200@tronnes.org \
--to=notro@tronnes.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=matthias.klein@linux.com \
--cc=swarren@wwwdotorg.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.