From: Bjorn Helgaas <helgaas@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Drop Kconfig option PCIEASPM?
Date: Mon, 28 Oct 2019 11:47:53 -0500 [thread overview]
Message-ID: <20191028164753.GA103542@google.com> (raw)
In-Reply-To: <1f784101-fe7a-becf-d855-ddc6d03a3f92@gmail.com>
On Fri, Oct 25, 2019 at 11:42:06PM +0200, Heiner Kallweit wrote:
> I wonder whether anybody actually wants to disable ASPM support.
> In an old Kconfig commit message is mentioned that it may help
> to reduce kernel size of embedded systems. However I would
> think that on embedded systems ASPM is quite useful as it
> saves significant power and may result in a lower system
> temperature therefore.
> W/o ASPM support we have to live with devices coming up
> in whatever mode boot loader or firmware configure.
What would be the advantage of dropping CONFIG_PCIEASPM? I don't
think it really costs us much to keep it. I do agree most systems
probably want it.
prev parent reply other threads:[~2019-10-28 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 21:42 Drop Kconfig option PCIEASPM? Heiner Kallweit
2019-10-28 5:41 ` Vidya Sagar
2019-10-28 6:26 ` Heiner Kallweit
2019-10-28 16:47 ` Bjorn Helgaas [this message]
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=20191028164753.GA103542@google.com \
--to=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=linux-pci@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).