From: Lukas Wunner <lukas@wunner.de>
To: Bryan O'Donoghue <pure.logic@nexus-software.ie>
Cc: Ingo Molnar <mingo@kernel.org>,
x86@kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/1] x86/platform/intel-mid: Retrofit pci_platform_pm_ops ->get_state hook
Date: Sun, 23 Oct 2016 16:57:57 +0200 [thread overview]
Message-ID: <20161023145757.GA4909@wunner.de> (raw)
In-Reply-To: <1477226275.2932.54.camel@nexus-software.ie>
On Sun, Oct 23, 2016 at 01:37:55PM +0100, Bryan O'Donoghue wrote:
> On Sun, 2016-10-23 at 13:55 +0200, Lukas Wunner wrote:
> > Commit cc7cc02bada8 ("PCI: Query platform firmware for device power
> > state") augmented struct pci_platform_pm_ops with a ->get_state hook
> > and
> > implemented it for acpi_pci_platform_pm, the only pci_platform_pm_ops
> > existing till v4.7.
> >
> > However v4.8 introduced another pci_platform_pm_ops for Intel Mobile
> > Internet Devices with commit 5823d0893ec2 ("x86/platform/intel-mid:
> > Add
> > Power Management Unit driver"). It is missing the ->get_state hook,
> > which is fatal since pci_set_platform_pm() enforces its
> > presence. Andy
> > Shevchenko reports that without the present commit, such a device
> > "crashes without even a character printed out on serial console and
> > reboots (since watchdog)".
> >
> > Retrofit mid_pci_platform_pm with the missing callback to fix the
> > breakage.
> >
> > Fixes: cc7cc02bada8 ("PCI: Query platform firmware for device power
> > state")
> > Cc: x86@kernel.org
> > Signed-off-by: Lukas Wunner <lukas@wunner.de>
> > Acked-and-tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.c
> > om>
> > Acked-by: Bjorn Helgaas <bhelgaas@google.com>
> > ---
> > Changes v1 -> v2:
> > - Cast return value of intel_mid_pci_get_power_state() to
> > (__force pci_power_t) to avoid "sparse -D__CHECK_ENDIAN__" warning.
> > - Add ack by Andy Shevchenko.
> >
> > Changes v2 -> v3:
> > - Amend commit message to explain the user-visible failure mode as
> > reported by Andy.
> > - Add ack by Bjorn Helgaas and Fixes tag.
> >
> > arch/x86/include/asm/intel-mid.h | 1 +
> > arch/x86/platform/intel-mid/pwr.c | 19 +++++++++++++++++++
> > drivers/pci/pci-mid.c | 6 ++++++
> > 3 files changed, 26 insertions(+)
> >
> > diff --git a/arch/x86/include/asm/intel-mid.h
> > b/arch/x86/include/asm/intel-mid.h
> > index 5b6753d..49da9f4 100644
> > --- a/arch/x86/include/asm/intel-mid.h
> > +++ b/arch/x86/include/asm/intel-mid.h
> > @@ -17,6 +17,7 @@
> >
> > extern int intel_mid_pci_init(void);
> > extern int intel_mid_pci_set_power_state(struct pci_dev *pdev,
> > pci_power_t state);
> > +extern pci_power_t intel_mid_pci_get_power_state(struct pci_dev
> > *pdev);
> >
> > extern void intel_mid_pwr_power_off(void);
> >
> > diff --git a/arch/x86/platform/intel-mid/pwr.c
> > b/arch/x86/platform/intel-mid/pwr.c
> > index 5d3b45a..67375dd 100644
> > --- a/arch/x86/platform/intel-mid/pwr.c
> > +++ b/arch/x86/platform/intel-mid/pwr.c
> > @@ -272,6 +272,25 @@ int intel_mid_pci_set_power_state(struct pci_dev
> > *pdev, pci_power_t state)
> > }
> > EXPORT_SYMBOL_GPL(intel_mid_pci_set_power_state);
> >
> > +pci_power_t intel_mid_pci_get_power_state(struct pci_dev *pdev)
> > +{
> > + struct mid_pwr *pwr = midpwr;
> > + int id, reg, bit;
> > + u32 power;
> > +
> > + if (!pwr || !pwr->available)
> > + return PCI_UNKNOWN;
> > +
> > + id = intel_mid_pwr_get_lss_id(pdev);
> > + if (id < 0)
> > + return PCI_UNKNOWN;
> > +
> > + reg = (id * LSS_PWS_BITS) / 32;
> > + bit = (id * LSS_PWS_BITS) % 32;
> > + power = mid_pwr_get_state(pwr, reg);
> > + return (__force pci_power_t)((power >> bit) & 3);
> > +}
> > +
> > void intel_mid_pwr_power_off(void)
> > {
> > struct mid_pwr *pwr = midpwr;
> > diff --git a/drivers/pci/pci-mid.c b/drivers/pci/pci-mid.c
> > index 55f453d..c7f3408 100644
> > --- a/drivers/pci/pci-mid.c
> > +++ b/drivers/pci/pci-mid.c
> > @@ -29,6 +29,11 @@ static int mid_pci_set_power_state(struct pci_dev
> > *pdev, pci_power_t state)
> > return intel_mid_pci_set_power_state(pdev, state);
> > }
> >
> > +static pci_power_t mid_pci_get_power_state(struct pci_dev *pdev)
> > +{
> > + return intel_mid_pci_get_power_state(pdev);
> > +}
> > +
> > static pci_power_t mid_pci_choose_state(struct pci_dev *pdev)
> > {
> > return PCI_D3hot;
> > @@ -52,6 +57,7 @@ static bool mid_pci_need_resume(struct pci_dev
> > *dev)
> > static struct pci_platform_pm_ops mid_pci_platform_pm = {
> > .is_manageable = mid_pci_power_manageable,
> > .set_state = mid_pci_set_power_state,
> > + .get_state = mid_pci_get_power_state,
> > .choose_state = mid_pci_choose_state,
> > .sleep_wake = mid_pci_sleep_wake,
> > .run_wake = mid_pci_run_wake,
>
> Shouldn't this serialize like this
>
> might_sleep();
>
> reg = (id * LSS_PWS_BITS) / 32;
> bit = (id * LSS_PWS_BITS) % 32;
>
> mutex_lock(&pwr->lock);
> power = mid_pwr_get_state(pwr, reg);
> mutex_lock(&pwr->lock);
>
> return (__force pci_power_t)((power >> bit) & 3);
>
> there's a corresponding flow in mid_pwr_set_power_state() that operates
> in exactly that way.
mid_pwr_set_power_state() uses a series of steps (set the power state,
wait for completion) so presumably Andy thought this needs to be done
under a lock to prevent concurrent execution.
mid_pwr_get_state() on the other hand is just a register read, which
I assume is atomic. The other stuff (calling intel_mid_pwr_get_lss_id(),
calculation of reg and bit) seems to be static, it never changes across
invocations. Hence there doesn't seem to be a necessity to acquire
the mutex and call might_sleep().
That said I'm not really familiar with these devices and rely on Andy's
ack for correctness. Andy if I'm mistaken please shout, otherwise I
assume the patch is correct.
The usage of a mutex in mid_pwr_set_power_state() actually seems
questionable since this is called with interrupts disabled:
pci_pm_resume_noirq
pci_pm_default_resume_early
pci_power_up
platform_pci_set_power_state
mid_pci_set_power_state
intel_mid_pci_set_power_state
mid_pwr_set_power_state
Thanks,
Lukas
next prev parent reply other threads:[~2016-10-23 14:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 11:55 [PATCH v3 0/1] x86/platform/intel-mid: Retrofit pci_platform_pm_ops Lukas Wunner
2016-10-23 11:55 ` [PATCH v3 1/1] x86/platform/intel-mid: Retrofit pci_platform_pm_ops ->get_state hook Lukas Wunner
2016-10-23 12:37 ` Bryan O'Donoghue
2016-10-23 14:57 ` Lukas Wunner [this message]
2016-10-23 16:25 ` Bryan O'Donoghue
2016-10-24 9:15 ` Andy Shevchenko
2016-10-24 10:09 ` Lukas Wunner
2016-10-24 11:05 ` Andy Shevchenko
2016-10-25 6:19 ` Lukas Wunner
2016-10-26 14:06 ` Bryan O'Donoghue
2016-10-26 15:01 ` Andy Shevchenko
2016-11-06 13:43 ` Thorsten Leemhuis
2016-11-06 17:12 ` Lukas Wunner
2016-11-07 12:12 ` [tip:x86/urgent] " tip-bot for Lukas Wunner
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=20161023145757.GA4909@wunner.de \
--to=lukas@wunner.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pure.logic@nexus-software.ie \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.