On Wed, Jul 15, 2015 at 12:05:25PM +0200, Sascha Hauer wrote:
> On Wed, Jul 15, 2015 at 10:45:42AM +0200, Ludovic Desroches wrote:
> > On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
> > > On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
> > > > Using a string to
On Wed, Jul 15, 2015 at 10:45:42AM +0200, Ludovic Desroches wrote:
> On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
> > On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
> > > Using a string to describe a pin in the device tree can be not enough.
> > > Some
On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
> On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
> > Using a string to describe a pin in the device tree can be not enough.
> > Some controllers may need extra information to fully describe a pin. It
> > concerns
On Wed, Jul 15, 2015 at 10:45:42AM +0200, Ludovic Desroches wrote:
On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may
On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly
On Wed, Jul 15, 2015 at 12:05:25PM +0200, Sascha Hauer wrote:
On Wed, Jul 15, 2015 at 10:45:42AM +0200, Ludovic Desroches wrote:
On Tue, Jul 14, 2015 at 08:13:59AM +0200, Sascha Hauer wrote:
On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
Using a string to describe a
On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
> Using a string to describe a pin in the device tree can be not enough.
> Some controllers may need extra information to fully describe a pin. It
> concerns mainly controllers which have a per pin muxing approach which
> don't fit
On Wed, Jun 10, 2015 at 05:04:57PM +0200, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have a per pin muxing approach which
don't fit
On Mon, Jun 15, 2015 at 10:01:29AM -0600, Stephen Warren wrote:
> On 06/10/2015 09:04 AM, Ludovic Desroches wrote:
> >Using a string to describe a pin in the device tree can be not enough.
> >Some controllers may need extra information to fully describe a pin. It
> >concerns mainly controllers
On Mon, Jun 15, 2015 at 10:01:29AM -0600, Stephen Warren wrote:
On 06/10/2015 09:04 AM, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have
On 06/10/2015 09:04 AM, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have a per pin muxing approach which
don't fit well the notions of
On 06/10/2015 09:04 AM, Ludovic Desroches wrote:
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have a per pin muxing approach which
don't fit well the notions of
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have a per pin muxing approach which
don't fit well the notions of groups and functions.
Instead of using a pin name, a
Using a string to describe a pin in the device tree can be not enough.
Some controllers may need extra information to fully describe a pin. It
concerns mainly controllers which have a per pin muxing approach which
don't fit well the notions of groups and functions.
Instead of using a pin name, a
14 matches
Mail list logo
