From: jogo@openwrt.org (Jonas Gorski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] net: mv643xx_eth: fix DT port device name
Date: Mon, 8 Jul 2013 00:05:40 +0200 [thread overview]
Message-ID: <20130708000540.00004b37@unknown> (raw)
In-Reply-To: <20130707234341.0000721b@unknown>
On Sun, 7 Jul 2013 23:43:41 +0200
Jonas Gorski <jogo@openwrt.org> wrote:
> On Sun, 7 Jul 2013 22:33:51 +0200
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>
> > Device tree support added to Marvell MV643xx ethernet driver registers
> > port devices from port device nodes found on the corresponding controller
> > node. The current port device name will cause the second controller to
> > fail on registration because of two identical device names. This fixes
> > the issue by taking the device node's name also as port device name.
> >
> > Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> > Reported-by: Jonas Gorski <jogo@openwrt.org>
> > ---
> > Cc: Lennert Buytenhek <buytenh@wantstofly.org>
> > Cc: Jonas Gorski <jogo@openwrt.org>
> > Cc: netdev at vger.kernel.org
> > Cc: linux-arm-kernel at lists.infradead.org
> > Cc: linux-kernel at vger.kernel.org
> > ---
> > drivers/net/ethernet/marvell/mv643xx_eth.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c b/drivers/net/ethernet/marvell/mv643xx_eth.c
> > index 6495bea..1f3a03d 100644
> > --- a/drivers/net/ethernet/marvell/mv643xx_eth.c
> > +++ b/drivers/net/ethernet/marvell/mv643xx_eth.c
> > @@ -2521,7 +2521,7 @@ static int mv643xx_eth_shared_of_add_port(struct platform_device *pdev,
> > of_property_read_u32(pnp, "duplex", &ppd.duplex);
> > }
> >
> > - ppdev = platform_device_alloc(MV643XX_ETH_NAME, ppd.port_number);
> > + ppdev = platform_device_alloc(pnp->name, ppd.port_number);
> > if (!ppdev)
> > return -ENOMEM;
> > ppdev->dev.coherent_dma_mask = DMA_BIT_MASK(32);
>
> This breaks ethernet completely, as there is no platform driver
> registered for pnp->name ("ethernetX-port"), only for MV643XX_ETH_NAME.
Looking back at our conversation, this is my fault.
I actually did not change this part as you asked, but I saw the
alloc/del issue with port 0, then added the counter and also only
replaced the ppd.port_number in the alloc with it. I had completely
forgotten at that time to replace the device name; else I would
have caught it back then.
I only caught it now because I tried your patch and wondered why there
wasn't anything registered, not because I saw the problem by review.
Sorry for that.
Regards
Jonas
next prev parent reply other threads:[~2013-07-07 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 20:33 [PATCH] net: mv643xx_eth: fix DT port device name Sebastian Hesselbarth
2013-07-07 21:43 ` Jonas Gorski
2013-07-07 21:58 ` Sebastian Hesselbarth
2013-07-07 22:44 ` [PATCH] net: mv643xx_eth: do not use port number as platform device id Jonas Gorski
2013-07-07 22:05 ` Jonas Gorski [this message]
2013-07-10 10:29 ` [PATCH] net: mv643xx_eth: fix DT port device name Gerlando Falauto
2013-07-10 22:59 ` Sebastian Hesselbarth
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=20130708000540.00004b37@unknown \
--to=jogo@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.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).