On Sun, Feb 23, 2014 at 04:11:59PM +, Charles Keepax wrote:
> On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
> > This is just regmap_multi_reg_write() I think? That already exists, the
> > theory was that we're going to get an optimised version of that for some
> > hardware
On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
> On Fri, Feb 21, 2014 at 07:37:11PM +, Charles Keepax wrote:
> > This patch provides a new regmap API call that allows a patch to be
> > applied but not registered with the regmap core. Common code between
> > this and the existing
On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
On Fri, Feb 21, 2014 at 07:37:11PM +, Charles Keepax wrote:
This patch provides a new regmap API call that allows a patch to be
applied but not registered with the regmap core. Common code between
this and the existing
On Sun, Feb 23, 2014 at 04:11:59PM +, Charles Keepax wrote:
On Sat, Feb 22, 2014 at 11:10:48AM +0900, Mark Brown wrote:
This is just regmap_multi_reg_write() I think? That already exists, the
theory was that we're going to get an optimised version of that for some
hardware which can
On Fri, Feb 21, 2014 at 07:37:11PM +, Charles Keepax wrote:
> This patch provides a new regmap API call that allows a patch to be
> applied but not registered with the regmap core. Common code between
> this and the existing regmap_register_patch function is factored out to
> reduce
This patch provides a new regmap API call that allows a patch to be
applied but not registered with the regmap core. Common code between
this and the existing regmap_register_patch function is factored out to
reduce duplication.
This can be helpful when devices have more complex boot proceedures
On Fri, Feb 21, 2014 at 07:37:11PM +, Charles Keepax wrote:
This patch provides a new regmap API call that allows a patch to be
applied but not registered with the regmap core. Common code between
this and the existing regmap_register_patch function is factored out to
reduce duplication.
This patch provides a new regmap API call that allows a patch to be
applied but not registered with the regmap core. Common code between
this and the existing regmap_register_patch function is factored out to
reduce duplication.
This can be helpful when devices have more complex boot proceedures
8 matches
Mail list logo