Date: Sun, 23 Nov 2008 19:04:09 +0100
From: Pavel Machek <pavel@suse.cz>
To: Cristiano Prisciandaro <cristiano.p@solnet.ch>
Cc: Dave Jones <davej@redhat.com>, cpufreq@vger.kernel.org,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Message-ID: <20081123180409.GB7731@ucw.cz>
References: <1227454026.7262.59.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1227454026.7262.59.camel@localhost>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1273
Lines: 34

On Sun 2008-11-23 16:27:06, Cristiano Prisciandaro wrote:
> From: Cristiano Prisciandaro <cristiano.p@solnet.ch>
> 
> The bios of the eeepc 900 exposes an acpi method that allows clocking
> the cpu to 630/900 MHz. This driver allows controlling the frequency
> switch through the cpufreq subsystem.

Is this really needed? Could we simply talk to the cpu directly,
without help of ACPI?

> +/* write to the acpi handle (from asus_acpi.c) */
> +static int write_eee900_acpi_int(acpi_handle handle, const char *method,
> +				 int val, struct acpi_buffer *output)
> +{
> +	struct acpi_object_list params;
> +	union acpi_object in_obj;
> +	acpi_status status;
> +
> +	params.count = 1;
> +	params.pointer = &in_obj;
> +	in_obj.type = ACPI_TYPE_INTEGER;
> +	in_obj.integer.value = val;
> +	status = acpi_evaluate_object(handle, (char *)method, &params, output);
> +	return status == AE_OK;
> +}

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/