linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Popple <alistair@popple.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-usb@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 5/7] IBM Akebono: Add support to the EHCI platform driver for Akebono
Date: Wed, 06 Nov 2013 14:50:28 +1100	[thread overview]
Message-ID: <2440701.siW6M1PPWz@mexican> (raw)
In-Reply-To: <1383681133.4776.95.camel@pasglop>

On Wed, 6 Nov 2013 06:52:13 Benjamin Herrenschmidt wrote:

[snip]

> 
> Why ? Do we need to add an entry for every platform in there ? Besides,
> it probably should be the SoC name not the platform here....
> 
> Why not simply a generic compatible "usb-ehci" ? It's a standard
> programming interface, there are no specific quirks, we shouldn't
> need to have to add new entries to the driver like that for every
> new SoC/platform.
> 

Actually a grep of "usb-ehci" turns up the ehci-ppc-of driver which I somehow 
missed. This driver works and uses .compatible = "usb-ehci" so I can use that 
instead if that is preferable?

However it is basically the same as the ehci-platform driver so I guess at 
some point the two should be merged...

> > > @@ -229,7 +230,7 @@ static struct platform_driver ehci_platform_driver =
> > > {
> > > 
> > >  		.owner	= THIS_MODULE,
> > >  		.name	= "ehci-platform",
> > >  		.pm	= &ehci_platform_pm_ops,
> > > 
> > > -		.of_match_table = vt8500_ehci_ids,
> > > +		.of_match_table = ehci_platform_ids,
> > > 
> > >  	}
> > >  
> > >  };
> > 
> > Acked-by: Alan Stern <stern@rowland.harvard.edu>
> > 
> > _______________________________________________
> > Linuxppc-dev mailing list
> > Linuxppc-dev@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2013-11-06  3:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  5:31 [PATCH 1/7] IBM Akebono: Add support to AHCI platform driver Alistair Popple
2013-11-05  5:31 ` [PATCH 2/7] IBM Akebono: Add a SDHCI " Alistair Popple
2013-11-05  5:31 ` [PATCH 3/7] IBM Akebono: Add support for a new PHY to the IBM emac driver Alistair Popple
2013-11-05 18:16   ` Ben Hutchings
2013-11-05 19:54     ` Benjamin Herrenschmidt
2013-11-05 23:11       ` Ben Hutchings
2013-11-06  1:34         ` Alistair Popple
2013-11-06 16:40           ` Ben Hutchings
2013-11-07  2:39             ` Alistair Popple
2013-11-05 18:47   ` Florian Fainelli
2013-11-06  0:08     ` Alistair Popple
2013-11-06  0:16       ` Florian Fainelli
2013-11-06  1:38         ` Alistair Popple
2013-11-06  2:17           ` Benjamin Herrenschmidt
2013-11-06  2:23             ` Florian Fainelli
2013-11-05  5:31 ` [PATCH 4/7] IBM Akebono: Add support to the OHCI platform driver for Akebono Alistair Popple
2013-11-05 15:04   ` Alan Stern
2013-11-07  3:34     ` Alistair Popple
2013-11-07  4:55       ` Benjamin Herrenschmidt
2013-11-07 15:04       ` Alan Stern
2013-11-05  5:31 ` [PATCH 5/7] IBM Akebono: Add support to the EHCI " Alistair Popple
2013-11-05 15:04   ` Alan Stern
2013-11-05 19:52     ` Benjamin Herrenschmidt
2013-11-06  3:50       ` Alistair Popple [this message]
2013-11-06  3:58         ` Benjamin Herrenschmidt
2013-11-06  7:39           ` [RFC PATCH] ehci-platform: Merge ppc-of EHCI driver into the ehci-platform driver Alistair Popple
2013-11-06 16:14             ` Alan Stern
2013-11-07  2:34               ` Alistair Popple
2013-11-06 19:57             ` Benjamin Herrenschmidt
2013-11-07  2:35               ` Alistair Popple
2013-11-05  5:31 ` [PATCH 6/7] IBM Currituck: Clean up board specific code before adding Akebono code Alistair Popple
2013-11-05  5:31 ` [PATCH 7/7] IBM Akebono: Add the Akebono platform Alistair Popple

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=2440701.siW6M1PPWz@mexican \
    --to=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stern@rowland.harvard.edu \
    /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).