From: Florian Fainelli <f.fainelli@gmail.com>
To: Marek Vasut <marex@denx.de>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH V3] net: phy: tja11xx: Add TJA11xx PHY driver
Date: Thu, 3 Jan 2019 18:57:49 -0800 [thread overview]
Message-ID: <f652fee7-80ab-5d85-0e83-a8d82aa67848@gmail.com> (raw)
In-Reply-To: <1731fce4-21c3-aa03-953e-ab4610479431@denx.de>
On 1/3/2019 6:53 PM, Marek Vasut wrote:
> On 1/4/19 3:19 AM, Marek Vasut wrote:
>
> [...]
>
> On a separate note, I was pondering about the master/slave mode of the
> TJA11xx PHY. Right now, the driver only operates in Automatic mode,
> however the PHY can be force-configured as either master or slave.
> Would using .set_tunable with a new tunable type be a good way to expose
> this to userspace ? The ethtool can then configure the PHY mode.
Using an ethtool u8 tunable would be fine, with something like:
0 -> automatic
1 -> force master
2 -> force slave
--
Florian
next prev parent reply other threads:[~2019-01-04 2:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 23:35 [PATCH V3] net: phy: tja11xx: Add TJA11xx PHY driver Marek Vasut
2018-12-22 17:39 ` Heiner Kallweit
2018-12-23 9:16 ` Marek Vasut
2018-12-23 9:41 ` Heiner Kallweit
2018-12-23 9:59 ` Andrew Lunn
2018-12-23 10:21 ` Marek Vasut
2018-12-23 10:35 ` Andrew Lunn
2018-12-23 10:48 ` Marek Vasut
2019-01-03 2:09 ` Marek Vasut
2019-01-03 6:23 ` Heiner Kallweit
2019-01-04 2:19 ` Marek Vasut
2019-01-04 2:53 ` Marek Vasut
2019-01-04 2:57 ` Florian Fainelli [this message]
2019-01-04 5:40 ` Marek Vasut
2018-12-22 20:51 ` Heiner Kallweit
2018-12-23 9:13 ` Marek Vasut
2018-12-23 10:06 ` Andrew Lunn
2018-12-23 10:49 ` Marek Vasut
2018-12-23 10:58 ` Andrew Lunn
2018-12-23 11:00 ` Marek Vasut
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=f652fee7-80ab-5d85-0e83-a8d82aa67848@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=marex@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.