From: Yegor Yefremov <yegorslists@googlemail.com>
To: David Miller <davem@davemloft.net>
Cc: Stefan Roese <sr@denx.de>, netdev <netdev@vger.kernel.org>,
"r.meier" <r.meier@siemens.com>,
"lukas.stockmann" <lukas.stockmann@siemens.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH] net: phy: Add support for SMSC/Microchip LAN9303 3-port switch
Date: Wed, 12 Mar 2014 09:43:03 +0100 [thread overview]
Message-ID: <CAGm1_kvTRkCq93BaPgN-MY5Oji3e4is7eq-BtOLv-LJGDCDqPQ@mail.gmail.com> (raw)
In-Reply-To: <20140311.163924.934541574802061078.davem@davemloft.net>
On Tue, Mar 11, 2014 at 9:39 PM, David Miller <davem@davemloft.net> wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> Date: Tue, 11 Mar 2014 21:11:16 +0100
>
>> On Fri, Feb 28, 2014 at 7:00 PM, David Miller <davem@davemloft.net> wrote:
>>> From: Stefan Roese <sr@denx.de>
>>> Date: Fri, 28 Feb 2014 10:32:20 +0100
>>>
>>>> On 27.02.2014 23:02, David Miller wrote:
>>>>> From: Stefan Roese <sr@denx.de>
>>>>> Date: Thu, 27 Feb 2014 10:07:52 +0100
>>>>>
>>>>> Better is to come up with a real, types, interface for programming
>>>>> such devices and providing an implementation of that.
>>>>
>>>> Right. Such a thing would be better. But as Florian already pointed
>>>> out, nothing like this is available in kernel.org right now. Thats the
>>>> reason why I chose to implement this "simple" driver, btw as done in
>>>> drivers/net/phy/spi_ks8995.c.
>>>
>>> When a suitable user facing interface is lacking, you create one
>>> and submit it for review here. You don't just submit adhoc driver
>>> local stuff.
>>
>> David, what about enabling ethtool to read/write from/to the PHY
>> registers (via passing PHY ID and register number)? I'm trying to get
>> ICplus IP175D running and it has lots of registers, that I would like
>> to look at dynamically.
>
> For debugging, register dumps are already supported by ethtool.
Do you mean 'ethtool -e' option? AFAIK it dumps Ethernet controller
regs, if it implements ethtool_ops.get_regs(). What I need are PHY
registers, that I can get via MII interface. ethtool should provide
access to PHY registers like mdiobus_read() and mdiobus_write()
routines. Another option were to add get_regs() to 'struct
phy_driver', but in this case one won't be able to write to the
registers.
Yegor
next prev parent reply other threads:[~2014-03-12 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 9:07 [PATCH] net: phy: Add support for SMSC/Microchip LAN9303 3-port switch Stefan Roese
2014-02-27 22:02 ` David Miller
2014-02-27 22:21 ` Florian Fainelli
2014-03-11 15:49 ` Yegor Yefremov
2014-02-28 9:32 ` Stefan Roese
2014-02-28 18:00 ` David Miller
2014-03-11 20:11 ` Yegor Yefremov
2014-03-11 20:14 ` Florian Fainelli
2014-03-12 8:47 ` Yegor Yefremov
2014-03-12 8:55 ` Meier, Roger
2014-03-11 20:39 ` David Miller
2014-03-12 8:43 ` Yegor Yefremov [this message]
2014-03-12 20:21 ` Ben Hutchings
2014-03-13 22:42 ` Yegor Yefremov
2014-03-14 14:29 ` Ben Hutchings
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=CAGm1_kvTRkCq93BaPgN-MY5Oji3e4is7eq-BtOLv-LJGDCDqPQ@mail.gmail.com \
--to=yegorslists@googlemail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=lukas.stockmann@siemens.com \
--cc=netdev@vger.kernel.org \
--cc=r.meier@siemens.com \
--cc=sr@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).