On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 17:04:26 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
Maybe I'm misreading the patch, but I don't see how it creates a
migration path. What I want to end up with is infrastructure that
lets anybody
On Tuesday 02 September 2014 09:05:16 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 17:04:26 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
Maybe I'm misreading the patch, but I don't see how it creates a
migration path. What I
...@vger.kernel.org;
jo...@samsung.com; vikas.saj...@samsung.com; linux-samsung-
s...@vger.kernel.org; broo...@kernel.org; thomas...@samsung.com;
chow@samsung.com
Subject: Re: [PATCH] mfd: syscon: Decouple syscon interface from syscon
devices
On Tuesday 02 September 2014 09:05:16 Lee Jones wrote:
On Mon
On Tue, 02 Sep 2014, Arnd Bergmann wrote:
On Tuesday 02 September 2014 09:05:16 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 17:04:26 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
Maybe I'm misreading the patch, but I don't
On Fri, 22 Aug 2014, Pankaj Dubey wrote:
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated driver. However in certain use
cases it is desirable to make a device used with another driver a syscon
On Monday 01 September 2014 08:49:18 Lee Jones wrote:
On Fri, 22 Aug 2014, Pankaj Dubey wrote:
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated driver. However in certain use
cases it is
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 08:49:18 Lee Jones wrote:
On Fri, 22 Aug 2014, Pankaj Dubey wrote:
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only registered directly through a
platform device that binds to a
...@arm.linux.org.uk; vikas.saj...@samsung.com; jo...@samsung.com;
naus...@samsung.com; thomas...@samsung.com; chow@samsung.com;
Tomasz Figa; broo...@kernel.org
Subject: Re: [PATCH] mfd: syscon: Decouple syscon interface from syscon
devices
On Monday 01 September 2014 08:49:18 Lee Jones wrote
On Monday 01 September 2014 12:25:49 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 08:49:18 Lee Jones wrote:
On Fri, 22 Aug 2014, Pankaj Dubey wrote:
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 12:25:49 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
On Monday 01 September 2014 08:49:18 Lee Jones wrote:
On Fri, 22 Aug 2014, Pankaj Dubey wrote:
From: Tomasz Figa t.f...@samsung.com
On Monday 01 September 2014 17:04:26 Lee Jones wrote:
On Mon, 01 Sep 2014, Arnd Bergmann wrote:
Maybe I'm misreading the patch, but I don't see how it creates a
migration path. What I want to end up with is infrastructure that
lets anybody call syscon_regmap_lookup_by_pdevname or
Figa; Pankaj Dubey
Subject: [PATCH] mfd: syscon: Decouple syscon interface from syscon
devices
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only registered directly through a
platform device
that binds to a dedicated driver. However in certain use cases
From: Tomasz Figa t.f...@samsung.com
Currently a syscon entity can be only registered directly through a
platform device that binds to a dedicated 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
13 matches
Mail list logo