public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: u-boot@lists.denx.de
Cc: alvaro.karsz@solid-run.com, Nate Drude <nate.d@variscite.com>
Subject: Re: [PATCH 0/5] mx6cuboxi: add eth support for SoMs revision 1.9+
Date: Thu, 19 May 2022 11:59:06 +0300	[thread overview]
Message-ID: <1e1fe138-fb2d-dda1-7220-96e032dc3bf2@solid-run.com> (raw)
In-Reply-To: <20220501124131.30614-1-josua@solid-run.com>

Greetings everybody,

The changes to the adin phy device-tree bindings and driver have been 
applied to netdev/net-next:
https://patchwork.kernel.org/project/netdevbpf/cover/20220517085143.3749-1-josua@solid-run.com/

As there have been no further comments, I will send v2 soon including 
some changes the Linux maintainers asked for - and drop the first patch 
now that Nate Drude has submitted a fix:
phy: adin: fix broken support for adi,phy-mode-override

sincerely
Josua Mayer

Am 01.05.22 um 15:41 schrieb Josua Mayer:
> As of Revision 1.9 the SolidRun i.MX6 SoMs ship with a new PHY - an
> ADIN1300 at address 1. This patchset carries many small parts to
> facilitate proper operation of the ethernet port in U-Boot as well as
> Linux:
> 
> 1. Fix a compile error in the recently phy driver
> 2. Add support for configuring the clock output pins to the phy driver
> 3. update device-tree with support for the neew phy
> 4. support runtime patching of device-tree for Linux:
>     enables only the phy node detected during boot, to avoid
>     warning messages during boot.
> 5. finally enable the phy driver in the cuboxi defconfig
> 
> Josua Mayer (5):
>    phy: adin: remove broken support for adi,phy-mode-override
>    phy: adin: add support for clock output
>    ARM: dts: imx6qdl-sr-som: add support for alternate phy addresses
>    mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS
>    mx6cuboxi: enable driver for adin1300 phy
> 
>   arch/arm/dts/imx6qdl-sr-som.dtsi     | 17 +++++-
>   board/solidrun/mx6cuboxi/mx6cuboxi.c | 78 +++++++++++++++++++++++++++
>   configs/mx6cuboxi_defconfig          |  2 +
>   drivers/net/phy/adin.c               | 80 ++++++++++++++++------------
>   4 files changed, 141 insertions(+), 36 deletions(-)
> 

      parent reply	other threads:[~2022-05-19  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 12:41 [PATCH 0/5] mx6cuboxi: add eth support for SoMs revision 1.9+ Josua Mayer
2022-05-01 12:41 ` [PATCH 1/5] phy: adin: remove broken support for adi, phy-mode-override Josua Mayer
2022-05-02 13:25   ` [PATCH 1/5] phy: adin: remove broken support for adi,phy-mode-override Nate Drude
2022-05-04  8:51     ` Josua Mayer
2022-05-04 12:46       ` Nate Drude
2022-05-05 15:30         ` Josua Mayer
2022-05-08  9:34           ` Josua Mayer
2022-05-01 12:41 ` [PATCH 2/5] phy: adin: add support for clock output Josua Mayer
2022-05-01 12:41 ` [PATCH 3/5] ARM: dts: imx6qdl-sr-som: add support for alternate phy addresses Josua Mayer
2022-05-01 12:41 ` [PATCH 4/5] mx6cuboxi: fixup dtb ethernet phy nodes before booting an OS Josua Mayer
2022-05-01 12:41 ` [PATCH 5/5] mx6cuboxi: enable driver for adin1300 phy Josua Mayer
2022-05-19  8:59 ` Josua Mayer [this message]

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=1e1fe138-fb2d-dda1-7220-96e032dc3bf2@solid-run.com \
    --to=josua@solid-run.com \
    --cc=alvaro.karsz@solid-run.com \
    --cc=nate.d@variscite.com \
    --cc=u-boot@lists.denx.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