On Tuesday 16 September 2014, Pankaj Dubey wrote:
> Hi Arnd, Lee Jones,
> > On Thu, 04 Sep 2014 10:15:27 +0530
> > Pankaj Dubey wrote:
>
> Any update on this patch. As already it has been tested on two DT based
> platforms.
>
> If you think that we can go ahead and break clps711x till it gets
g.com;
> > > chow@samsung.com; lee.jo...@linaro.org; Michal Simek;
> > > linux-arm-ker...@lists.infradead.org;
> > Mark
> > > Brown
> > > Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
> > platform
> > > devices
> > >
&
...@lists.infradead.org;
Mark
Brown
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
platform
devices
On Wed, 03 Sep 2014 15:49:04 +0200
Arnd Bergmann a...@arndb.de wrote:
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
I checked that part
On Tuesday 16 September 2014, Pankaj Dubey wrote:
Hi Arnd, Lee Jones,
On Thu, 04 Sep 2014 10:15:27 +0530
Pankaj Dubey pankaj.du...@samsung.com wrote:
Any update on this patch. As already it has been tested on two DT based
platforms.
If you think that we can go ahead and break clps711x
> Mark
> > Brown
> > Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
> platform
> > devices
> >
> > On Wed, 03 Sep 2014 15:49:04 +0200
> > Arnd Bergmann wrote:
> >
> > > On Wednesday 03 September 2014 15:16:11 Boris BREZILLO
: syscon: Decouple syscon interface from
platform
devices
On Wed, 03 Sep 2014 15:49:04 +0200
Arnd Bergmann a...@arndb.de wrote:
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
I checked that part, and it appears most of the code is already
there (see usage
org;
> Mark
> > Brown
> > Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
> platform
> > devices
> >
> > On Wed, 03 Sep 2014 15:49:04 +0200
> > Arnd Bergmann wrote:
> >
> > > On Wednesday 03 September 201
v2] mfd: syscon: Decouple syscon interface from
platform
devices
On Wed, 03 Sep 2014 15:49:04 +0200
Arnd Bergmann a...@arndb.de wrote:
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
I checked that part, and it appears most of the code is already
there (see
g; lee.jo...@linaro.org; kgene@samsung.com;
> > li...@arm.linux.org.uk; vikas.saj...@samsung.com; jo...@samsung.com;
> > naus...@samsung.com; thomas...@samsung.com; chow@samsung.com;
> > tomasz.f...@gmail.com; Tomasz Figa; Alexander Shiyan; Michal Simek
> > Subject: Re: [PATCH v2]
r.kernel.org;
thomas...@samsung.com;
> tomasz.f...@gmail.com; vikas.saj...@samsung.com; chow@samsung.com;
> lee.jo...@linaro.org; Michal Simek; linux-arm-ker...@lists.infradead.org;
Mark
> Brown
> Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
platform
> devices
>
sung.com; jo...@samsung.com;
> naus...@samsung.com; thomas...@samsung.com; chow@samsung.com;
> tomasz.f...@gmail.com; Tomasz Figa; Alexander Shiyan; Michal Simek
> Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
platform
> devices
>
> On Tuesday 02 September 20
On Wed, 03 Sep 2014 15:49:04 +0200
Arnd Bergmann wrote:
> On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
> > I checked that part, and it appears most of the code is already there
> > (see usage of regmap_attach_dev function here [1]).
> >
> > The only problem I see is that
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
> I checked that part, and it appears most of the code is already there
> (see usage of regmap_attach_dev function here [1]).
>
> The only problem I see is that errors are still printed with dev_err,
> which, AFAIK, will trigger a
Hi,
I'm joining the thread cause I'm really interested in having a syscon
dev available during early init (I need it to share at91 PMC
registers among several subsystems, one of this subsystem being the CCF
which is called during early ARM boot process to register system
clocks).
On Tue, 02 Sep
Hi,
I'm joining the thread cause I'm really interested in having a syscon
dev available during early init (I need it to share at91 PMC
registers among several subsystems, one of this subsystem being the CCF
which is called during early ARM boot process to register system
clocks).
On Tue, 02 Sep
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
I checked that part, and it appears most of the code is already there
(see usage of regmap_attach_dev function here [1]).
The only problem I see is that errors are still printed with dev_err,
which, AFAIK, will trigger a kernel
On Wed, 03 Sep 2014 15:49:04 +0200
Arnd Bergmann a...@arndb.de wrote:
On Wednesday 03 September 2014 15:16:11 Boris BREZILLON wrote:
I checked that part, and it appears most of the code is already there
(see usage of regmap_attach_dev function here [1]).
The only problem I see is that
...@samsung.com;
naus...@samsung.com; thomas...@samsung.com; chow@samsung.com;
tomasz.f...@gmail.com; Tomasz Figa; Alexander Shiyan; Michal Simek
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
platform
devices
On Tuesday 02 September 2014 20:12:15 Pankaj Dubey wrote
...@samsung.com;
tomasz.f...@gmail.com; vikas.saj...@samsung.com; chow@samsung.com;
lee.jo...@linaro.org; Michal Simek; linux-arm-ker...@lists.infradead.org;
Mark
Brown
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
platform
devices
On Wed, 03 Sep 2014 15:49:04 +0200
@samsung.com;
li...@arm.linux.org.uk; vikas.saj...@samsung.com; jo...@samsung.com;
naus...@samsung.com; thomas...@samsung.com; chow@samsung.com;
tomasz.f...@gmail.com; Tomasz Figa; Alexander Shiyan; Michal Simek
Subject: Re: [PATCH v2] mfd: syscon: Decouple syscon interface from
On Tue, Sep 2, 2014 at 8:12 PM, Pankaj Dubey wrote:
> Currently a syscon entity can only be registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain cases it is required to bind a device with it's dedicated
> driver rather than binding with
On Tuesday 02 September 2014 19:42:52 Alexander Shiyan wrote:
> > > -struct regmap *syscon_regmap_lookup_by_pdevname(const char *s)
> > > -{
> > > - struct device *dev;
> > > - struct syscon *syscon;
> > > -
> > > - dev = driver_find_device(_driver.driver, NULL, (void *)s,
> > > -
Tue, 02 Sep 2014 17:20:03 +0200 от Arnd Bergmann :
> On Tuesday 02 September 2014 20:12:15 Pankaj Dubey wrote:
> > Currently a syscon entity can only be registered directly through a
> > platform device that binds to a dedicated syscon driver. However in
> > certain cases it is required to bind a
On Tuesday 02 September 2014 20:12:15 Pankaj Dubey wrote:
> Currently a syscon entity can only be registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain cases it is required to bind a device with it's dedicated
> driver rather than binding
On 02.09.2014 16:42, Pankaj Dubey wrote:
> Currently a syscon entity can only be registered directly through a
> platform device that binds to a dedicated syscon driver. However in
> certain cases it is required to bind a device with it's dedicated
> driver rather than binding with syscon driver.
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to bind a device with it's dedicated
driver rather than binding with syscon driver.
For example, certain SoCs (e.g. Exynos) contain
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to bind a device with it's dedicated
driver rather than binding with syscon driver.
For example, certain SoCs (e.g. Exynos) contain
On 02.09.2014 16:42, Pankaj Dubey wrote:
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to bind a device with it's dedicated
driver rather than binding with syscon driver.
On Tuesday 02 September 2014 20:12:15 Pankaj Dubey wrote:
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to bind a device with it's dedicated
driver rather than binding with
Tue, 02 Sep 2014 17:20:03 +0200 от Arnd Bergmann a...@arndb.de:
On Tuesday 02 September 2014 20:12:15 Pankaj Dubey wrote:
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to
On Tuesday 02 September 2014 19:42:52 Alexander Shiyan wrote:
-struct regmap *syscon_regmap_lookup_by_pdevname(const char *s)
-{
- struct device *dev;
- struct syscon *syscon;
-
- dev = driver_find_device(syscon_driver.driver, NULL, (void *)s,
-
On Tue, Sep 2, 2014 at 8:12 PM, Pankaj Dubey pankaj.du...@samsung.com wrote:
Currently a syscon entity can only be registered directly through a
platform device that binds to a dedicated syscon driver. However in
certain cases it is required to bind a device with it's dedicated
driver rather
32 matches
Mail list logo
