linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()
Date: Thu, 19 Jan 2017 16:35:48 +0000	[thread overview]
Message-ID: <20170119163548.GG27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170119163013.GA22777@kroah.com>

On Thu, Jan 19, 2017 at 05:30:13PM +0100, Greg KH wrote:
> On Thu, Jan 19, 2017 at 03:53:15PM +0100, Andrew Lunn wrote:
> > > > > struct dsa_platform_data {
> > > > >         /*
> > > > >          * Reference to a Linux network interface that connects
> > > > >          * to the root switch chip of the tree.
> > > > >          */
> > > > >         struct device   *netdev;
> > > 
> > > This I think is the oddest thing, why do you need to have the "root
> > > switch" here?  You seem to have dropped the next value in this
> > > structure:
> > > 	struct net_device *of_netdev;
> > 
> > We are implementing platform_data for devices which don't support
> > device tree. When using OF, we don't have any of these issues. We can
> > go straight to the device.
> > 
> > It is a bit convoluted, but look at
> > arch/arm/mach-orion5x/rd88f5181l-ge-setup.c. It defines the start of
> > the dsa_platform_data in that file. It then gets passed through
> > common.c: orion5x_eth_switch_init() to 
> > arch/arm/plat-orion/common.c:orion_ge00_switch_init() :
> > 
> > void __init orion_ge00_switch_init(struct dsa_platform_data *d)
> > {
> >         int i;
> > 
> >         d->netdev = &orion_ge00.dev;
> >         for (i = 0; i < d->nr_chips; i++)
> >                 d->chip[i].host_dev = &orion_ge_mvmdio.dev;
> > 
> >         platform_device_register_data(NULL, "dsa", 0, d, sizeof(d));
> > }
> > 
> > Where we have
> > 
> > static struct platform_device orion_ge00 = {
> >         .name           = MV643XX_ETH_NAME,
> >         .id             = 0,
> >         .num_resources  = 1,
> >         .resource       = orion_ge00_resources,
> >         .dev            = {
> >                 .coherent_dma_mask      = DMA_BIT_MASK(32),
> >         },
> > };
> > 
> > So this is the platform device for the Ethernet device. We cannot go
> > to the net_device, because it does not exist until this Ethernet
> > platform device is instantiated.
> 
> Ok, fine, but why isn't the ethernet device a child of this platform
> device?  Why is it floating around somewhere else?  You don't see that
> happening for other devices.

The ethernet device is not a child of the DSA device.  I'm going to
send a mail I've had queued up for a few hours redoing Andrew's
ASCII art, because I think that's what's causing the confusion here,
provided I haven't discarded it.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2017-01-19 16:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14 21:47 [PATCH net-next v3 00/10] net: dsa: Support for pdata in dsa2 Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 01/10] net: dsa: Pass device pointer to dsa_register_switch Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 02/10] net: dsa: Make most functions take a dsa_port argument Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 03/10] net: dsa: Suffix function manipulating device_node with _dn Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 04/10] net: dsa: Move ports assignment closer to error checking Florian Fainelli
2017-01-15 10:17   ` Sergei Shtylyov
2017-01-14 21:47 ` [PATCH net-next v3 05/10] drivers: base: Add device_find_class() Florian Fainelli
2017-01-15 11:04   ` Greg KH
2017-01-15 17:39     ` Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class() Florian Fainelli
2017-01-15 11:06   ` Greg KH
2017-01-15 17:27     ` Florian Fainelli
2017-01-15 17:39       ` Greg KH
2017-01-15 17:52         ` Florian Fainelli
2017-01-15 19:16           ` Andrew Lunn
2017-01-16 20:01             ` Florian Fainelli
2017-01-18  7:06               ` Greg KH
2017-01-19 14:28               ` Greg KH
2017-01-19 14:53                 ` Andrew Lunn
2017-01-19 16:30                   ` Greg KH
2017-01-19 16:35                     ` Russell King - ARM Linux [this message]
2017-01-19 16:51                   ` Russell King - ARM Linux
2017-01-19 18:12                     ` Florian Fainelli
2017-01-24 18:59                       ` Florian Fainelli
2017-01-25 21:25                         ` Greg KH
2017-01-30 22:46                           ` Florian Fainelli
2017-02-10 13:02                     ` Greg KH
2017-02-10 18:30                       ` Florian Fainelli
2017-02-12 12:56                         ` Greg KH
2017-01-14 21:47 ` [PATCH net-next v3 07/10] net: Relocate dev_to_net_device() into core Florian Fainelli
2017-01-15 11:07   ` Greg KH
2017-01-15 17:20     ` Florian Fainelli
2017-01-15 17:40       ` Greg KH
2017-01-14 21:47 ` [PATCH net-next v3 08/10] net: dsa: Add support for platform data Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 09/10] net: phy: Allow pre-declaration of MDIO devices Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 10/10] ARM: orion: Register DSA switch as a MDIO device Florian Fainelli
2017-01-15 11:08 ` [PATCH net-next v3 00/10] net: dsa: Support for pdata in dsa2 Greg KH
2017-01-15 17:40   ` Florian Fainelli
2017-01-15 17:49     ` Greg KH

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=20170119163548.GG27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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).