Re: [PATCH V2 02/12] pinctrl: tegra: add suspend and resume support

[Dmitry Osipenko]

29.05.2019 23:11, Sowjanya Komatineni ÐÐÑÐÑ:
> 
> On 5/29/19 12:32 PM, Dmitry Osipenko wrote:
>> 29.05.2019 21:14, Sowjanya Komatineni ÐÐÑÐÑ:
>>> On 5/29/19 8:29 AM, Dmitry Osipenko wrote:
>>>> 29.05.2019 2:08, Sowjanya Komatineni ÐÐÑÐÑ:
>>>>> This patch adds suspend and resume support for Tegra pinctrl driver
>>>>> and registers them to syscore so the pinmux settings are restored
>>>>> before the devices resume.
>>>>>
>>>>> Signed-off-by: Sowjanya Komatineni <skomatineni@xxxxxxxxxx>
>>>>> ---
>>>>> ÂÂ drivers/pinctrl/tegra/pinctrl-tegra.cÂÂÂ | 68
>>>>> +++++++++++++++++++++++++++++++-
>>>>> ÂÂ drivers/pinctrl/tegra/pinctrl-tegra.hÂÂÂ |Â 3 ++
>>>>> ÂÂ drivers/pinctrl/tegra/pinctrl-tegra114.c |Â 1 +
>>>>> ÂÂ drivers/pinctrl/tegra/pinctrl-tegra124.c |Â 1 +
>>>>>  drivers/pinctrl/tegra/pinctrl-tegra20.c | 1 +
>>>>> ÂÂ drivers/pinctrl/tegra/pinctrl-tegra210.c |Â 1 +
>>>>>  drivers/pinctrl/tegra/pinctrl-tegra30.c | 1 +
>>>>> ÂÂ 7 files changed, 75 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/drivers/pinctrl/tegra/pinctrl-tegra.c
>>>>> b/drivers/pinctrl/tegra/pinctrl-tegra.c
>>>>> index a5008c066bac..bdc47e62c457 100644
>>>>> --- a/drivers/pinctrl/tegra/pinctrl-tegra.c
>>>>> +++ b/drivers/pinctrl/tegra/pinctrl-tegra.c
>>>>> @@ -28,11 +28,18 @@
>>>>> ÂÂ #include <linux/pinctrl/pinmux.h>
>>>>> ÂÂ #include <linux/pinctrl/pinconf.h>
>>>>> ÂÂ #include <linux/slab.h>
>>>>> +#include <linux/syscore_ops.h>
>>>>> ÂÂ Â #include "../core.h"
>>>>> ÂÂ #include "../pinctrl-utils.h"
>>>>> ÂÂ #include "pinctrl-tegra.h"
>>>>> ÂÂ +#define EMMC2_PAD_CFGPADCTRL_0ÂÂÂÂÂÂÂÂÂÂÂ 0x1c8
>>>>> +#define EMMC4_PAD_CFGPADCTRL_0ÂÂÂÂÂÂÂÂÂÂÂ 0x1e0
>>>>> +#define EMMC_DPD_PARKINGÂÂÂÂÂÂÂÂÂÂÂ (0x1fff << 14)
>>>>> +
>>>>> +static struct tegra_pmx *pmx;
>>>>> +
>>>>> ÂÂ static inline u32 pmx_readl(struct tegra_pmx *pmx, u32 bank, u32
>>>>> reg)
>>>>> ÂÂ {
>>>>> ÂÂÂÂÂÂ return readl(pmx->regs[bank] + reg);
>>>>> @@ -629,6 +636,50 @@ static void
>>>>> tegra_pinctrl_clear_parked_bits(struct tegra_pmx *pmx)
>>>>> ÂÂÂÂÂÂ }
>>>>> ÂÂ }
>>>>> ÂÂ +static int __maybe_unused tegra_pinctrl_suspend(void)
>>>>> +{
>>>>> +ÂÂÂ u32 *backup_regs = pmx->backup_regs;
>>>>> +ÂÂÂ u32 *regs;
>>>>> +ÂÂÂ int i, j;
>>>>> +
>>>>> +ÂÂÂ for (i = 0; i < pmx->nbanks; i++) {
>>>>> +ÂÂÂÂÂÂÂ regs = pmx->regs[i];
>>>>> +ÂÂÂÂÂÂÂ for (j = 0; j < pmx->reg_bank_size[i] / 4; j++)
>>>>> +ÂÂÂÂÂÂÂÂÂÂÂ *backup_regs++ = readl(regs++);
>>>>> +ÂÂÂ }
>>>>> +
>>>>> +ÂÂÂ return pinctrl_force_sleep(pmx->pctl);
>>>>> +}
>>>>> +
>>>>> +static void __maybe_unused tegra_pinctrl_resume(void)
>>>>> +{
>>>>> +ÂÂÂ u32 *backup_regs = pmx->backup_regs;
>>>>> +ÂÂÂ u32 *regs;
>>>>> +ÂÂÂ u32 val;
>>>>> +ÂÂÂ int i, j;
>>>>> +
>>>>> +ÂÂÂ for (i = 0; i < pmx->nbanks; i++) {
>>>>> +ÂÂÂÂÂÂÂ regs = pmx->regs[i];
>>>>> +ÂÂÂÂÂÂÂ for (j = 0; j < pmx->reg_bank_size[i] / 4; j++)
>>>>> +ÂÂÂÂÂÂÂÂÂÂÂ writel(*backup_regs++, regs++);
>>>>> +ÂÂÂ }
>>>>> +
>>>>> +ÂÂÂ if (pmx->soc->has_park_padcfg) {
>>>>> +ÂÂÂÂÂÂÂ val = pmx_readl(pmx, 0, EMMC2_PAD_CFGPADCTRL_0);
>>>>> +ÂÂÂÂÂÂÂ val &= ~EMMC_DPD_PARKING;
>>>>> +ÂÂÂÂÂÂÂ pmx_writel(pmx, val, 0, EMMC2_PAD_CFGPADCTRL_0);
>>>>> +
>>>>> +ÂÂÂÂÂÂÂ val = pmx_readl(pmx, 0, EMMC4_PAD_CFGPADCTRL_0);
>>>>> +ÂÂÂÂÂÂÂ val &= ~EMMC_DPD_PARKING;
>>>>> +ÂÂÂÂÂÂÂ pmx_writel(pmx, val, 0, EMMC4_PAD_CFGPADCTRL_0);
>>>>> +ÂÂÂ }
>>>>> +}
>>>>>
>>>> But the CFGPADCTRL registers are already programmed by restoring the
>>>> backup_regs and hence the relevant EMMC's are already unparked. Hence
>>>> why do you need to force-unpark both of the EMMC's? What if EMMC is
>>>> unpopulated on a board, why do you need to unpark it then?
>>> PARK bit for EMMC2/EMMC4 (EMMC2_PAD_CFGPADCTRL and EMMC4_PAD_CFGPADCTRL)
>>> are not part of pinmux.
>>>
>>> They are part of CFGPADCTRL register so pinctrl driver pingroup doesn't
>>> include these registers.
>> I'm looking at the tegra210_groups and it clearly has these both
>> registers as a part of pinctrl setup because the rest of the bits
>> configure drive of the pads.
>>
>> ÂFrom pinctrl-tegra210.c:
>>
>> #define DRV_PINGROUP_REG_AÂÂÂÂÂÂÂ 0x8d4ÂÂÂ /* bank 0 */
>>
>> DRV_PINGROUP(sdmmc2, 0xa9c, 2, 6, 8, 6, 28, 2, 30, 2),
>> DRV_PINGROUP(sdmmc4, 0xab4, 2, 6, 8, 6, 28, 2, 30, 2),
>>
>> ...
>>
>> 0xa9c - 0x8d4 = 0x1c8
>> 0xab4 - 0x8d4 = 0x1e0
>>
>> Hence the PARK bits are already getting unset by restoring the
>> backup_regs because the CFGPADCTRL registers are a part of the "bank 0"
>> registers.
>>
>> Am I still missing something?
> 
> DRV_PINGROUP parked_bit is -1 and will not be programmed so store and
> restore will not take care of it.
> 
> Also EMMC PADCFG is the only padcfg register which has parked bit and
> for other IO pads its part of pinmux

You're storing raw values of all of the PINCTRL registers and then
restoring the raw values (if I'm not misreading that part on the patch),
it's absolutely meaningless that DRV_PINGROUP doesn't define the PARK bits.

In a result, the backup_regs array contains raw CFGPADCTRL value with
the PARK bits being unset on store, that value is written out on the
restore as-is and hence the PARK bits are getting unset as well.

And why DRV_PINGROUP misses PARK bits for the EMMC's? Looks like a
driver's drawback that need to be addressed.