From: Lee Jones <lee.jones@linaro.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com
Subject: Re: [PATCH v2 4/5] phy: miphy365x: Represent each PHY channel as a subnode
Date: Wed, 2 Jul 2014 12:34:28 +0100 [thread overview]
Message-ID: <20140702113428.GA16724@lee--X1> (raw)
In-Reply-To: <53B3DE4F.1040100@ti.com>
> On Monday 30 June 2014 08:11 PM, Lee Jones wrote:
> > phy: miphy365x: Represent each PHY channel as a DT subnode
> >
> > This has the added advantages of being able to enable/disable each
> > of the channels as simply as enabling/disabling the DT node.
> >
> > Suggested-by: Kishon Vijay Abraham I <kishon@ti.com>
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> >
> > diff --git a/drivers/phy/phy-miphy365x.c b/drivers/phy/phy-miphy365x.c
> > index 1109f42..2c4ea6e 100644
> > --- a/drivers/phy/phy-miphy365x.c
> > +++ b/drivers/phy/phy-miphy365x.c
[...]
> > -static int miphy365x_of_probe(struct device_node *np,
> > +static int miphy365x_of_probe(struct platform_device *pdev,
> > struct miphy365x_dev *phy_dev)
> > {
> > + struct device_node *np = pdev->dev.of_node;
> > + struct device_node *child;
> > + int child_count = 0;
> > +
> > + for_each_child_of_node(np, child)
> > + child_count++;
>
> use of_get_child_count() instead.
Ah, nice. I'll do that.
[...]
> I think you can merge this to your original patch.
I can do that, but I thought It'd be nice to keep some history and
show the migration over to a different setup. This is particularly
important for when we back-port the changes back into the internal
development kernel.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-07-02 11:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:01 [PATCH 0/5] phy: miphy365x: Introduce support for MiPHY365x Lee Jones
2014-06-30 13:01 ` [PATCH 1/5] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-07-02 9:24 ` Kishon Vijay Abraham I
2014-07-02 12:06 ` Lee Jones
2014-07-03 9:06 ` Kishon Vijay Abraham I
2014-06-30 13:01 ` [PATCH 2/5] phy: miphy365x: Add MiPHY365x header file for DT x Driver defines Lee Jones
2014-07-02 9:28 ` Kishon Vijay Abraham I
2014-07-02 12:02 ` Lee Jones
2014-06-30 13:01 ` [PATCH 3/5] phy: miphy365x: Provide support for the MiPHY356x Generic PHY Lee Jones
2014-07-02 10:19 ` Kishon Vijay Abraham I
2014-07-02 12:00 ` Lee Jones
2014-07-03 8:07 ` Lee Jones
2014-07-03 10:06 ` Kishon Vijay Abraham I
2014-07-04 13:55 ` Gabriel Fernandez
2014-07-08 7:15 ` Lee Jones
2014-06-30 13:01 ` [PATCH 4/5] phy: miphy365x: Represent each PHY channel as a subnode Lee Jones
2014-06-30 13:06 ` [STLinux Kernel] " Maxime Coquelin
2014-06-30 13:52 ` Lee Jones
2014-06-30 14:41 ` [PATCH v2 " Lee Jones
2014-07-02 10:26 ` Kishon Vijay Abraham I
2014-07-02 11:34 ` Lee Jones [this message]
2014-07-02 11:57 ` Kishon Vijay Abraham I
2014-07-02 12:19 ` Lee Jones
2014-06-30 13:01 ` [PATCH 5/5] ARM: DT: STi: Add DT node for MiPHY365x Lee Jones
2014-07-03 14:08 ` Gabriel Fernandez
2014-07-02 9:19 ` [PATCH 0/5] phy: miphy365x: Introduce support " Kishon Vijay Abraham I
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=20140702113428.GA16724@lee--X1 \
--to=lee.jones@linaro.org \
--cc=kernel@stlinux.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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