From: Bjorn Helgaas <helgaas@kernel.org>
To: rui_feng@realsil.com.cn
Cc: lee.jones@linaro.org, linux-kernel@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v6] mfd: Add support for RTS5250S power saving
Date: Thu, 14 Dec 2017 16:25:23 -0600 [thread overview]
Message-ID: <20171214222522.GL30595@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <1504772799-15173-1-git-send-email-rui_feng@realsil.com.cn>
[+cc Hans, Dave, linux-pci]
On Thu, Sep 07, 2017 at 04:26:39PM +0800, rui_feng@realsil.com.cn wrote:
> From: Rui Feng <rui_feng@realsil.com.cn>
I wish this had been posted to linux-pci before being merged.
I'm concerned because some of this appears to overlap and
conflict with PCI core management of ASPM.
I assume these devices advertise ASPM support in their Link
Capabilites registers, right? If so, why isn't the existing
PCI core ASPM support sufficient?
> Enable power saving for RTS5250S as following steps:
> 1.Set 0xFE58 to enable clock power management.
Is this clock power management something specific to RTS5250S, or is
it standard PCIe architected stuff?
> 2.Check cfg space whether support L1SS or not.
This sounds like standard PCIe ASPM L1 Substates, right?
> 3.If support L1SS, set 0xFF03 to free clkreq.
> 4.When entering idle status, enable aspm
> and set parameters for L1SS and LTR.
> 5.Wnen entering run status, disable aspm
> and set parameters for L1SS and LTR.
In general, drivers should not configure ASPM, L1SS, and LTR
themselves; the PCI core should do that.
If a driver needs to tweak ASPM at run-time, it should use interfaces
exported by the PCI core to do so.
> If entering L1SS mode successfully,
> electric current will be below 2mA.
> Signed-off-by: Rui Feng <rui_feng@realsil.com.cn>
> ...
> +static void rts5249_init_from_cfg(struct rtsx_pcr *pcr)
> +{
> + struct rtsx_cr_option *option = &(pcr->option);
> + u32 lval;
> +
> + if (CHK_PCI_PID(pcr, PID_524A))
> + rtsx_pci_read_config_dword(pcr,
> + PCR_ASPM_SETTING_REG1, &lval);
> + else
> + rtsx_pci_read_config_dword(pcr,
> + PCR_ASPM_SETTING_REG2, &lval);
This looks like you're reading the ASPM L1 Substates capability, i.e.,
PCI_L1SS_CAP, using hard-coded offsets based on the Device ID. You
should be using pci_find_ext_capability() to locate it.
> + if (lval & ASPM_L1_1_EN_MASK)
> + rtsx_set_dev_flag(pcr, ASPM_L1_1_EN);
> +
> + if (lval & ASPM_L1_2_EN_MASK)
> + rtsx_set_dev_flag(pcr, ASPM_L1_2_EN);
> +
> + if (lval & PM_L1_1_EN_MASK)
> + rtsx_set_dev_flag(pcr, PM_L1_1_EN);
> +
> + if (lval & PM_L1_2_EN_MASK)
> + rtsx_set_dev_flag(pcr, PM_L1_2_EN);
You're adding these:
#define ASPM_L1_1_EN_MASK BIT(3)
#define ASPM_L1_2_EN_MASK BIT(2)
#define PM_L1_1_EN_MASK BIT(1)
#define PM_L1_2_EN_MASK BIT(0)
The PCI core already defines these and you should use them instead:
#define PCI_L1SS_CAP_PCIPM_L1_2 0x00000001 /* PCI-PM L1.2 Supported */
#define PCI_L1SS_CAP_PCIPM_L1_1 0x00000002 /* PCI-PM L1.1 Supported */
#define PCI_L1SS_CAP_ASPM_L1_2 0x00000004 /* ASPM L1.2 Supported */
#define PCI_L1SS_CAP_ASPM_L1_1 0x00000008 /* ASPM L1.1 Supported */
> + if (option->ltr_en) {
> + u16 val;
> +
> + pcie_capability_read_word(pcr->pci, PCI_EXP_DEVCTL2, &val);
> + if (val & PCI_EXP_DEVCTL2_LTR_EN) {
> + option->ltr_enabled = true;
> + option->ltr_active = true;
ltr_active is never actually used.
> + rtsx_set_ltr_latency(pcr, option->ltr_active_latency);
> + } else {
> + option->ltr_enabled = false;
> + }
> + }
> +}
> ...
> +static void rts5249_set_aspm(struct rtsx_pcr *pcr, bool enable)
> +{
> + struct rtsx_cr_option *option = &pcr->option;
> + u8 val = 0;
> +
> + if (pcr->aspm_enabled == enable)
> + return;
> +
> + if (option->dev_aspm_mode == DEV_ASPM_DYNAMIC) {
> + if (enable)
> + val = pcr->aspm_en;
> + rtsx_pci_update_cfg_byte(pcr,
> + pcr->pcie_cap + PCI_EXP_LNKCTL,
> + ASPM_MASK_NEG, val);
This stomps on whatever ASPM configuration the PCI core did.
> + } else if (option->dev_aspm_mode == DEV_ASPM_BACKDOOR) {
DEV_ASPM_BACKDOOR is never set, so this looks like dead code.
> + u8 mask = FORCE_ASPM_VAL_MASK | FORCE_ASPM_CTL0;
> + if (!enable)
> + val = FORCE_ASPM_CTL0;
> + rtsx_pci_write_register(pcr, ASPM_FORCE_CTL, mask, val);
> + }
> +
> + pcr->aspm_enabled = enable;
> +}
next prev parent reply other threads:[~2017-12-14 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 8:26 rui_feng
2017-09-07 10:57 ` Lee Jones
2017-12-14 22:25 ` Bjorn Helgaas [this message]
2017-12-15 7:41 ` Hans de Goede
[not found] ` <2A308283684ECD4B896628E09AF5361E01A8150B@RS-MBS01.realsil.com.cn>
2017-12-15 15:15 ` 答复: " Bjorn Helgaas
2017-12-19 8:15 ` 答复: " 冯锐
2017-12-27 23:37 ` Bjorn Helgaas
2018-01-17 21:01 ` Bjorn Helgaas
2018-01-19 7:38 ` 答复: " 冯锐
2018-01-30 19:18 ` Bjorn Helgaas
2018-02-01 8:45 ` 答复: " 冯锐
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=20171214222522.GL30595@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=dave.jiang@intel.com \
--cc=hdegoede@redhat.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rui_feng@realsil.com.cn \
/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
all inboxes | Powered by JetHome®