[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BFE86D4.60602@nokia.com>
Date: Thu, 27 May 2010 17:51:00 +0300
From: Igor Stoppa <igor.stoppa@...ia.com>
To: ext Arjan van de Ven <arjan@...radead.org>
CC: Kevin Hilman <khilman@...prootsystems.com>,
Brown <len.brown@...el.com>, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Len@...p1.linux-foundation.org" <Len@...p1.linux-foundation.org>,
"linux-pm@...ts.linux-foundation.org"
<linux-pm@...ts.linux-foundation.org>
Subject: Re: [linux-pm] [PATCH 8/8] intel_idle: create a native cpuidle driver
for select intel processors
Hi,
ext Arjan van de Ven wrote:
> it's really inconvenient to have such drivers hidden in the
> architecture code; it's much more convenient for cpuidle developers
> if they're all in one place.
>
why?
> Think of it this way: you're not putting the NIC driver for your SOC in
> a architecture directory either...
>
>
That would be a separate chip, usually, which has its own driver.
The SOC has some bus interface and the arch-specific part of it, if any,
is in the arch directory.
igor
--
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