From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] ARM64: dts: meson-gxm: Add Vega S96 board
Date: Wed, 20 Sep 2017 10:36:26 +0200 [thread overview]
Message-ID: <5e034ee7-278a-5b89-8ebc-ca24a00ae095@baylibre.com> (raw)
In-Reply-To: <CAFBinCCVKFbU-kk9EFzbTbfKCGbOpmm+46spsVry=0E_JCTJgQ@mail.gmail.com>
On 09/19/2017 07:51 PM, Martin Blumenstingl wrote:
> Hi Neil,
>
> On Tue, Sep 19, 2017 at 2:05 PM, Neil Armstrong <narmstrong@baylibre.com> wrote:
>> The Tronsmart Vega S96 is a TV box derived from Amlogic q200 reference design.
>>
>> Cc: support at tronsmart.com
>> Signed-off-by: Oleg <balbes-150@yandex.ru>
>> Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
>> ---
>> arch/arm64/boot/dts/amlogic/Makefile | 1 +
>> arch/arm64/boot/dts/amlogic/meson-gxm-vega-s96.dts | 39 ++++++++++++++++++++++
>> 2 files changed, 40 insertions(+)
>> create mode 100644 arch/arm64/boot/dts/amlogic/meson-gxm-vega-s96.dts
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/Makefile b/arch/arm64/boot/dts/amlogic/Makefile
>> index 7a9f48c..a6c4a06 100644
>> --- a/arch/arm64/boot/dts/amlogic/Makefile
>> +++ b/arch/arm64/boot/dts/amlogic/Makefile
>> @@ -19,6 +19,7 @@ dtb-$(CONFIG_ARCH_MESON) += meson-gxm-nexbox-a1.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-q200.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-q201.dtb
>> dtb-$(CONFIG_ARCH_MESON) += meson-gxm-rbox-pro.dtb
>> +dtb-$(CONFIG_ARCH_MESON) += meson-gxm-vega-s96.dtb
>>
>> always := $(dtb-y)
>> subdir-y := $(dts-dirs)
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxm-vega-s96.dts b/arch/arm64/boot/dts/amlogic/meson-gxm-vega-s96.dts
>> new file mode 100644
>> index 0000000..ba74240
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/amlogic/meson-gxm-vega-s96.dts
>> @@ -0,0 +1,39 @@
>> +/*
>> + * Copyright (c) 2017 BayLibre, SAS.
>> + * Author: Neil Armstrong <narmstrong@baylibre.com>
>> + * Copyright (c) 2017 Oleg <balbes-150@yandex.ru>
>> + *
>> + * SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>> + */
>> +
>> +/dts-v1/;
>> +
>> +#include "meson-gxm.dtsi"
>> +#include "meson-gx-p23x-q20x.dtsi"
>> +
>> +/ {
>> + compatible = "tronsmart,vega-s96", "amlogic,s912", "amlogic,meson-gxm";
>> + model = "Tronsmart Vega S96";
>> +
>> +};
>> +
>> +ðmac {
>> + pinctrl-0 = <ð_pins>;
>> + pinctrl-names = "default";
>> +
>> + /* Select external PHY by default */
>> + phy-handle = <&external_phy>;
>> +
>> + amlogic,tx-delay-ns = <2>;
>> +
>> + /* External PHY is in RGMII */
>> + phy-mode = "rgmii";
>> +};
>> +
>> +&external_mdio {
>> + external_phy: ethernet-phy at 0 {
>> + compatible = "ethernet-phy-id001c.c916", "ethernet-phy-ieee802.3-c22";
> some time ago I thought it was smart to add a compatible string with the PHY ID.
> this was until I figured out that it should only be done if the PHY
> reports an invalid ID: [0]
> that's why most .dts files that I've touched skip the "compatible"
> property and use a comment like "/* Realtek RTL8211F (0x001cc916) */"
> instead
Done, thanks !
Neil
>
>> + reg = <0>;
>> + max-speed = <1000>;
>> + };
>> +};
>> --
>> 1.9.1
>>
>>
>> _______________________________________________
>> linux-amlogic mailing list
>> linux-amlogic at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-amlogic
>
>
> Regards,
> Martin
>
>
> [0] https://github.com/torvalds/linux/commit/7630ea4bda18df2ee1c64dfdca1724a9cc32f920
>
next prev parent reply other threads:[~2017-09-20 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:05 [PATCH 0/2] ARM64: Add Vega S96 board support Neil Armstrong
2017-09-19 12:05 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add Vega S96 board Neil Armstrong
2017-09-19 15:01 ` Jerome Brunet
2017-09-19 18:12 ` Oleg
2017-09-20 8:28 ` Neil Armstrong
2017-09-20 10:47 ` Oleg
2017-09-27 12:30 ` Oleg
2017-09-19 17:51 ` Martin Blumenstingl
2017-09-20 8:36 ` Neil Armstrong [this message]
2017-09-19 12:05 ` [PATCH 2/2] dt-bindings: arm: amlogic: Add Tronsmart Vega S96 binding Neil Armstrong
2017-09-21 23:41 ` Rob Herring
2017-09-19 15:03 ` [PATCH 0/2] ARM64: Add Vega S96 board support Jerome Brunet
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=5e034ee7-278a-5b89-8ebc-ca24a00ae095@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®