Re: [PATCH 1/2] mmc: omap_hsmmc: Add support for slot-name property in DT

Pali Rohár
2016-01-02T15:22:11Z

[-- Attachment #1: Type: Text/Plain, Size: 1764 bytes --]

On Monday 28 December 2015 15:55:28 Arnd Bergmann wrote:
> On Monday 28 December 2015 15:54:35 Pali Rohár wrote:
> > On Monday 28 December 2015 15:41:01 Arnd Bergmann wrote:
> > > On Monday 28 December 2015 15:28:48 Pali Rohár wrote:
> > > > On Monday 28 December 2015 15:14:50 Arnd Bergmann wrote:
> > > > > On Friday 25 December 2015 13:53:11 Pali Rohár wrote:
> > > > > > On Monday 18 May 2015 17:07:57 Arnd Bergmann wrote:
> > > > > > > On Monday 18 May 2015 08:06:07 Tony Lindgren wrote:
> > > > > > > > * Arnd Bergmann <arnd@arndb.de> [150515 14:26]:
> > > > > > > > > On Friday 15 May 2015 23:22:37 Pali Rohár wrote:
> > > > > > > > If setting up the generic binding is expected to take a
> > > > > > > > while, you can naturally pass it in pdata while waiting
> > > > > > > > for the generic binding to get merged.
> > > > > > >
> > > > > > > Yes, good idea. So the n900 machine can use auxdata to
> > > > > > > pass this for the time being, while the binding and
> > > > > > > generic implementation is being worked out.
> > > > > >
> > > > > > Ok, so what is needed to finish this patch series?
> > > > >
> > > > > I don't know where we are at this point. Has either the
> > > > > auxdata approach or the generic binding been worked on at
> > > > > all?
> > > >
> > > > What are auxdata data?
> > >
> > > I mean you can add the platform data to the omap_auxdata_lookup[]
> > > table for this board.
> >
> > But can I mix data from omap3-n900.dts and omap_auxdata_lookup[]?
>
> Yes.
>
> Arnd

Hm... looks like it is not possible. omap_hsmmc driver ignores any
supplied platform data if there are device tree data. So array
omap_auxdata_lookup[] does not help.

--
Pali Rohár
pali.rohar@gmail.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]