From: Robert Nelson <robertcnelson@gmail.com>
To: Paul Barker <paul.barker@sancloud.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"Marc Murphy" <marc.murphy@sancloud.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>
Subject: Re: [PATCH 3/4] ARM: dts: am335x-sancloud-bbe-lite: New devicetree
Date: Fri, 18 Jun 2021 11:02:12 -0500 [thread overview]
Message-ID: <CAOCHtYjEn+F+_chyMQ0cppA0y=ZeHrme3c66A2Z5U6pJf9a8_w@mail.gmail.com> (raw)
In-Reply-To: <20210617093330.9179-4-paul.barker@sancloud.com>
Hi Paul,
On Thu, Jun 17, 2021 at 4:35 AM Paul Barker <paul.barker@sancloud.com> wrote:
>
> This adds support for the Sancloud BBE Lite which shares a common
> hardware base with the non-Lite version of the BBE.
>
> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
> ---
> arch/arm/boot/dts/Makefile | 1 +
> .../arm/boot/dts/am335x-sancloud-bbe-lite.dts | 51 +++++++++++++++++++
> 2 files changed, 52 insertions(+)
> create mode 100644 arch/arm/boot/dts/am335x-sancloud-bbe-lite.dts
>
> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
> index f8f09c5066e7..8629c941f573 100644
> --- a/arch/arm/boot/dts/Makefile
> +++ b/arch/arm/boot/dts/Makefile
> @@ -834,6 +834,7 @@ dtb-$(CONFIG_SOC_AM33XX) += \
> am335x-pocketbeagle.dtb \
> am335x-regor-rdk.dtb \
> am335x-sancloud-bbe.dtb \
> + am335x-sancloud-bbe-lite.dtb \
> am335x-shc.dtb \
> am335x-sbc-t335.dtb \
> am335x-sl50.dtb \
> diff --git a/arch/arm/boot/dts/am335x-sancloud-bbe-lite.dts b/arch/arm/boot/dts/am335x-sancloud-bbe-lite.dts
> new file mode 100644
> index 000000000000..9c311bd106f6
> --- /dev/null
> +++ b/arch/arm/boot/dts/am335x-sancloud-bbe-lite.dts
> @@ -0,0 +1,51 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> +/*
> + * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
> + * Copyright (C) 2021 SanCloud Ltd
> + */
> +/dts-v1/;
> +
> +#include "am33xx.dtsi"
> +#include "am335x-bone-common.dtsi"
> +#include "am335x-boneblack-common.dtsi"
> +#include "am335x-sancloud-bbe-common.dtsi"
> +
> +/ {
> + model = "SanCloud BeagleBone Enhanced Lite";
> + compatible = "sancloud,am335x-boneenhanced",
> + "ti,am335x-bone-black",
> + "ti,am335x-bone",
> + "ti,am33xx";
> +};
> +
> +&am33xx_pinmux {
> + bb_spi0_pins: pinmux_bb_spi0_pins {
> + pinctrl-single,pins = <
> + AM33XX_PADCONF(AM335X_PIN_SPI0_SCLK, PIN_INPUT, MUX_MODE0)
> + AM33XX_PADCONF(AM335X_PIN_SPI0_D0, PIN_INPUT, MUX_MODE0)
> + AM33XX_PADCONF(AM335X_PIN_SPI0_D1, PIN_INPUT, MUX_MODE0)
> + AM33XX_PADCONF(AM335X_PIN_SPI0_CS0, PIN_INPUT, MUX_MODE0)
> + >;
> + };
> +};
> +
> +&spi0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&bb_spi0_pins>;
> +
> + channel@0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + compatible = "micron,spi-authenta";
> + symlink = "spi/0.0";
Sorry, this "symlink" is an undocumented "feature" of the
BeagleBoard.org tree.. We use it to help "identity" spi/usart/i2c
nodes names when they dynamically change node numbers based on kernel
versions or even 'drivers'....
https://github.com/beagleboard/customizations/blob/master/etc/udev/rules.d/10-of-symlink.rules
For 'mainline' we need to remove it..
Regards,
--
Robert Nelson
https://rcn-ee.com/
next prev parent reply other threads:[~2021-06-18 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:33 [PATCH 0/4] Add support for the SanCloud BBE Lite Paul Barker
2021-06-17 9:33 ` [PATCH 1/4] ARM: dts: am335x-boneblack: Extract HDMI config Paul Barker
2021-06-17 9:33 ` [PATCH 2/4] ARM: dts: am335x-sancloud-bbe: Extract common code Paul Barker
2021-06-17 9:33 ` [PATCH 3/4] ARM: dts: am335x-sancloud-bbe-lite: New devicetree Paul Barker
2021-06-18 16:02 ` Robert Nelson [this message]
2021-06-29 13:10 ` Paul Barker
2021-07-20 8:41 ` Paul Barker
2021-06-17 9:33 ` [PATCH 4/4] MAINTAINERS: Adopt SanCloud dts files as supported Paul Barker
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='CAOCHtYjEn+F+_chyMQ0cppA0y=ZeHrme3c66A2Z5U6pJf9a8_w@mail.gmail.com' \
--to=robertcnelson@gmail.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.murphy@sancloud.com \
--cc=olof@lixom.net \
--cc=paul.barker@sancloud.com \
--cc=tony@atomide.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 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.