public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Lin <shawn.lin@rock-chips.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: shawn.lin@rock-chips.com, Rob Herring <robh+dt@kernel.org>,
	"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	Bart Van Assche <bvanassche@acm.org>,
	YiFeng Zhao <zyf@rock-chips.com>, Liang Chen <cl@rock-chips.com>,
	linux-scsi@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 5/5] scsi: ufs: rockchip: initial support for UFS
Date: Thu, 10 Oct 2024 09:21:08 +0800	[thread overview]
Message-ID: <3969bae0-eeb8-447a-86a5-dfdac0b136cd@rock-chips.com> (raw)
In-Reply-To: <CAPDyKForpLcmkqruuTfD6kkJhp_4CKFABWRxFVYNskGL1tjO=w@mail.gmail.com>

Hi Ulf

在 2024/10/9 21:15, Ulf Hansson 写道:
> [...]
> 
>> +
>> +static int ufs_rockchip_runtime_suspend(struct device *dev)
>> +{
>> +       struct ufs_hba *hba = dev_get_drvdata(dev);
>> +       struct ufs_rockchip_host *host = ufshcd_get_variant(hba);
>> +       struct generic_pm_domain *genpd = pd_to_genpd(dev->pm_domain);
> 
> pd_to_genpd() isn't safe to use like this. It's solely to be used by
> genpd provider drivers.
> 
>> +
>> +       clk_disable_unprepare(host->ref_out_clk);
>> +
>> +       /*
>> +        * Shouldn't power down if rpm_lvl is less than level 5.
> 
> Can you elaborate on why we must not power-off the power-domain when
> level is less than 5?
> 

Because ufshcd driver assume the controller is active and the link is on
if level is less than 5. So the default resume policy will not try to
recover the registers until the first error happened. Otherwise if the
level is >=5, it assumes the controller is off and the link is down,
then it will restore the registers and link.

And the level is changeable via sysfs.

> What happens if we power-off anyway when the level is less than 5?
> 
>> +        * This flag will be passed down to platform power-domain driver
>> +        * which has the final decision.
>> +        */
>> +       if (hba->rpm_lvl < UFS_PM_LVL_5)
>> +               genpd->flags |= GENPD_FLAG_RPM_ALWAYS_ON;
>> +       else
>> +               genpd->flags &= ~GENPD_FLAG_RPM_ALWAYS_ON;
> 
> The genpd->flags is not supposed to be changed like this - and
> especially not from a genpd consumer driver.
> 
> I am trying to understand a bit more of the use case here. Let's see
> if that helps me to potentially suggest an alternative approach.
> 

I was not familiar with the genpd part, so I haven't come up with 
another solution. It would be great if you can guide me to the right
way.

>> +
>> +       return ufshcd_runtime_suspend(dev);
>> +}
>> +
>> +static int ufs_rockchip_runtime_resume(struct device *dev)
>> +{
>> +       struct ufs_hba *hba = dev_get_drvdata(dev);
>> +       struct ufs_rockchip_host *host = ufshcd_get_variant(hba);
>> +       int err;
>> +
>> +       err = clk_prepare_enable(host->ref_out_clk);
>> +       if (err) {
>> +               dev_err(hba->dev, "failed to enable ref out clock %d\n", err);
>> +               return err;
>> +       }
>> +
>> +       reset_control_assert(host->rst);
>> +       usleep_range(1, 2);
>> +       reset_control_deassert(host->rst);
>> +
>> +       return ufshcd_runtime_resume(dev);
>> +}
>> +
>> +static int ufs_rockchip_system_suspend(struct device *dev)
>> +{
>> +       struct ufs_hba *hba = dev_get_drvdata(dev);
>> +       struct ufs_rockchip_host *host = ufshcd_get_variant(hba);
>> +
>> +       /* Pass down desired spm_lvl to Firmware */
>> +       arm_smccc_smc(ROCKCHIP_SIP_SUSPEND_MODE, ROCKCHIP_SLEEP_PD_CONFIG,
>> +                       host->pd_id, hba->spm_lvl < 5 ? 1 : 0, 0, 0, 0, 0, NULL);
> 
> Can you please elaborate on what goes on here? Is this turning off the
> power-domain that the dev is attached to - or what is actually
> happening?
> 

This smc call is trying to ask firmware not to turn off the power-domian
that the UFS is attached to and also not to turn off the power of UFS
conntroller.

Per your comment at patch 4, should I use GENPD_FLAG_ALWAYS_ON +
arm_smccc_smc here in system suspend?

>> +
>> +       return ufshcd_system_suspend(dev);
>> +}
>> +
>> +static const struct dev_pm_ops ufs_rockchip_pm_ops = {
>> +       SET_SYSTEM_SLEEP_PM_OPS(ufs_rockchip_system_suspend, ufshcd_system_resume)
>> +       SET_RUNTIME_PM_OPS(ufs_rockchip_runtime_suspend, ufs_rockchip_runtime_resume, NULL)
>> +       .prepare         = ufshcd_suspend_prepare,
>> +       .complete        = ufshcd_resume_complete,
>> +};
>> +
>> +static struct platform_driver ufs_rockchip_pltform = {
>> +       .probe = ufs_rockchip_probe,
>> +       .remove = ufs_rockchip_remove,
>> +       .driver = {
>> +               .name = "ufshcd-rockchip",
>> +               .pm = &ufs_rockchip_pm_ops,
>> +               .of_match_table = ufs_rockchip_of_match,
>> +       },
>> +};
>> +module_platform_driver(ufs_rockchip_pltform);
>> +
> 
> [...]
> 
> Kind regards
> Uffe

  reply	other threads:[~2024-10-10  4:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08  6:15 [PATCH v3 0/5] Initial support for RK3576 UFS controller Shawn Lin
2024-10-08  6:15 ` [PATCH v3 1/5] scsi: ufs: core: Add UFSHCI_QUIRK_DME_RESET_ENABLE_AFTER_HCE Shawn Lin
2024-10-08 18:08   ` Bart Van Assche
2024-10-08  6:15 ` [PATCH v3 2/5] dt-bindings: ufs: Document Rockchip UFS host controller Shawn Lin
2024-10-08 13:32   ` Krzysztof Kozlowski
2024-10-08  6:15 ` [PATCH v3 3/5] soc: rockchip: add header for suspend mode SIP interface Shawn Lin
2024-10-08  6:15 ` [PATCH v3 4/5] soc: rockchip: power-domain: Add GENPD_FLAG_RPM_ALWAYS_ON support Shawn Lin
2024-10-09 13:23   ` Ulf Hansson
2024-10-08  6:15 ` [PATCH v3 5/5] scsi: ufs: rockchip: initial support for UFS Shawn Lin
2024-10-09 13:15   ` Ulf Hansson
2024-10-10  1:21     ` Shawn Lin [this message]
2024-10-18  9:07       ` Ulf Hansson
2024-10-18  9:20         ` Shawn Lin
2024-10-18 10:03           ` Ulf Hansson
2024-10-21  0:43             ` Shawn Lin
2024-11-01 15:12               ` Ulf Hansson
2024-11-04  6:21                 ` Shawn Lin
2024-11-03 12:02           ` Manivannan Sadhasivam
     [not found]             ` <6f3f2d17-4ca2-44ad-b8df-72986d4b3174@rock-chips.com>
2024-11-04  9:51               ` Ulf Hansson
2024-11-04 15:08                 ` Manivannan Sadhasivam
2024-10-09 20:00   ` kernel test robot
2024-11-03 13:09   ` Christophe JAILLET

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=3969bae0-eeb8-447a-86a5-dfdac0b136cd@rock-chips.com \
    --to=shawn.lin@rock-chips.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bvanassche@acm.org \
    --cc=cl@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=martin.petersen@oracle.com \
    --cc=robh+dt@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=zyf@rock-chips.com \
    /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