From: Frank Wunderlich <frank-w@public-files.de>
To: Daniel Golle <daniel@makrotopia.org>
Cc: "Frank Wunderlich" <linux@fw-web.de>,
linux-mediatek@lists.infradead.org,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Ryder Lee" <ryder.lee@mediatek.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
"Jianjun Wang" <jianjun.wang@mediatek.com>,
"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
"Vinod Koul" <vkoul@kernel.org>,
linux-usb@vger.kernel.org,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
devicetree@vger.kernel.org
Subject: Aw: Re: [next v7 8/8] arm64: dts: mt7986: add Bananapi R3
Date: Sun, 25 Dec 2022 12:47:02 +0100 [thread overview]
Message-ID: <trinity-b51cbf64-8df3-4a0b-883a-dbb7443eb954-1671968822286@3c-app-gmx-bap38> (raw)
In-Reply-To: <Y6dMWFy7gChG88j0@makrotopia.org>
Hi
> Gesendet: Samstag, 24. Dezember 2022 um 20:00 Uhr
> Von: "Daniel Golle" <daniel@makrotopia.org>
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3-emmc.dtso
> > @@ -0,0 +1,30 @@
> > +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
> > +/*
> > + * Copyright (C) 2021 MediaTek Inc.
> > + * Author: Sam.Shih <sam.shih@mediatek.com>
> > + */
> > +
> > +/dts-v1/;
> > +/plugin/;
> > +
> > +/ {
> > + compatible = "bananapi,bpi-r3", "mediatek,mt7986a";
> > + model = "Bananapi BPI-R3 (emmc)";
>
> Why do you set the model string here?
seems to be a left over from testing where i wanted to see which base-dtb was
loaded without comparing mmc-node settings. Was easier to see with model-string :)
> > +
> > + fragment@0 {
> > + target-path = "/soc/mmc@11230000";
> > + __overlay__ {
> > + bus-width = <8>;
> > + max-frequency = <200000000>;
> > + cap-mmc-highspeed;
> > + mmc-hs200-1_8v;
> > + mmc-hs400-1_8v;
> > + hs400-ds-delay = <0x14014>;
> > + non-removable;
> > + no-sd;
> > + no-sdio;
> > + status = "okay";
> > + };
> > + };
> > +};
> > diff --git a/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts b/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts
> > new file mode 100644
> > index 000000000000..618d3bb2f32f
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/mediatek/mt7986a-bananapi-bpi-r3.dts
> > +&mdio {
> > + switch: switch@31 {
> > + compatible = "mediatek,mt7531";
> > + reg = <31>;
> > + reset-gpios = <&pio 5 GPIO_ACTIVE_HIGH>;
>
> Please add:
>
> interrupt-controller;
> #interrupt-cells = <1>;
> interrupt-parent = <&pio>;
> interrupts = <66 IRQ_TYPE_LEVEL_HIGH>;
>
> to have IRQ driven phy status instead of having to poll the link status
> of the 5x rj-45 ports.
> The value comes from schematics (pin AD24, GPIO66, 7531_INT) and I've
> tested this on my board.
ok, if you have it tested i add these properties in next version (and test it too).
I wait for tphy-binding to be applied to next (pcie and xhci already in torvalds/master).
> > + };
> > +};
> > +
> > +&spi0 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&spi_flash_pins>;
> > + cs-gpios = <0>, <0>;
>
> I don't think those bogus cs-gpios here and for spi1 below are needed.
can drop them in next version
> > + status = "okay";
> > +};
> > +
> > +&spi1 {
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&spic_pins>;
> > + cs-gpios = <0>, <0>;
> > + status = "okay";
> > +};
> > +
regards Frank
next prev parent reply other threads:[~2022-12-25 11:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 11:41 [next v7 0/8] Add BananaPi R3 Frank Wunderlich
2022-11-27 11:41 ` [next v7 1/8] dt-bindings: phy: mediatek,tphy: add support for mt7986 Frank Wunderlich
2022-11-27 11:41 ` [next v7 2/8] dt-bindings: usb: mtk-xhci: " Frank Wunderlich
2022-11-27 11:41 ` [next v7 3/8] dt-bindings: PCI: mediatek-gen3: add SoC based clock config Frank Wunderlich
2022-11-27 11:41 ` [next v7 4/8] dt-bindings: PCI: mediatek-gen3: add support for mt7986 Frank Wunderlich
2022-11-27 11:41 ` [next v7 5/8] arm64: dts: mt7986: add usb related device nodes Frank Wunderlich
2022-11-27 11:41 ` [next v7 6/8] arm64: dts: mt7986: add mmc " Frank Wunderlich
2022-11-27 11:41 ` [next v7 7/8] arm64: dts: mt7986: add pcie " Frank Wunderlich
2022-11-27 11:41 ` [next v7 8/8] arm64: dts: mt7986: add Bananapi R3 Frank Wunderlich
2022-12-24 19:00 ` Daniel Golle
2022-12-25 11:47 ` Frank Wunderlich [this message]
2022-12-27 9:43 ` Aw: " Frank Wunderlich
2022-12-27 10:29 ` Frank Wunderlich
2022-12-06 11:32 ` [next v7 0/8] Add BananaPi R3 Lorenzo Pieralisi
2022-12-06 15:42 ` (subset) " Lorenzo Pieralisi
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=trinity-b51cbf64-8df3-4a0b-883a-dbb7443eb954-1671968822286@3c-app-gmx-bap38 \
--to=frank-w@public-files.de \
--cc=bhelgaas@google.com \
--cc=chunfeng.yun@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jianjun.wang@mediatek.com \
--cc=kishon@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@fw-web.de \
--cc=lpieralisi@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).