From: Florian Fainelli <f.fainelli@gmail.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Cc: Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Christian Gmeiner <christian.gmeiner@gmail.com>
Subject: Re: [PATCHv4 2/5] net: phy: extend fixed driver with fixed_phy_register()
Date: Thu, 03 Sep 2015 12:23:19 -0700 [thread overview]
Message-ID: <55E89E27.6050708@gmail.com> (raw)
In-Reply-To: <55E89D83.1090401@cogentembedded.com>
On 03/09/15 12:20, Sergei Shtylyov wrote:
> Hello.
>
> On 05/16/2014 06:14 PM, Thomas Petazzoni wrote:
>
>> The existing fixed_phy_add() function has several drawbacks that
>> prevents it from being used as is for OF-based declaration of fixed
>> PHYs:
>>
>> * The address of the PHY on the fake bus needs to be passed, while a
>> dynamic allocation is desired.
>>
>> * Since the phy_device instantiation is post-poned until the next
>> mdiobus scan, there is no way to associate the fixed PHY with its
>> OF node, which later prevents of_phy_connect() from finding this
>> fixed PHY from a given OF node.
>>
>> To solve this, this commit introduces fixed_phy_register(), which will
>> allocate an available PHY address, add the PHY using fixed_phy_add()
>> and instantiate the phy_device structure associated with the provided
>> OF node.
>>
>> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
>> Acked-by: Grant Likely <grant.likely@linaro.org>
>> ---
>> drivers/net/phy/fixed.c | 61
>> +++++++++++++++++++++++++++++++++++++++++++++++
>> include/linux/phy_fixed.h | 11 +++++++++
>> 2 files changed, 72 insertions(+)
>>
>> diff --git a/drivers/net/phy/fixed.c b/drivers/net/phy/fixed.c
>> index e41546d..d60d875 100644
>> --- a/drivers/net/phy/fixed.c
>> +++ b/drivers/net/phy/fixed.c
> [...]
>> @@ -203,6 +204,66 @@ err_regs:
> [...]
>> +int fixed_phy_register(unsigned int irq,
>> + struct fixed_phy_status *status,
>> + struct device_node *np)
>> +{
>> + struct fixed_mdio_bus *fmb = &platform_fmb;
>> + struct phy_device *phy;
>> + int phy_addr;
>> + int ret;
>> +
>> + /* Get the next available PHY address, up to PHY_MAX_ADDR */
>> + spin_lock(&phy_fixed_addr_lock);
>> + if (phy_fixed_addr == PHY_MAX_ADDR) {
>> + spin_unlock(&phy_fixed_addr_lock);
>> + return -ENOSPC;
>> + }
>> + phy_addr = phy_fixed_addr++;
>> + spin_unlock(&phy_fixed_addr_lock);
>> +
>> + ret = fixed_phy_add(PHY_POLL, phy_addr, status);
>
> Was rummaging in the fixed_phy driver and a bug sprang right at me:
> 'phy' should have been passed here, not PHY_POLL. Luckily, all callers
> pass PHY_POLL anyway...
Are we looking at the same header file for the prototype of fixed_phy_add()?
extern int fixed_phy_add(unsigned int irq, int phy_id,
struct fixed_phy_status *status,
int link_gpio);
First argument is correct here.. at any rate, if something needs fixing,
just go ahead and submit a patch.
--
Florian
next prev parent reply other threads:[~2015-09-03 19:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 14:14 [PATCHv4 0/5] Add DT support for fixed PHYs Thomas Petazzoni
2014-05-16 14:14 ` [PATCHv4 1/5] net: phy: decouple PHY id and PHY address in fixed PHY driver Thomas Petazzoni
2014-05-16 18:30 ` Florian Fainelli
2014-05-16 14:14 ` [PATCHv4 2/5] net: phy: extend fixed driver with fixed_phy_register() Thomas Petazzoni
2014-05-16 18:28 ` Florian Fainelli
2015-09-03 19:20 ` Sergei Shtylyov
2015-09-03 19:23 ` Florian Fainelli [this message]
2015-09-03 19:35 ` Sergei Shtylyov
2015-09-03 19:37 ` Sergei Shtylyov
2015-09-03 19:38 ` Florian Fainelli
2015-09-03 19:55 ` Sergei Shtylyov
2014-05-16 14:14 ` [PATCHv4 3/5] of: provide a binding for fixed link PHYs Thomas Petazzoni
[not found] ` <1400249647-4643-4-git-send-email-thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-05-16 18:29 ` Florian Fainelli
2014-05-16 14:14 ` [PATCHv4 4/5] net: mvneta: add support for fixed links Thomas Petazzoni
2014-05-16 14:14 ` [PATCHv4 5/5] ARM: mvebu: use the fixed-link PHY DT binding for the Armada XP Matrix board Thomas Petazzoni
[not found] ` <1400249647-4643-1-git-send-email-thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2014-05-16 18:27 ` [PATCHv4 0/5] Add DT support for fixed PHYs Florian Fainelli
2014-05-16 20:46 ` Thomas Petazzoni
2014-05-16 21:20 ` David Miller
2014-05-18 10:18 ` Thomas Petazzoni
2014-05-18 17:21 ` Florian Fainelli
2014-05-18 17:46 ` Thomas Petazzoni
2014-05-18 23:07 ` Jason Cooper
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=55E89E27.6050708@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alior@marvell.com \
--cc=christian.gmeiner@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
/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).