Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-20 Thread Charles Keepax
On Tue, Oct 20, 2015 at 11:47:11AM +0900, Jiada Wang wrote: > By doing software reset of wm8962 in pm_resume, all registers which > have already been set will be reset to default value without regmap > interface be involved, thus driver need to mark cache_dirty flag, > to let regcache can be

Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-20 Thread Charles Keepax
On Tue, Oct 20, 2015 at 11:47:11AM +0900, Jiada Wang wrote: > By doing software reset of wm8962 in pm_resume, all registers which > have already been set will be reset to default value without regmap > interface be involved, thus driver need to mark cache_dirty flag, > to let regcache can be

[PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-19 Thread Jiada Wang
By doing software reset of wm8962 in pm_resume, all registers which have already been set will be reset to default value without regmap interface be involved, thus driver need to mark cache_dirty flag, to let regcache can be updated by regcache_sync(). Signed-off-by: Jiada Wang ---

[PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-19 Thread Jiada Wang
By doing software reset of wm8962 in pm_resume, all registers which have already been set will be reset to default value without regmap interface be involved, thus driver need to mark cache_dirty flag, to let regcache can be updated by regcache_sync(). Signed-off-by: Jiada Wang

Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-07 Thread Jiada Wang
Hi On 10/06/2015 07:59 PM, Mark Brown wrote: On Tue, Oct 06, 2015 at 04:06:54PM +0900, Jiada Wang wrote: + /* All registers have been reset to default value without calling +* to regmap interface, even if reset fails, some registers +* maybe in intermediate status, so we

Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-07 Thread Jiada Wang
Hi On 10/06/2015 07:59 PM, Mark Brown wrote: On Tue, Oct 06, 2015 at 04:06:54PM +0900, Jiada Wang wrote: + /* All registers have been reset to default value without calling +* to regmap interface, even if reset fails, some registers +* maybe in intermediate status, so we

Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-06 Thread Mark Brown
On Tue, Oct 06, 2015 at 04:06:54PM +0900, Jiada Wang wrote: > + /* All registers have been reset to default value without calling > + * to regmap interface, even if reset fails, some registers > + * maybe in intermediate status, so we need to mark regmap > + * cache_dirty flag.

[PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-06 Thread Jiada Wang
By doing software reset of wm8962 in pm_resume, all registers which have already been set will be reset to default value without regmap interface be involved, thus driver need to mark cache_dirty flag, to let regcache can be updated by regcache_sync(). Signed-off-by: Jiada Wang ---

[PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-06 Thread Jiada Wang
By doing software reset of wm8962 in pm_resume, all registers which have already been set will be reset to default value without regmap interface be involved, thus driver need to mark cache_dirty flag, to let regcache can be updated by regcache_sync(). Signed-off-by: Jiada Wang

Re: [PATCH 1/2] ASoC: WM8962: mark cache_dirty flag after software reset in pm_resume

2015-10-06 Thread Mark Brown
On Tue, Oct 06, 2015 at 04:06:54PM +0900, Jiada Wang wrote: > + /* All registers have been reset to default value without calling > + * to regmap interface, even if reset fails, some registers > + * maybe in intermediate status, so we need to mark regmap > + * cache_dirty flag.