public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tobias Waldekranz" <tobias@waldekranz.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] net: phy: marvell smi2usb mdio controller
Date: Fri, 20 Mar 2020 15:44:34 +0100	[thread overview]
Message-ID: <C1FQR2V46F7K.1KBCJSQ8V4V2B@wkz-x280> (raw)
In-Reply-To: <20200319230002.GO27807@lunn.ch>

Hi Andrew,

> > How about just mdio-mvusb?
>
> 
> Yes, i like that.

ACK.

> > On the 88E6390X-DB, I know that there is a chip by the USB port that
> > is probably either an MCU or a small FPGA. I can have a closer look at
> > it when I'm at the office tomorrow if you'd like. I also remember
> > seeing some docs from Marvell which seemed to indicate that they have
> > a standalone product providing only the USB-to-MDIO functionality.
>
> 
> I would be interested in knowing more.

It seems like they are using the Cypress FX2 controller
(CY7C68013). I've used it before on USB device projects. If I remember
correctly it has an 8052 core, a USB2 controller and some low-speed
I/O blocks. Couldn't locate the slide deck about a standalone device
unfortunately.

> I would fixup the naming and repost. You can put whatever comments you
> want under the --- marker. So say this driver should be merged via
> netdev, but you would appreciate reviews of the USB parts from USB
> maintainers. linux-usb@vger.kernel.org would be the correct list to
> add.

Great. Just to make sure I've understood: I'll send v3 with _both_
netdev and linux-usb in "To:"?

Thanks,
wkz

  reply	other threads:[~2020-03-20 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 13:59 [PATCH v2 1/2] dt-bindings: net: add marvell smi2usb bindings Tobias Waldekranz
2020-03-19 13:59 ` [PATCH v2 2/2] net: phy: marvell smi2usb mdio controller Tobias Waldekranz
2020-03-19 15:49   ` Andrew Lunn
2020-03-19 22:35     ` Tobias Waldekranz
2020-03-19 23:00       ` Andrew Lunn
2020-03-20 14:44         ` Tobias Waldekranz [this message]
2020-03-21  0:29           ` Andrew Lunn

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=C1FQR2V46F7K.1KBCJSQ8V4V2B@wkz-x280 \
    --to=tobias@waldekranz.com \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.kernel.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