public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marcin Wojtas" <mw@semihalf.com>
To: Leif Lindholm <leif@nuviainc.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Grzegorz Jaszczyk <jaz@semihalf.com>,
	 Grzegorz Bernacki <gjb@semihalf.com>,
	upstream@semihalf.com,
	 Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	Jon Nettleton <jon@solid-run.com>
Subject: Re: [edk2-platforms PATCH 0/4] ACPI MDIO support for Marvell SoCs
Date: Mon, 12 Jul 2021 12:51:50 +0200	[thread overview]
Message-ID: <CAPv3WKdQJp6_gntpx7k7LWLUX72Co59jdx40y768ZmeHyJwHhA@mail.gmail.com> (raw)
In-Reply-To: <CAPv3WKdV4qbEmjT6Gjc2BKhZhcFM9sTTjNfxPwiCrJJ27KnG+A@mail.gmail.com>

Hi,

wt., 29 cze 2021 o 16:17 Marcin Wojtas <mw@semihalf.com> napisał(a):
>
> Hi Leif,
>
> pon., 14 cze 2021 o 23:55 Leif Lindholm <leif@nuviainc.com> napisał(a):
> >
> > Hi Marcin,
> >
> > On Sun, Jun 13, 2021 at 20:16:27 +0200, Marcin Wojtas wrote:
> > > Hi,
> > >
> > > The MDIO ACPI binding has been established and merged to the
> > > Linux tree,
> >
> > Congratulations! :)
> >
> > Is FreeBSD expected to follow suit?
>
> There's no driver yet, but once it's finally created I will make sure
> it supports ACPI properly.
>
> >
> > > hence it is now possible to update the ACPI
> > > description of the platforms that base on the Marvell SoCs.
> > >
> > > For convenience, the code is exposed in the public github branch:
> > > https://github.com/semihalf-wojtas-marcin/edk2-platforms/commits/acpi-mdio-r20210613
> > > There is also MacchiatoBin firmware binary avaialable for testing:
> > > https://drive.google.com/file/d/1eigP_aeM4wYQpEaLAlQzs3IN_w1-kQr0
> > >
> > > I'm looking forward to the comments or remarks.
> >
> > The patches themselves look straightforward enough.
> > I *would* prefer some tested-by, for these sources rather than the
> > binary, before merging though.
> >
>
> I have some our patches queued, that are blocked by this patchset. In
> case no time is found for external testers - if this may help to get
> it pushed through, please see below logs from the next-20210628 tag
> and unchanged firmware. All network ports of MacchiatoBin and
> CN913x-DB work properly, with full 1G/10G PHY support via X/MDIO
> interfaces:
>
> MacchiatoBin
> # uname -a
> Linux buildroot 5.13.0-rc7-next-20210628 #6 SMP PREEMPT Tue Jun 29
> 09:14:07 CEST 2021 aarch64 GNU/Linux
> # dmesg | grep MRVL0101
> [    1.829659] mv88x3340 MRVL0101:00-mii:00: Firmware version 0.3.3.0
> [    1.839622] mv88x3340 MRVL0101:00-mii:08: Firmware version 0.3.3.0
> [    2.748351] mvpp2 MRVL0110:00 eth1: PHY [MRVL0101:00-mii:00] driver
> [mv88x3340] (irq=POLL)
> [    2.767479] mvpp2 MRVL0110:01 eth2: PHY [MRVL0101:00-mii:08] driver
> [mv88x3340] (irq=POLL)
> # dmesg | grep MRVL0100
> [    2.919424] mvpp2 MRVL0110:01 eth3: PHY [MRVL0100:00-mii:00] driver
> [Marvell 88E1510] (irq=POLL)
> # dmesg | grep mvpp2
> [...]
> [    2.748351] mvpp2 MRVL0110:00 eth1: PHY [MRVL0101:00-mii:00] driver
> [mv88x3340] (irq=POLL)
> [    2.756701] mvpp2 MRVL0110:00 eth1: configuring for phy/10gbase-r link mode
> [    2.767479] mvpp2 MRVL0110:01 eth2: PHY [MRVL0101:00-mii:08] driver
> [mv88x3340] (irq=POLL)
> [    2.775834] mvpp2 MRVL0110:01 eth2: configuring for phy/10gbase-r link mode
> [    2.919424] mvpp2 MRVL0110:01 eth3: PHY [MRVL0100:00-mii:00] driver
> [Marvell 88E1510] (irq=POLL)
> [    2.928285] mvpp2 MRVL0110:01 eth3: configuring for phy/sgmii link mode
> [    2.936351] mvpp2 MRVL0110:01 eth4: configuring for
> inband/2500base-x link mode
> [    5.987259] mvpp2 MRVL0110:01 eth3: Link is Up - 1Gbps/Full - flow
> control off
> #
>
> CN913x-DB
> # uname -a
> Linux buildroot 5.13.0-rc7-next-20210628 #6 SMP PREEMPT Tue Jun 29
> 09:14:07 CEST 2021 aarch64 GNU/Linux
> # dmesg | grep MRVL0100
> [    2.621201] mvpp2 MRVL0110:00 eth2: PHY [MRVL0100:00-mii:00] driver
> [Marvell 88E1510] (irq=POLL)
> [    2.741199] mvpp2 MRVL0110:00 eth3: PHY [MRVL0100:00-mii:01] driver
> [Marvell 88E1510] (irq=POLL)
> # dmesg | grep mvpp2
> [...]
> [    2.544917] mvpp2 MRVL0110:00 eth1: configuring for
> inband/10gbase-r link mode
> [    2.552480] mvpp2 MRVL0110:00 eth1: Link is Up - 10Gbps/Full - flow
> control rx
> [    2.621201] mvpp2 MRVL0110:00 eth2: PHY [MRVL0100:00-mii:00] driver
> [Marvell 88E1510] (irq=POLL)
> [    2.630060] mvpp2 MRVL0110:00 eth2: configuring for phy/rgmii-id link mode
> [    2.741199] mvpp2 MRVL0110:00 eth3: PHY [MRVL0100:00-mii:01] driver
> [Marvell 88E1510] (irq=POLL)
> [    2.750056] mvpp2 MRVL0110:00 eth3: configuring for phy/rgmii-id link mode
> [    2.810169] mvpp2 MRVL0110:01 eth4: configuring for
> inband/10gbase-r link mode
> [    2.817471] mvpp2 MRVL0110:01 eth4: Link is Up - 10Gbps/Full - flow
> control rx
> [    5.693231] mvpp2 MRVL0110:00 eth2: Link is Up - 1Gbps/Full - flow
> control off
> [   10.840942] mvpp2 MRVL0110:00 eth1: Link is Down
> [   10.864124] mvpp2 MRVL0110:01 eth4: Link is Down
> #
>

Both platforms were have been additionally tested by Greg, do you have
any comments/objections to merging this patchset?

Thanks,
Marcin

  reply	other threads:[~2021-07-12 10:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-13 18:16 [edk2-platforms PATCH 0/4] ACPI MDIO support for Marvell SoCs Marcin Wojtas
2021-06-13 18:16 ` [edk2-platforms PATCH 1/4] SolidRun/Armada80x0McBin: Add ACPI MDIO description Marcin Wojtas
2021-07-09  5:51   ` Grzegorz Bernacki
2021-06-13 18:16 ` [edk2-platforms PATCH 2/4] Marvell/Cn913xDb: " Marcin Wojtas
2021-07-09  5:36   ` Grzegorz Bernacki
2021-06-13 18:16 ` [edk2-platforms PATCH 3/4] Marvell/Armada70x0Db: " Marcin Wojtas
2021-06-13 18:16 ` [edk2-platforms PATCH 4/4] Marvell/Armada80x0Db: " Marcin Wojtas
2021-06-14 21:55 ` [edk2-platforms PATCH 0/4] ACPI MDIO support for Marvell SoCs Leif Lindholm
2021-06-15  4:10   ` Jon Nettleton
2021-06-29 14:17   ` Marcin Wojtas
2021-07-12 10:51     ` Marcin Wojtas [this message]
2021-07-12 11:17       ` Jon Nettleton
2021-07-16 17:32         ` Ard Biesheuvel
2021-07-19  7:27           ` Ard Biesheuvel
2021-07-19  9:34             ` Marcin Wojtas

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-list 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=CAPv3WKdQJp6_gntpx7k7LWLUX72Co59jdx40y768ZmeHyJwHhA@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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