public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dongas86@gmail.com (Dong Aisheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/8] soc: imx: gpc: fix the wrong using of regmap cache
Date: Thu, 23 Mar 2017 02:53:22 +0800	[thread overview]
Message-ID: <20170322185322.GB16264@b29396-OptiPlex-7040> (raw)
In-Reply-To: <1490002701.2895.13.camel@pengutronix.de>

Hi Lucas,

Thanks for the review.

On Mon, Mar 20, 2017 at 10:38:21AM +0100, Lucas Stach wrote:
> Am Montag, den 20.03.2017, 14:15 +0800 schrieb Dong Aisheng:
> > Without providing the proper reg_defaults, the regmap registers first
> > read out may be always 0 if enabling cache, which results in the
> > following issue we met.
> > e.g. During driver probe in imx6_pm_domain_power_on():
> > regmap_read(pd->regmap, pd->reg_offs + GPC_PGC_PUPSCR_OFFS, &val);
> > The PGC_PUPSCR register val is always 0 but it's actually 0xf01 in HW.
> > 
> > Since GPC registers are tightly related to CPU bring up and may be
> > changed in bootloader, we don't want to provide defaults.
> > And the cache really does not save too much for GPC module.
> > 
> > Therefore, simply disable cache to fix the issue and make life easy.
> 
> While I agree that not using the cache may be the right thing to do
> here, bypassing the cache by not providing the volatile function is only
> half the fix.
> 

Removing volatile function actually is only due to it becomes meaningless
after disable cache, not used to bypass or fix the cache issue.

> Please also set the cache type to REGCACHE_NONE, to make it clear that
> the cache isn't used.
> 

I believe all guys normally may know the regmap cache is disabled by default
if without specifying cache_type, this way is also commonly used in kernel.
So i just simply remove it.
Another bonus is it fully hides the cache bits from drive user.
No one needs to know it if not use.

Anyway, if you insist on it, i could explicitly claim the cache type to
REGCACHE_NONE in V2.

Thanks

Regards
Dong Aisheng

> Regards,
> Lucas
> 
> > Cc: Lucas Stach <l.stach@pengutronix.de>
> > Cc: Shawn Guo <shawnguo@kernel.org>
> > Fixes: 721cabf6c660 ("soc: imx: move PGC handling to a new GPC driver")
> > Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com>
> > ---
> >  drivers/soc/imx/gpc.c | 10 ----------
> >  1 file changed, 10 deletions(-)
> > 
> > diff --git a/drivers/soc/imx/gpc.c b/drivers/soc/imx/gpc.c
> > index c9bfdfd..7e6a672 100644
> > --- a/drivers/soc/imx/gpc.c
> > +++ b/drivers/soc/imx/gpc.c
> > @@ -289,22 +289,12 @@ static bool imx_gpc_readable_reg(struct device *dev, unsigned int reg)
> >  	return (reg % 4 == 0) && (reg <= 0x2ac);
> >  }
> >  
> > -static bool imx_gpc_volatile_reg(struct device *dev, unsigned int reg)
> > -{
> > -	if (reg == GPC_CNTR)
> > -		return true;
> > -
> > -	return false;
> > -}
> > -
> >  static const struct regmap_config imx_gpc_regmap_config = {
> > -	.cache_type = REGCACHE_FLAT,
> >  	.reg_bits = 32,
> >  	.val_bits = 32,
> >  	.reg_stride = 4,
> >  
> >  	.readable_reg = imx_gpc_readable_reg,
> > -	.volatile_reg = imx_gpc_volatile_reg,
> >  
> >  	.max_register = 0x2ac,
> >  };
> 
> 

  reply	other threads:[~2017-03-22 18:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  6:15 [PATCH 0/8] soc: imx: gpc: fixes and clean up Dong Aisheng
2017-03-20  6:15 ` [PATCH 1/8] soc: imx: gpc: fix gpc clk get error handling Dong Aisheng
2017-03-20  8:05   ` Shawn Guo
2017-03-22 18:33     ` Dong Aisheng
2017-03-22  6:38       ` Shawn Guo
2017-03-20  6:15 ` [PATCH 2/8] soc: imx: gpc: fix the wrong using of regmap cache Dong Aisheng
2017-03-20  9:38   ` Lucas Stach
2017-03-22 18:53     ` Dong Aisheng [this message]
2017-03-22  8:43       ` Lucas Stach
2017-03-20  6:15 ` [PATCH 3/8] soc: imx: gpc: fix domain_index sanity check issue Dong Aisheng
2017-03-20  9:40   ` Lucas Stach
2017-03-20  6:15 ` [PATCH 4/8] soc: imx: gpc: fix imx6sl gpc power domain regression Dong Aisheng
2017-03-20  9:26   ` Lucas Stach
2017-03-22 19:23     ` Dong Aisheng
2017-03-22  8:46       ` Lucas Stach
2017-03-23  0:47         ` Dong Aisheng
2017-03-20  6:15 ` [PATCH 5/8] soc: imx: gpc: fix comment when power up domain Dong Aisheng
2017-03-20  9:41   ` Lucas Stach
2017-03-20  6:15 ` [PATCH 6/8] soc: imx: gpc: keep PGC_X_CTRL name align with reference manual Dong Aisheng
2017-03-20  9:42   ` Lucas Stach
2017-03-20  6:15 ` [PATCH 7/8] dt-bindings: imx-gpc: correct the DOMAIN_INDEX using Dong Aisheng
2017-03-20  9:43   ` Lucas Stach
2017-03-20  6:15 ` [PATCH 8/8] soc: imx: gpc: remove unnecessary readable_reg callback Dong Aisheng
2017-03-20  9:43   ` Lucas Stach
2017-03-22 19:25     ` Dong Aisheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170322185322.GB16264@b29396-OptiPlex-7040 \
    --to=dongas86@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox