We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part. Also improve
the check for a parent.
Signed-off-by: Wolfram Sang
Cc: Richard Röjfors
---
drivers/mmc/host/sdhci-pltfm.c | 10 +++---
drivers/mmc/host/sdhci-pltfm.h |
We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part. Also improve
the check for a parent.
Signed-off-by: Wolfram Sang
Cc: Richard Röjfors
---
Changes since last version:
* Improved detection of a "real" parent device
driver
On Thu, Sep 30, 2010 at 12:19:38PM +0200, Wolfram Sang wrote:
[...]
> > You're right it wouldn't. But isn't it a bit risky even if you could access
> > it,
> > in the long the platform_data coild point to something that is in the
> > __devinit section
> > or similar?
>
> The use-case we see now
On Thu, Sep 30, 2010 at 11:54:53AM +0200, Richard Röjfors wrote:
> On 09/30/2010 10:16 AM, Wolfram Sang wrote:
> >Hi Richard,
> >
> >On Wed, Sep 29, 2010 at 11:24:25PM +0200, Richard Röjfors wrote:
> >>On 09/29/2010 10:07 PM, Wolfram Sang wrote:
> >>>We need to carry some information per host, e.g.
On 09/30/2010 10:16 AM, Wolfram Sang wrote:
Hi Richard,
On Wed, Sep 29, 2010 at 11:24:25PM +0200, Richard Röjfors wrote:
On 09/29/2010 10:07 PM, Wolfram Sang wrote:
We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part. Also do
Hi Richard,
On Wed, Sep 29, 2010 at 11:24:25PM +0200, Richard Röjfors wrote:
> On 09/29/2010 10:07 PM, Wolfram Sang wrote:
> >We need to carry some information per host, e.g. the clock. Add a
> >structure for it and initialize it in the generic part. Also do not use
> >the parent of the platform_d
On 09/29/2010 10:07 PM, Wolfram Sang wrote:
We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part. Also do not use
the parent of the platform_device (if it is available), this breaks the
clock-matching on ARM.
The reason it's th
We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part. Also do not use
the parent of the platform_device (if it is available), this breaks the
clock-matching on ARM.
Signed-off-by: Wolfram Sang
Cc: Richard Röjfors
---
Changes si
On Tue, Sep 28, 2010 at 06:54:47AM -0700, Philip Rakity wrote:
> taking this off line for a bit (if you don't mind)
Actually, I do. Going back to the list.
> I really like what you are doing but it does not go far enough. The
> controller I work on is somewhat funny and broken. It needs to do
On Tue, Sep 28, 2010 at 8:36 AM, Wolfram Sang wrote:
> We need to carry some information per host, e.g. the clock. Add a
> structure for it and initialize it in the generic part.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Change since last version:
>
> * include clk.h
>
> drivers/mmc/host/sdhci-p
On Tue, Sep 28, 2010 at 02:36:41PM +0200, Wolfram Sang wrote:
> We need to carry some information per host, e.g. the clock. Add a
> structure for it and initialize it in the generic part.
>
> Signed-off-by: Wolfram Sang
> ---
[...]
> +++ b/drivers/mmc/host/sdhci-pltfm.h
> @@ -11,8 +11,14 @@
> #i
We need to carry some information per host, e.g. the clock. Add a
structure for it and initialize it in the generic part.
Signed-off-by: Wolfram Sang
---
Change since last version:
* include clk.h
drivers/mmc/host/sdhci-pltfm.c |7 +--
drivers/mmc/host/sdhci-pltfm.h |6 ++
2 f
12 matches
Mail list logo
