missed
> > one place to fix up.
> >
> > Signed-off-by: Daniel Wagner
> > Cc: Nariman Poushin
> > Cc: Mark Brown
>
> Forgot to add:
>
> Reported-by: kbuild test robot
>
> Sorry about that.
Acked-By: Nariman Poushin
--
To unsubscribe from this li
missed
> > one place to fix up.
> >
> > Signed-off-by: Daniel Wagner <daniel.wag...@bmw-carit.de>
> > Cc: Nariman Poushin <nari...@opensource.wolfsonmicro.com>
> > Cc: Mark Brown <broo...@kernel.org>
>
> Forgot to add:
>
> Reported-by: kbuild
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
> On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
>
> > What is the best course of action here? I am more than happy to help with
> > whatever is needed but unsure of the etiquette here and also not s
Introduced by:
commit 8019ff6cfc04
("regmap: Use reg_sequence for multi_reg_write / register_patch")
Interacting with:
commit d1acd31883d7
("ASoC: wm5110: Add special DRE on/off handling for the headphone path")
Signed-off-by: Nariman Poushin
---
sound/soc/codecs/wm5110.c
Introduced by:
commit 8019ff6cfc04
("regmap: Use reg_sequence for multi_reg_write / register_patch")
Interacting with:
commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above&
On Fri, Jul 17, 2015 at 02:39:34PM +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> After merging the regmap tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings:
>
> sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
> sound/soc/codecs/wm5110.c:294:9:
Introduced by:
commit 8019ff6cfc04
(regmap: Use reg_sequence for multi_reg_write / register_patch)
Interacting with:
commit 561629755a21 (mfd: arizona: Add support for WM8998 and WM1814)
commit 81207880cef2 (mfd: wm5110: Add register patch for rev E and above)
Signed-off-by: Nariman Poushin nari
Introduced by:
commit 8019ff6cfc04
(regmap: Use reg_sequence for multi_reg_write / register_patch)
Interacting with:
commit d1acd31883d7
(ASoC: wm5110: Add special DRE on/off handling for the headphone path)
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
sound/soc/codecs
On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote:
On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote:
What is the best course of action here? I am more than happy to help with
whatever is needed but unsure of the etiquette here and also not sure
what I can do
On Fri, Jul 17, 2015 at 02:39:34PM +1000, Stephen Rothwell wrote:
Hi Mark,
After merging the regmap tree, today's linux-next build (powerpc
allyesconfig) produced these warnings:
sound/soc/codecs/wm5110.c: In function 'wm5110_hp_pre_enable':
sound/soc/codecs/wm5110.c:294:9: warning:
On Thu, Jul 16, 2015 at 01:52:54PM +0100, Mark Brown wrote:
> On Tue, Jul 14, 2015 at 03:45:51PM +0100, Nariman Poushin wrote:
>
> Please submit patches in the format covered in SubmittingPatches,
> version information goes inside the [].
>
> > Add support for writing s
before
a delay (in the same way you can coalesce all writes before a page
change is needed)
Signed-off-by: Nariman Poushin
---
drivers/base/regmap/regmap.c | 54 +++-
include/linux/regmap.h | 5 +++-
2 files changed, 52 insertions(+), 7 deletions
adding an int to all register defaults, which could
substantially increase memory usage for regmaps with large default tables.
This also updates all the clients of multi_reg_write/register_patch.
Signed-off-by: Nariman Poushin
---
drivers/base/regmap/internal.h | 2 +-
drivers/base/regmap
adding an int to all register defaults, which could
substantially increase memory usage for regmaps with large default tables.
This also updates all the clients of multi_reg_write/register_patch.
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
drivers/base/regmap/internal.h
before
a delay (in the same way you can coalesce all writes before a page
change is needed)
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
drivers/base/regmap/regmap.c | 54 +++-
include/linux/regmap.h | 5 +++-
2 files changed
On Thu, Jul 16, 2015 at 01:52:54PM +0100, Mark Brown wrote:
On Tue, Jul 14, 2015 at 03:45:51PM +0100, Nariman Poushin wrote:
Please submit patches in the format covered in SubmittingPatches,
version information goes inside the [].
Add support for writing sequences of registers / patches
substantially.
This also updates all the clients of multi_reg_write/register_patch.
Signed-off-by: Nariman Poushin
---
drivers/base/regmap/internal.h | 2 +-
drivers/base/regmap/regmap.c | 22 +++---
drivers/gpu/drm/i2c/adv7511.c | 2 +-
drivers/input/misc/drv260x.c | 6
We treat a delay in a sequence the same way we treat a page change as
they are logically similar in that you can coalesce all write before
a delay (in the same way you can coalesce all writes before a page
change is needed)
Signed-off-by: Nariman Poushin
---
drivers/base/regmap/regmap.c | 65
substantially.
This also updates all the clients of multi_reg_write/register_patch.
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
drivers/base/regmap/internal.h | 2 +-
drivers/base/regmap/regmap.c | 22 +++---
drivers/gpu/drm/i2c/adv7511.c | 2 +-
drivers
We treat a delay in a sequence the same way we treat a page change as
they are logically similar in that you can coalesce all write before
a delay (in the same way you can coalesce all writes before a page
change is needed)
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
On Fri, May 08, 2015 at 11:34:54AM +0100, Nariman Poushin wrote:
> On Fri, May 08, 2015 at 11:20:19AM +0100, Mark Brown wrote:
> > On Fri, May 08, 2015 at 10:55:37AM +0100, Nariman Poushin wrote:
> > > Signed-off-by: Nariman Poushin
> > > ---
> > >
On Fri, May 08, 2015 at 11:34:54AM +0100, Nariman Poushin wrote:
On Fri, May 08, 2015 at 11:20:19AM +0100, Mark Brown wrote:
On Fri, May 08, 2015 at 10:55:37AM +0100, Nariman Poushin wrote:
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
regcache currently
On Tue, Jun 02, 2015 at 07:15:13PM +0100, Mark Brown wrote:
> On Mon, Jun 01, 2015 at 10:20:12AM +0100, Nariman Poushin wrote:
>
> > it be accepted), should I:
> > - Squash all the updates in to this patch (I suppose the benefit
> > there is that we don't bre
On Tue, Jun 02, 2015 at 07:15:13PM +0100, Mark Brown wrote:
On Mon, Jun 01, 2015 at 10:20:12AM +0100, Nariman Poushin wrote:
it be accepted), should I:
- Squash all the updates in to this patch (I suppose the benefit
there is that we don't break the kernel build from one patch
).
Signed-off-by: Nariman Poushin
---
I am not sure how best to update all the users of this patch (should
it be accepted), should I:
- Squash all the updates in to this patch (I suppose the benefit
there is that we don't break the kernel build from one patch
).
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
I am not sure how best to update all the users of this patch (should
it be accepted), should I:
- Squash all the updates in to this patch (I suppose the benefit
there is that we don't break the kernel build
On Tue, May 26, 2015 at 04:36:54PM +0100, Richard Fitzgerald wrote:
> On Tue, May 26, 2015 at 04:21:00PM +0100, Mark Brown wrote:
> > On Tue, May 26, 2015 at 01:39:21PM +0100, Nariman Poushin wrote:
> >
> > > Change-Id:Ie9e77aa48f258b353ffa7406d02e19c28d5f2a44
My
On Tue, May 26, 2015 at 04:36:54PM +0100, Richard Fitzgerald wrote:
On Tue, May 26, 2015 at 04:21:00PM +0100, Mark Brown wrote:
On Tue, May 26, 2015 at 01:39:21PM +0100, Nariman Poushin wrote:
Change-Id:Ie9e77aa48f258b353ffa7406d02e19c28d5f2a44
My bad, should have removed
. This also maintains atomicity for the
sequence, which avoids callers needing this type of behaviour from
having to implement their own locking schemes to achieve this when
also requiring delays within a write sequence
Change-Id:Ie9e77aa48f258b353ffa7406d02e19c28d5f2a44
Signed-off-by: Nariman Poushin
. This also maintains atomicity for the
sequence, which avoids callers needing this type of behaviour from
having to implement their own locking schemes to achieve this when
also requiring delays within a write sequence
Change-Id:Ie9e77aa48f258b353ffa7406d02e19c28d5f2a44
Signed-off-by: Nariman Poushin nari
On Fri, May 08, 2015 at 11:20:19AM +0100, Mark Brown wrote:
> On Fri, May 08, 2015 at 10:55:37AM +0100, Nariman Poushin wrote:
> > Signed-off-by: Nariman Poushin
> > ---
> > regcache currently causes a BUG_ON if cache_sync/sync_region is
> > called on a map wi
Signed-off-by: Nariman Poushin
---
regcache currently causes a BUG_ON if cache_sync/sync_region is
called on a map with cache_type REGCACHE_NONE. This is not
consistent with the behaviour of regcache_read/write which
currently just return -ENOSYS and only throws a BUG_ON if
the cache_type
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
regcache currently causes a BUG_ON if cache_sync/sync_region is
called on a map with cache_type REGCACHE_NONE. This is not
consistent with the behaviour of regcache_read/write which
currently just return -ENOSYS and only
On Fri, May 08, 2015 at 11:20:19AM +0100, Mark Brown wrote:
On Fri, May 08, 2015 at 10:55:37AM +0100, Nariman Poushin wrote:
Signed-off-by: Nariman Poushin nari...@opensource.wolfsonmicro.com
---
regcache currently causes a BUG_ON if cache_sync/sync_region is
called on a map
34 matches
Mail list logo
