From: Sergey Suloev <ssuloev@orpaltech.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Eric Anholt <eric@anholt.net>
Cc: devicetree@vger.kernel.org, Phil Elwell <phil@raspberrypi.org>,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH V4 2/3] ARM: dts: add Raspberry Pi 3 A+
Date: Sat, 12 Jan 2019 21:11:46 +0300 [thread overview]
Message-ID: <2da60463-f536-84f4-a176-4f8df30f6eaf@orpaltech.com> (raw)
In-Reply-To: <1545780008-22271-3-git-send-email-stefan.wahren@i2se.com>
Hi, Stefan,
is this patch the only update required to run Rpi3 A+ with kernel 4.20?
Thank you,
Sergey
On 12/26/18 2:20 AM, Stefan Wahren wrote:
> The Raspberry Pi 3 A+ is similar to the Pi 3 B+ but has only 512 MB RAM,
> 1 USB 2.0 port and no Ethernet.
>
> Compared to the Raspberry Pi 3 B it isn't possible to control BT_ON and
> WL_ON separately.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> arch/arm/boot/dts/Makefile | 1 +
> arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts | 175 +++++++++++++++++++++++++++++
> 2 files changed, 176 insertions(+)
> create mode 100644 arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index 78551c4..764fe91 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -79,6 +79,7 @@ dtb-$(CONFIG_ARCH_BCM2835) += \
> bcm2835-rpi-a-plus.dtb \
> bcm2835-rpi-cm1-io1.dtb \
> bcm2836-rpi-2-b.dtb \
> + bcm2837-rpi-3-a-plus.dtb \
> bcm2837-rpi-3-b.dtb \
> bcm2837-rpi-3-b-plus.dtb \
> bcm2837-rpi-cm3-io3.dtb \
> diff --git a/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
> new file mode 100644
> index 0000000..61f4e4d
> --- /dev/null
> +++ b/arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts
> @@ -0,0 +1,175 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/dts-v1/;
> +#include "bcm2837.dtsi"
> +#include "bcm2836-rpi.dtsi"
> +#include "bcm283x-rpi-usb-host.dtsi"
> +
> +/ {
> + compatible = "raspberrypi,3-model-a-plus", "brcm,bcm2837";
> + model = "Raspberry Pi 3 Model A+";
> +
> + chosen {
> + /* 8250 auxiliary UART instead of pl011 */
> + stdout-path = "serial1:115200n8";
> + };
> +
> + memory {
> + reg = <0 0x20000000>;
> + };
> +
> + leds {
> + act {
> + gpios = <&gpio 29 GPIO_ACTIVE_HIGH>;
> + };
> +
> + pwr {
> + label = "PWR";
> + gpios = <&expgpio 2 GPIO_ACTIVE_LOW>;
> + };
> + };
> +};
> +
> +&gpio {
> + /*
> + * This is mostly based on the official GPU firmware DT blob.
> + *
> + * Legend:
> + * "NC" = not connected (no rail from the SoC)
> + * "FOO" = GPIO line named "FOO" on the schematic
> + * "FOO_N" = GPIO line named "FOO" on schematic, active low
> + */
> + gpio-line-names = "ID_SDA",
> + "ID_SCL",
> + "SDA1",
> + "SCL1",
> + "GPIO_GCLK",
> + "GPIO5",
> + "GPIO6",
> + "SPI_CE1_N",
> + "SPI_CE0_N",
> + "SPI_MISO",
> + "SPI_MOSI",
> + "SPI_SCLK",
> + "GPIO12",
> + "GPIO13",
> + /* Serial port */
> + "TXD1",
> + "RXD1",
> + "GPIO16",
> + "GPIO17",
> + "GPIO18",
> + "GPIO19",
> + "GPIO20",
> + "GPIO21",
> + "GPIO22",
> + "GPIO23",
> + "GPIO24",
> + "GPIO25",
> + "GPIO26",
> + "GPIO27",
> + "HDMI_HPD_N",
> + "STATUS_LED",
> + /* Used by BT module */
> + "CTS0",
> + "RTS0",
> + "TXD0",
> + "RXD0",
> + /* Used by Wifi */
> + "SD1_CLK",
> + "SD1_CMD",
> + "SD1_DATA0",
> + "SD1_DATA1",
> + "SD1_DATA2",
> + "SD1_DATA3",
> + "PWM0_OUT",
> + "PWM1_OUT",
> + "NC", /* GPIO42 */
> + "WIFI_CLK",
> + "SDA0",
> + "SCL0",
> + "SMPS_SCL",
> + "SMPS_SDA",
> + /* Used by SD Card */
> + "SD_CLK_R",
> + "SD_CMD_R",
> + "SD_DATA0_R",
> + "SD_DATA1_R",
> + "SD_DATA2_R",
> + "SD_DATA3_R";
> +};
> +
> +&firmware {
> + expgpio: gpio {
> + compatible = "raspberrypi,firmware-gpio";
> + gpio-controller;
> + #gpio-cells = <2>;
> + gpio-line-names = "",
> + "BT_WL_ON",
> + "STATUS_LED",
> + "",
> + "",
> + "CAM_GPIO0",
> + "CAM_GPIO1",
> + "";
> + status = "okay";
> + };
> +};
> +
> +&hdmi {
> + hpd-gpios = <&gpio 28 GPIO_ACTIVE_LOW>;
> +};
> +
> +&pwm {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pwm0_gpio40 &pwm1_gpio41>;
> + status = "okay";
> +};
> +
> +/*
> + * SDHCI is used to control the SDIO for wireless
> + *
> + * WL_REG_ON and BT_REG_ON of the CYW43455 Wifi/BT module are driven
> + * by a single GPIO. We can't give GPIO control to one of the drivers,
> + * otherwise the other part would get unexpectedly disturbed.
> + */
> +&sdhci {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&emmc_gpio34>;
> + status = "okay";
> + bus-width = <4>;
> + non-removable;
> +
> + brcmf: wifi@1 {
> + reg = <1>;
> + compatible = "brcm,bcm4329-fmac";
> + };
> +};
> +
> +/* SDHOST is used to drive the SD card */
> +&sdhost {
> + pinctrl-names = "default";
> + pinctrl-0 = <&sdhost_gpio48>;
> + status = "okay";
> + bus-width = <4>;
> +};
> +
> +/* uart0 communicates with the BT module */
> +&uart0 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart0_ctsrts_gpio30 &uart0_gpio32 &gpclk2_gpio43>;
> + status = "okay";
> +
> + bluetooth {
> + compatible = "brcm,bcm43438-bt";
> + max-speed = <2000000>;
> + };
> +};
> +
> +/* uart1 is mapped to the pin header */
> +&uart1 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&uart1_gpio14>;
> + status = "okay";
> +};
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-12 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 23:20 [PATCH V4 0/3] ARM: dts: add Raspberry Pi 3 A+ Stefan Wahren
2018-12-25 23:20 ` [PATCH V4 1/3] dt-bindings: bcm: Add " Stefan Wahren
2018-12-25 23:20 ` [PATCH V4 2/3] ARM: dts: add " Stefan Wahren
2018-12-28 0:51 ` Eric Anholt
2019-01-12 18:11 ` Sergey Suloev [this message]
2019-01-12 19:34 ` Stefan Wahren
2019-01-14 12:16 ` Sergey Suloev
2018-12-25 23:20 ` [PATCH V4 3/3] arm64: dts: broadcom: Add reference to RPi " Stefan Wahren
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=2da60463-f536-84f4-a176-4f8df30f6eaf@orpaltech.com \
--to=ssuloev@orpaltech.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=phil@raspberrypi.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).