LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au> To: Tao Ren <rentao.bupt@gmail.com> Cc: Rob Herring <robh+dt@kernel.org>, Andrew Jeffery <andrew@aj.id.au>, devicetree <devicetree@vger.kernel.org>, Linux ARM <linux-arm-kernel@lists.infradead.org>, linux-aspeed <linux-aspeed@lists.ozlabs.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, OpenBMC Maillist <openbmc@lists.ozlabs.org>, Tao Ren <taoren@fb.com> Subject: Re: [PATCH 6/6] ARM: dts: aspeed: Add Facebook Fuji (AST2600) BMC Date: Thu, 5 Aug 2021 00:28:02 +0000 [thread overview] Message-ID: <CACPK8XemZkV7nK_b4883DN+dJKhL=tXfqK6=DpHQe=fZRu_ETQ@mail.gmail.com> (raw) In-Reply-To: <20210728233755.17963-7-rentao.bupt@gmail.com> On Wed, 28 Jul 2021 at 23:38, <rentao.bupt@gmail.com> wrote: > > From: Tao Ren <rentao.bupt@gmail.com> > > Add initial version of device tree for Facebook Fuji (AST2600) BMC. I like to read what kind of platform the BMC is going into if you can add that detail, but it's not essential. > +&spi1 { > + status = "okay"; > + > + /* > + * Customize spi1 flash memory size to 32MB (maximum flash size on > + * the bus) to save vmalloc space. > + */ > + reg = < 0x1e630000 0xc4 > + 0x30000000 0x2000000 >; Which driver supports this? It would be great to see Facebook work to get the SPI NOR driver for the ast2600 merged to mainline. I doubt the IBM team will get to this, as we are using eMMC instead. > + > + flash@0 { > + status = "okay"; > + m25p,fast-read; > + label = "spi1.0"; > + spi-max-frequency = <5000000>; > + > + partitions { > + compatible = "fixed-partitions"; > + #address-cells = <1>; > + #size-cells = <1>; > + > + flash1@0 { > + reg = <0x0 0x2000000>; > + label = "system-flash"; > + }; > + }; > + }; > +}; > +&ehci1 { > + status = "okay"; > +}; Have you verified that USB works with mainline? I've had reports of it working on 5.8 but it seems to have regressed as of v5.10. > +&mdio1 { > + status = "okay"; > + > + ethphy3: ethernet-phy@13 { > + compatible = "ethernet-phy-ieee802.3-c22"; > + reg = <0x0d>; > + }; > +}; > + > +&mac3 { > + phy-handle = <ðphy3>; status = okay? You should specify the pinmux too I think, even if the default happens to work, so that other devices cannot claim the pins. Cheers, Joel
next prev parent reply other threads:[~2021-08-05 0:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-28 23:37 [PATCH 0/6] ARM: dts: Add Facebook AST2600 BMCs rentao.bupt 2021-07-28 23:37 ` [PATCH 1/6] ARM: dts: Add Facebook BMC 128MB flash layout rentao.bupt 2021-07-28 23:37 ` [PATCH 2/6] ARM: dts: aspeed: wedge400: Use common " rentao.bupt 2021-07-28 23:37 ` [PATCH 3/6] ARM: dts: aspeed: Common dtsi for Facebook AST2600 Network BMCs rentao.bupt 2021-07-28 23:37 ` [PATCH 4/6] ARM: dts: aspeed: Add Facebook Cloudripper (AST2600) BMC rentao.bupt 2021-07-28 23:37 ` [PATCH 5/6] ARM: dts: aspeed: Add Facebook Elbert " rentao.bupt 2021-07-28 23:37 ` [PATCH 6/6] ARM: dts: aspeed: Add Facebook Fuji " rentao.bupt 2021-08-05 0:28 ` Joel Stanley [this message] 2021-08-05 1:19 ` Tao Ren 2021-08-05 1:37 ` Joel Stanley 2021-08-05 2:09 ` Tao Ren 2021-08-05 2:17 ` Joel Stanley
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='CACPK8XemZkV7nK_b4883DN+dJKhL=tXfqK6=DpHQe=fZRu_ETQ@mail.gmail.com' \ --to=joel@jms.id.au \ --cc=andrew@aj.id.au \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-aspeed@lists.ozlabs.org \ --cc=linux-kernel@vger.kernel.org \ --cc=openbmc@lists.ozlabs.org \ --cc=rentao.bupt@gmail.com \ --cc=robh+dt@kernel.org \ --cc=taoren@fb.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: linkBe 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).