public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Soeren Moch <smoch@web.de>
Cc: Fabio Estevam <festevam@gmail.com>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] ARM: dts: imx6q-tbs2910: Add an mdio node
Date: Mon, 13 Jul 2020 09:18:10 +0800	[thread overview]
Message-ID: <20200713011810.GQ21277@dragon> (raw)
In-Reply-To: <1500b023-57dd-8031-863d-328fa9dcb214@web.de>

On Thu, Jun 25, 2020 at 06:29:25PM +0200, Soeren Moch wrote:
> Hi Fabio,
> 
> On 25.06.20 13:18, Fabio Estevam wrote:
> > imx6q-tbs2910 has an Atheros AR8035 Ethernet PHY at address 4.
> >
> > The AR8035 provides a 125MHz clock to the ENET_REF_CLK i.MX6 pin.
> >
> > Improve the Ethernet representation by adding an mdio node with such
> > information.
> >
> > This fixes an Ethernet regression in U-Boot as U-Boot AR803X driver now
> > expects the 'qca,clk-out-frequency' property to be passed via
> > device tree.
> >
> > Signed-off-by: Fabio Estevam <festevam@gmail.com>
> Due to my experience Shawn likes the properties sorted alphabetically,
> with some exceptions.

Oh, it would be good to have properties sorted somehow, but I'm not
enforcing that.  What I like to sort alphabetically is those labeling
nodes.

Shawn

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-07-13  1:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 11:18 [PATCH v2 1/2] ARM: dts: imx6q-tbs2910: Pass phy-reset-duration Fabio Estevam
2020-06-25 11:18 ` [PATCH v2 2/2] ARM: dts: imx6q-tbs2910: Add an mdio node Fabio Estevam
2020-06-25 16:29   ` Soeren Moch
2020-07-13  1:18     ` Shawn Guo [this message]
2020-06-25 16:29 ` [PATCH v2 1/2] ARM: dts: imx6q-tbs2910: Pass phy-reset-duration Soeren Moch
2020-07-13  1:19   ` Shawn Guo
2020-07-13 13:10     ` Fabio Estevam

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=20200713011810.GQ21277@dragon \
    --to=shawnguo@kernel.org \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=smoch@web.de \
    /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