public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Guenter Roeck <linux@roeck-us•net>
To: Alexander Duyck <alexander.h.duyck@intel•com>
Cc: netdev@vger•kernel.org, f.fainelli@gmail•com,
	kernel@wantstofly•org, davem@davemloft•net
Subject: Re: [2/2] dsa: Replace mii_bus with a generic host device
Date: Mon, 13 Oct 2014 10:51:43 -0700	[thread overview]
Message-ID: <20141013175143.GA30743@roeck-us.net> (raw)
In-Reply-To: <20140915170024.1261.97226.stgit@ahduyck-bv4.jf.intel.com>

On Mon, Sep 15, 2014 at 01:00:27PM -0400, Alexander Duyck wrote:
> This change makes it so that instead of passing and storing a mii_bus we
> instead pass and store a host_dev.  From there we can test to determine the
> exact type of device, and can verify it is the correct device for our switch.
> 
> So for example it would be possible to pass a device pointer from a pci_dev
> and instead of checking for a PHY ID we could check for a vendor and/or device
> ID.
> 

Hi Alexander,

We are thinking about porting a PCIe based switch to use the DSA infrastructure,
so this patch is coming quite handy.

Have you been working on a port or a PCIe based chip to DSA yourself, by any
chance ? If yes, could you possibly share the current state ?
That might save us some time.

Thanks,
Guenter

next prev parent reply	other threads:[~2014-10-13 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:59 [PATCH 0/2] DSA Cleanups Alexander Duyck
2014-09-15 17:00 ` [PATCH 1/2] dsa: Split ops up, and avoid assigning tag_protocol and receive separately Alexander Duyck
2014-09-15 17:00 ` [PATCH 2/2] dsa: Replace mii_bus with a generic host device Alexander Duyck
2014-09-15 21:48   ` Florian Fainelli
2014-10-13 17:51   ` Guenter Roeck [this message]
2014-09-15 21:24 ` [PATCH 0/2] DSA Cleanups David Miller

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=20141013175143.GA30743@roeck-us.net \
    --to=linux@roeck-us$(echo .)net \
    --cc=alexander.h.duyck@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=kernel@wantstofly$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox