On Thu, Jul 12, 2012 at 10:22 AM, Michal Simek wrote:
>
>
>> thats what platform_data is for, if i understand what you mean
>>
>
> That's my understanding too. But the point is how it is passed to the
> driver itself
> because I didn't see any pointer to it there.
>
>
I had an impression that plat
Dear Tomas Hlavacek,
> On Thu, Jul 12, 2012 at 10:22 AM, Michal Simek wrote:
> >> thats what platform_data is for, if i understand what you mean
> >
> > That's my understanding too. But the point is how it is passed to the
> > driver itself
> > because I didn't see any pointer to it there.
>
>
Hi
On Wednesday 11 of July 2012 11:52:13 Michal Simek wrote:
> On 07/10/2012 03:12 PM, Marek Vasut wrote:
> > Dear Wolfgang Denk,
> >
> >> Dear Michal Simek,
> >>
> >> In message<4ffc1ef8.9060...@monstr.eu> you wrote:
> >>> The hardest part I have identify on microblaze was about u-boot
> >>> v
I am missing how you want to pass driver configuration data(addresses,
settings) to the driver. I expect that this must be done out of device
drivers.
thats what platform_data is for, if i understand what you mean
That's my understanding too. But the point is how it is passed to the driver
Dear Simon Glass,
> Hi,
>
> On Tue, Jul 10, 2012 at 3:05 PM, Marek Vasut wrote:
> > Dear Michal Simek,
> >
> > > Hi Simon, Wolfgang and others,
> > >
> > > just want to open new topic about FDT driver initialization function
> > > declaration.
> >
> > Ok, my few nits (with consideration of th
5 matches
Mail list logo