lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121207111415.GH23611@intel.com>
Date:	Fri, 7 Dec 2012 13:14:15 +0200
From:	Mika Westerberg <mika.westerberg@...ux.intel.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-acpi@...r.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Len Brown <lenb@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ACPI: add Haswell LPSS devices to
 acpi_platform_device_ids list

On Fri, Dec 07, 2012 at 11:01:26AM +0000, Alan Cox wrote:
> On Fri,  7 Dec 2012 12:08:02 +0200
> Mika Westerberg <mika.westerberg@...ux.intel.com> wrote:
> 
> > All devices behind Haswell LPSS (Low Power Subsystem) should be represented
> > as platform devices 
> 
> What about the bus heirarchy ? What about making sure they appear in the
> PCI resource heirarchy so we don't mash them up if we reassign or
> allocate other resources on the bus ?

I'm not sure if I understand what you mean here.

We put them in hierarchy if the parent ACPI node has also a physical device
bound to it (like PCIe root port).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ