Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.duyck@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v1 net-next 1/2] igb: add PHY support for Broadcom 5461S
Date: Thu, 07 May 2015 10:49:07 -0700	[thread overview]
Message-ID: <554BA593.6080703@gmail.com> (raw)
In-Reply-To: <CAPg-hwmB-=fd_OjMbtL_Am5e9znX36KOnMnHNdwTMnCmQBeHPw@mail.gmail.com>

On 05/07/2015 06:41 AM, Andy Gospodarek wrote:
> On Thu, May 7, 2015 at 7:49 AM, Jeff Kirsher
> <jeffrey.t.kirsher@intel.com> wrote:
>> On Fri, 2015-04-17 at 13:23 -0700, Jonathan Toppins wrote:
>>> From: Alan Liebthal <alanl@cumulusnetworks.com>
>>>
>>> The Quanta LY8 Ethernet management port uses a Broadcom 5461S chip for
>>> the PHY layer. This adds support for this PHY to the Intel igb driver.
>>>
>>> Signed-off-by: Alan Liebthal <alanl@cumulusnetworks.com>
>>> Signed-off-by: Jonathan Toppins <jtoppins@cumulusnetworks.com>
>>> ---
>>>   drivers/net/ethernet/intel/igb/e1000_82575.c   |   20 +++++-
>>>   drivers/net/ethernet/intel/igb/e1000_defines.h |    1 +
>>>   drivers/net/ethernet/intel/igb/e1000_hw.h      |    1 +
>>>   drivers/net/ethernet/intel/igb/e1000_phy.c     |   79
>>> ++++++++++++++++++++++++
>>>   drivers/net/ethernet/intel/igb/e1000_phy.h     |    2 +
>>>   5 files changed, 102 insertions(+), 1 deletion(-)
>> After at lot of discussion on these changes, we would like to you to use
>> the PHYLib approach.  I know that means adding PHYLib support to our
>> drivers, which we currently do not have.
> Jeff,
>
> I think we would be willing to take on this task, but I would not like
> that to be a gating factor for upstream acceptance of the
> functionality added with this patch.  I see that Aaron has commented
> that no regressions were found with this patch, but based on current
> status in patchwork, it looks like Dave is waiting for something a bit
> more definitive before accepting it.  Can you ACK it first so we have
> support for this platform upstream and then we can go take a stab at
> phylib support for igb?
>
> Thanks,
>
> -andy

I agree with Jeff.  We already have the code from Tim Harvey which is 
adding PHYlib support for i210/i211, it shouldn't take much to extend 
the same kind of SGMII support for i350/i354.  Then with that you free 
yourself up to add whatever PHY you need in the future without having to 
get buy-off from Intel.  As is this patch set looks fishy to me since 
you are providing the

The fact is the merge window will still be open for a while since we are 
only at RC2.

- Alex

  reply	other threads:[~2015-05-07 17:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 20:23 [Intel-wired-lan] [PATCH v1 net-next 1/2] igb: add PHY support for Broadcom 5461S Jonathan Toppins
2015-04-17 20:24 ` [Intel-wired-lan] [PATCH v1 net-next 2/2] igb: support SIOCSMIIREG Jonathan Toppins
2015-05-05 17:25   ` Brown, Aaron F
2015-05-05 19:31     ` Jonathan Toppins
2015-05-07 17:52   ` Alexander Duyck
2015-05-07 20:46     ` Rustad, Mark D
2015-05-08 16:57       ` Jonathan Toppins
2015-04-27 15:44 ` [Intel-wired-lan] [PATCH v1 net-next 1/2] igb: add PHY support for Broadcom 5461S Jonathan Toppins
2015-05-02  1:45   ` Brown, Aaron F
2015-05-07 11:49 ` Jeff Kirsher
2015-05-07 13:41   ` Andy Gospodarek
2015-05-07 17:49     ` Alexander Duyck [this message]
2015-05-08 16:39     ` Ronciak, John
2015-05-08 17:46       ` Andy Gospodarek
2015-05-08 21:32         ` Alexander Duyck
2015-05-08 21:42           ` Jonathan Toppins
2015-05-08 22:05             ` Alexander Duyck
2015-05-08 22:30               ` Jonathan Toppins
2015-05-08 23:06                 ` Alexander Duyck
2015-05-11 14:46           ` Andy Gospodarek
2015-05-07 16:32   ` Tim Harvey
2015-05-07 16:18 ` Tim Harvey
2015-05-07 16:57   ` Jonathan Toppins
2015-05-07 18:20 ` Alexander Duyck

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=554BA593.6080703@gmail.com \
    --to=alexander.duyck@gmail.com \
    --cc=intel-wired-lan@osuosl.org \
    /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