From: Luca Coelho <luca@coelho.fi>
To: Paul Bolle <pebolle@tiscali.nl>,
linux-wireless@vger.kernel.org, chris@rorvick.com
Cc: linuxwifi@intel.com, emmanuel.grumbach@intel.com,
johannes@sipsolutions.net, kvalo@codeaurora.org,
oren.givon@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: pcie: fix SPLC structure parsing
Date: Thu, 13 Oct 2016 20:49:43 +0300 [thread overview]
Message-ID: <1476380983.3880.33.camel@coelho.fi> (raw)
In-Reply-To: <1476363353.1999.17.camel@tiscali.nl>
On Thu, 2016-10-13 at 14:55 +0200, Paul Bolle wrote:
> On Thu, 2016-10-13 at 15:44 +0300, Luca Coelho wrote:
> > Even though there is apparently something wrong with this part of the
> > ACPI table on you laptop, since it doesn't match our specifications.
> > In any case, it's mostly harmless.
>
>
> Would a correct implementation by Dell have any benefits for the users
> of these laptops? In other words: should I bother somehow contacting
> Dell and point them to this discussion in order to have them fix this?
This value provides a way for the OEM to fine tune the power budget of
the device. This is (usually) used to prevent parts of the platform
from getting too hot. We have a certain default that is good enough
for most cases. If Dell didn't want to set proper limits for this
device, it probably means that it is not a concern. Dell does set
these values correctly for other platforms.
So, I guess it's up to you if you want to clarify this with them. This
could be some default "blank" values when they don't want to change
them.
--
Luca.
next prev parent reply other threads:[~2016-10-13 17:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 7:19 [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning Chris Rorvick
2016-10-10 14:02 ` Luca Coelho
2016-10-11 10:11 ` Paul Bolle
2016-10-11 14:09 ` Chris Rorvick
2016-10-11 14:27 ` Chris Rorvick
2016-10-12 6:25 ` Luca Coelho
2016-10-12 4:32 ` Chris Rorvick
2016-10-12 12:24 ` Luca Coelho
2016-10-12 12:36 ` Paul Bolle
2016-10-12 13:06 ` Luca Coelho
2016-10-12 6:11 ` Luca Coelho
2016-10-12 6:52 ` Paul Bolle
2016-10-12 17:50 ` Chris Rorvick
2016-10-12 18:05 ` Paul Bolle
2016-10-12 18:36 ` Chris Rorvick
2016-10-13 9:01 ` Luca Coelho
2016-10-13 10:21 ` [PATCH] iwlwifi: pcie: fix SPLC structure parsing Luca Coelho
2016-10-13 11:27 ` Paul Bolle
2016-10-13 11:30 ` Luca Coelho
2016-10-13 12:36 ` Paul Bolle
2016-10-13 12:44 ` Luca Coelho
2016-10-13 12:55 ` Paul Bolle
2016-10-13 17:49 ` Luca Coelho [this message]
2016-10-13 13:56 ` Chris Rorvick
2016-10-13 14:30 ` Luca Coelho
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=1476380983.3880.33.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=chris@rorvick.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oren.givon@intel.com \
--cc=pebolle@tiscali.nl \
/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).