On 06/29/2013 10:22 AM, Marc Dietrich wrote:
> On Friday 28 June 2013 09:13:38 Stephen Warren wrote:
>> On 06/27/2013 12:26 PM, Marc Dietrich wrote:
...
>>> I'm puzzling for some time now to find a binding for a mfd device. So
>>> let's
>>> start with something I think I have learned already, let's
On Friday 28 June 2013 09:13:38 Stephen Warren wrote:
> On 06/27/2013 12:26 PM, Marc Dietrich wrote:
> > Hi,
>
> (CC'ing linux-tegra)
>
> > I'm puzzling for some time now to find a binding for a mfd device. So
> > let's
> > start with something I think I have learned already, let's describe the
>
On Fri, Jun 28, 2013 at 09:13:38AM -0600, Stephen Warren wrote:
> On 06/27/2013 12:26 PM, Marc Dietrich wrote:
[...]
> > Another question is how the children will get their platform data. I guess
> > they will just walk the device tree of their parent node and search for it,
> > but maybe there i
On 06/27/2013 12:26 PM, Marc Dietrich wrote:
> Hi,
(CC'ing linux-tegra)
> I'm puzzling for some time now to find a binding for a mfd device. So let's
> start with something I think I have learned already, let's describe the
> hardware.
>
> Here the problem starts, because the nvec (nvidia [pro
Hi,
I'm puzzling for some time now to find a binding for a mfd device. So let's
start with something I think I have learned already, let's describe the
hardware.
Here the problem starts, because the nvec (nvidia [protocol] compliant
embedded controller) isn't a well defined piece of silicon at
