linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk,
	linux-embedded@vger.kernel.org
Subject: Re: [PATCH] phylib: add mdio-gpio bus driver (v2)
Date: Tue, 28 Oct 2008 09:46:00 +0200	[thread overview]
Message-ID: <4906C338.6010300@teltonika.lt> (raw)
In-Reply-To: <20081027143734.GA13565@secretlab.ca>

Grant Likely wrote:
> On Mon, Oct 27, 2008 at 12:53:22PM +0200, Paulius Zaleckas wrote:
>> Useful for machines where PHY control is connected to GPIO.
>> This driver also supports interrupts from PHY.
>>
>> Changes since v1:
>> - fixed releasing of gpio (thanks to Sascha Hauer)
>> - fixed compiling due to bus->dev to bus->parent change
>>
>> Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
>> ---
> 
> Well structured driver.  Comments below.

Thanks for review.

>> diff --git a/drivers/net/phy/mdio-gpio.c b/drivers/net/phy/mdio-gpio.c
>> new file mode 100644
>> index 0000000..585897b
>> --- /dev/null
>> +++ b/drivers/net/phy/mdio-gpio.c

[...]

> 
>> +static int __devinit mdio_gpio_probe(struct platform_device *pdev)
>> +{
>> +	struct mii_bus *new_bus;
>> +	struct mdio_gpio_info *bitbang;
>> +	struct mdio_gpio_platform_data *pdata;
>> +	int ret = -ENOMEM;
>> +	int i;
>> +
>> +	pdata = pdev->dev.platform_data;
>> +	if (pdata == NULL)
>> +		goto out;
>> +
>> +	bitbang = kzalloc(sizeof(struct mdio_gpio_info), GFP_KERNEL);
>> +	if (!bitbang)
>> +		goto out;
>> +
>> +	bitbang->ctrl.ops = &mdio_gpio_ops;
>> +	bitbang->mdc = pdata->mdc;
>> +	bitbang->mdio = pdata->mdio;
>> +
>> +	if (gpio_request(bitbang->mdc, "mdc"))
>> +		goto out_free_bitbang;
>> +
>> +	if (gpio_request(bitbang->mdio, "mdio"))
>> +		goto out_free_mdc;
>> +
>> +	new_bus = alloc_mdio_bitbang(&bitbang->ctrl);
>> +	if (!new_bus)
>> +		goto out_free_gpio;
>> +
>> +	new_bus->name = "GPIO Bitbanged MII",
>> +	snprintf(new_bus->id, MII_BUS_ID_SIZE, "phy%i", pdev->id);
>> +
>> +	new_bus->phy_mask = ~0;
>> +	new_bus->irq = kmalloc(sizeof(int) * PHY_MAX_ADDR, GFP_KERNEL);
>> +	if (!new_bus->irq)
>> +		goto out_free_bus;
> 
> The IRQ array is fixed size.  You can add it to the mdio_gpio_info
> structure and then just set the pointer here so that only one kzalloc
> is needed.

It can be put in mdio_gpio_info, but please note that mdio_gpio_info is
allocated with kzalloc() and irq with kmalloc(), because there is no need
to fill this array with zeros(see below).

>> +
>> +	for (i = 0; i < PHY_MAX_ADDR; i++)
>> +		new_bus->irq[i] = PHY_POLL;
>> +
>> +	for (i = 0; i < pdata->nr_phys; i++) {
>> +		unsigned int phy_addr = pdata->phys[i].addr;
>> +
>> +		BUG_ON(phy_addr >= PHY_MAX_ADDR);
> 
> Is it really worth bringing down the whole kernel when too many phys are
> specified in pdata?
> 
>> +
>> +		new_bus->phy_mask &= ~(1 << phy_addr);
>> +		new_bus->irq[phy_addr] = pdata->phys[i].irq;
>> +	}
>> +
>> +	new_bus->parent = &pdev->dev;
>> +	platform_set_drvdata(pdev, new_bus);
>> +
>> +	ret = mdiobus_register(new_bus);
>> +	if (ret)
>> +		goto out_free_all;
>> +
>> +	return 0;

  parent reply	other threads:[~2008-10-28  7:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 10:53 [PATCH] phylib: add mdio-gpio bus driver (v2) Paulius Zaleckas
2008-10-27 14:37 ` Grant Likely
2008-10-27 16:41   ` David Brownell
2008-10-28  8:55     ` Paulius Zaleckas
2008-10-28  7:46   ` Paulius Zaleckas [this message]
2008-10-28 13:08     ` Grant Likely
2008-10-28 15:17       ` Russell King - ARM Linux
2008-10-28 15:30         ` Grant Likely
2008-10-28 16:16           ` Russell King - ARM Linux
2008-10-27 14:52 ` Mike Frysinger
2008-10-28  8:30   ` Paulius Zaleckas
2008-10-28 10:07     ` Mike Frysinger
2008-10-27 14:53 ` Mike Frysinger
2008-10-28  7:37   ` Paulius Zaleckas
2008-10-28  7:41     ` Mike Frysinger

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=4906C338.6010300@teltonika.lt \
    --to=paulius.zaleckas@teltonika.lt \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --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).