public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Darren Hart <dvhart@infradead.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Zhang Rui <rui.zhang@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI / scan: Add a scan handler for PRP0001
Date: Tue, 05 May 2015 14:14:57 +0200	[thread overview]
Message-ID: <1654400.V6HOKtoCaE@vostro.rjw.lan> (raw)
In-Reply-To: <20150505112425.GB1541@lahna.fi.intel.com>

On Tuesday, May 05, 2015 02:24:25 PM Mika Westerberg wrote:
> On Tue, May 05, 2015 at 02:49:55AM +0200, Rafael J. Wysocki wrote:
> > 
> > Thanks, I have an update, though.
> > 
> > In a recent discussion with Darren we've come to the conlusion that
> > having a parent with PRP0001 and "compatible" and a child with PRP0001 only
> > (without "compatible") is useful in cases when one complex device is
> > represented by a hierarchy of "device" objects (in analogy with device
> > nodes in a DT that have no struct device representations).  Thus it isn't
> > useful to complain that "compatible" is not present in such cases.
> 
> OK, I see.
> 
> > Updated patch:
> > 
> > ---
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > Subject: ACPI / property: Refine consistency check for PRP0001
> > 
> > Refine the check for the presence of the "compatible" property
> > if the PRP0001 device ID is present in the device's list of
> > ACPI/PNP IDs to also print the message if _DSD is missing
> > entirely or the format of it is incorrect.
> > 
> > One special case to take into accout is that the "compatible"
> > property need not be provided for devices having the PRP0001
> > device ID in their lists of ACPI/PNP IDs if they are ancestors
> > of PRP0001 devices with the "compatible" property present.
> > This is to cover heriarchies of device objects where the kernel
> > is only supposed to use a struct device representation for the
> > topmost one and the others represent, for example, functional
> > blocks of a composite device.
> > 
> > While at it, reduce the log level of the message to "info"
> > and reduce the log level of the "broken _DSD" message to
> > "debug" (noise reduction).
> > 
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Still looks fine to me,
> 
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Thanks!

  reply	other threads:[~2015-05-05 12:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 23:28 [PATCH] ACPI / scan: Add a scan handler for PRP0001 Rafael J. Wysocki
2015-04-14  2:04 ` Darren Hart
2015-04-14 11:50   ` Rafael J. Wysocki
2015-04-14 13:03     ` Rafael J. Wysocki
2015-04-22  1:54       ` Rafael J. Wysocki
2015-04-22  9:57         ` Mika Westerberg
2015-05-05  0:49           ` Rafael J. Wysocki
2015-05-05 11:24             ` Mika Westerberg
2015-05-05 12:14               ` Rafael J. Wysocki [this message]
2015-04-24  0:15 ` [Update][PATCH] " Rafael J. Wysocki
2015-04-24 22:21   ` Darren Hart
2015-04-25  2:25     ` Rafael J. Wysocki

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=1654400.V6HOKtoCaE@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=dvhart@infradead.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rui.zhang@intel.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