From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
"Ooi, Tzy Way" <tzy.way.ooi@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Loh, Tien Hock" <tien.hock.loh@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [PATCH v4 edk2-platforms 1/1] Silicon/DesignWare/Driver: DwEmacSnpDxe: Add DesignWare EMAC driver
Date: Wed, 26 Jun 2019 12:00:37 +0200 [thread overview]
Message-ID: <CAKv+Gu_+U2iqCV2g6Jpv8nZJjvkhsSuCLeW25Ewmdj+aSL03kA@mail.gmail.com> (raw)
In-Reply-To: <5F1105621EDF844291AF8B109E27C06D34D21B38@PGSMSX109.gar.corp.intel.com>
On Wed, 26 Jun 2019 at 11:35, Ooi, Tzy Way <tzy.way.ooi@intel.com> wrote:
>
> Hi Bieshuevel,
>
> You mentioned that "Are these discrete components? If so, I wonder we should use some kind of abstraction for the PHY operation". In our system, the MAC is only connected to this PHY, hence wonder if is it ok to still maintain as it is for now?
>
I think that is ok for now, since it is what all ethernet drivers do.
> Also, may I know if you could explain more on what is abstraction for the PHY?
>
MAC <-> PHY communication uses a standardized programming interface
over a standardized bus, so there is bound to be an opportunity for
sharing more code between drivers than we do today.
prev parent reply other threads:[~2019-06-26 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 9:52 [PATCH v4 edk2-platforms 1/1] Silicon/DesignWare/Driver: DwEmacSnpDxe: Add DesignWare EMAC driver tzy.way.ooi
2019-05-22 2:37 ` tzy.way.ooi
2019-05-22 7:21 ` [edk2-devel] " Ard Biesheuvel
2019-05-31 9:14 ` Ooi, Tzy Way
2019-05-31 9:19 ` Ard Biesheuvel
2019-06-19 10:09 ` Ooi, Tzy Way
2019-06-19 10:12 ` Ard Biesheuvel
2019-06-26 9:35 ` Ooi, Tzy Way
2019-06-26 10:00 ` Ard Biesheuvel [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-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=CAKv+Gu_+U2iqCV2g6Jpv8nZJjvkhsSuCLeW25Ewmdj+aSL03kA@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