On Wed, 22 Oct 2014, Pankaj Dubey wrote:
> Hello Lee,
>
> On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
> > On Tue, 30 Sep 2014, Pankaj Dubey wrote:
> >
> > > Currently a syscon entity can be only registered directly through a
> > > platform device that binds to a dedicated syscon
Hello Lee,
On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
> On Tue, 30 Sep 2014, Pankaj Dubey wrote:
>
> > Currently a syscon entity can be only registered directly through a
> > platform device that binds to a dedicated syscon driver. However in
> > certain use cases it is desirable to
Hello Lee,
On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
On Tue, 30 Sep 2014, Pankaj Dubey wrote:
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a
On Wed, 22 Oct 2014, Pankaj Dubey wrote:
Hello Lee,
On Tuesday, October 07, 2014 2:39 PM, Lee Jones wrote,
On Tue, 30 Sep 2014, Pankaj Dubey wrote:
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However
On Tue, 30 Sep 2014, Pankaj Dubey wrote:
> Currently a syscon entity can be only registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain use cases it is desirable to make a device used with another
> driver a syscon interface provider.
>
>
On Tue, 30 Sep 2014, Pankaj Dubey wrote:
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For
On Mon, 06 Oct 2014, Pankaj Dubey wrote:
> Hi Lee,
>
> On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
> > Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
> > devices
> >
> > Pankaj,
> >
> > On Tue, Sep
Hi Lee,
On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
> Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
> devices
>
> Pankaj,
>
> On Tue, Sep 30, 2014 at 1:35 AM, Pankaj Dubey
> wrote:
> > Currently a syscon entity can
Hi Lee,
On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
devices
Pankaj,
On Tue, Sep 30, 2014 at 1:35 AM, Pankaj Dubey pankaj.du...@samsung.com
wrote:
Currently a syscon entity can be only
On Mon, 06 Oct 2014, Pankaj Dubey wrote:
Hi Lee,
On Tuesday, September 30, 2014 9:39 PM Doug Anderson wrote,
Subject: Re: [PATCH v7] mfd: syscon: Decouple syscon interface from platform
devices
Pankaj,
On Tue, Sep 30, 2014 at 1:35 AM, Pankaj Dubey pankaj.du...@samsung.com
Pankaj,
On Tue, Sep 30, 2014 at 1:35 AM, Pankaj Dubey wrote:
> Currently a syscon entity can be only registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain use cases it is desirable to make a device used with another
> driver a syscon
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
driver a syscon interface provider.
For example, certain SoCs (e.g. Exynos) contain system
Pankaj,
On Tue, Sep 30, 2014 at 1:35 AM, Pankaj Dubey pankaj.du...@samsung.com wrote:
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain use cases it is desirable to make a device used with another
14 matches
Mail list logo