From: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<Allan.Nielsen@microsemi.com>, <andrew@lunn.ch>
Subject: Re: [PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi
Date: Tue, 7 Feb 2017 19:09:10 +0530 [thread overview]
Message-ID: <20170207133908.GA29408@microsemi.com> (raw)
In-Reply-To: <6e89a748-f3ca-022f-032f-7fc45c68482d@gmail.com>
Hi Florian,
Thank you for review comments.
On Wed, Feb 01, 2017 at 10:04:08AM -0800, Florian Fainelli wrote:
> EXTERNAL EMAIL
>
>
> On 02/01/2017 04:53 AM, Raju Lakkaraju wrote:
> > From: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
> >
> > LED Mode:
> > Microsemi PHY support 2 LEDs (LED[0] and LED[1]) to display different
> > status information that can be selected by setting LED mode.
>
> Why is this LED selection done through Device Tree/initial configuration
> instead of coming up with a proper LED device registered by the PHY
> which allows you to select exactly how you want the modes to wind-up
> looking like?
>
I wrote the LED driver similar to "Micrel". Added only LED mode.
> NB: you don't need a cover letter for single patches.
>
Accepted. I will do.
> >
> > LED Mode parameter (vsc8531, led-0-mode) and (vsc8531, led-1-mode) get from
> > Device Tree.
> >
> > Tested on Beaglebone Black with VSC 8531 PHY.
> >
> > Change set:
> > v0:
> > - Initial version of LED driver for Microsemi PHYs.
> > v1:
> > - Update all review comments given by Andrew.
> > - Add new header file "mscc-phy-vsc8531.h" to define DT macros.
> > - Add error/range check for DT LED mode input
> > v2:
> > - Fixed x86_64 build error.
> >
> > Signed-off-by: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
> >
> >
> > Raju Lakkaraju (1):
> > net: phy: Add LED mode driver for Microsemi PHYs.
> >
> > .../devicetree/bindings/net/mscc-phy-vsc8531.txt | 10 +++
> > drivers/net/phy/mscc.c | 85 +++++++++++++++++++++-
> > include/dt-bindings/net/mscc-phy-vsc8531.h | 29 ++++++++
> > 3 files changed, 123 insertions(+), 1 deletion(-)
> > create mode 100644 include/dt-bindings/net/mscc-phy-vsc8531.h
> >
>
>
> --
> Florian
---
Thanks,
Raju.
prev parent reply other threads:[~2017-02-07 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 12:53 [PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi Raju Lakkaraju
2017-02-01 12:53 ` [PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi PHYs Raju Lakkaraju
2017-02-01 13:55 ` Andrew Lunn
[not found] ` <20170201135555.GE4967-g2DYL2Zd6BY@public.gmane.org>
2017-02-07 9:17 ` Raju Lakkaraju
[not found] ` <20170207091737.GA24582-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2017-02-07 13:12 ` Andrew Lunn
[not found] ` <1485953626-25780-2-git-send-email-Raju.Lakkaraju-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2017-02-01 18:02 ` Rob Herring
2017-02-01 18:04 ` [PATCH v2 net-next] net: phy: Add LED mode driver for Microsemi Florian Fainelli
2017-02-07 13:39 ` Raju Lakkaraju [this message]
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=20170207133908.GA29408@microsemi.com \
--to=raju.lakkaraju@microsemi.com \
--cc=Allan.Nielsen@microsemi.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).