Return-Path: <linux-kernel-owner+w=401wt.eu-S1754858AbZGON6S@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754858AbZGON6S (ORCPT <rfc822;w@1wt.eu>);
	Wed, 15 Jul 2009 09:58:18 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754844AbZGON6R
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 15 Jul 2009 09:58:17 -0400
Received: from cavan.codon.org.uk ([93.93.128.6]:52900 "EHLO
	cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753957AbZGON6O (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 15 Jul 2009 09:58:14 -0400
Date: Wed, 15 Jul 2009 14:58:08 +0100
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Zhang Rui <rui.zhang@intel.com>,
       "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
       "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
       "lenb@kernel.org" <lenb@kernel.org>,
       "corentincj@iksaif.net" <corentincj@iksaif.net>
Subject: Re: [PATCH 1/3] backlight: Allow drivers to update the core, and
	generate events on changes
Message-ID: <20090715135808.GA19054@srcf.ucam.org>
References: <1247517685-7719-1-git-send-email-mjg@redhat.com> <1247574573.23871.8.camel@dax.rpnet.com> <1247644518.26272.88.camel@rzhang-dt> <1247646153.6248.3.camel@dax.rpnet.com> <1247647105.26272.99.camel@rzhang-dt> <1247649089.20241.5.camel@dax.rpnet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1247649089.20241.5.camel@dax.rpnet.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk
X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1004
Lines: 24

On Wed, Jul 15, 2009 at 10:11:29AM +0100, Richard Purdie wrote:

> So there are basically two values we're ever interested in at a given
> point in time. The current ambient light reading and the corresponding
> display luminance adjustment. Both of those could just be exposed as an
> input device really?

The alternative would be hwmon, I guess.

> Agreed, userspace should be where policy is decided. Having a standalone
> module which connected the two together with a "default" policy might be
> acceptable too though? If userspace then wants to handle things it just
> makes sure the module is not loaded.

You want smoothing even in a default policy, and doing that well might 
be a bit much for the kernel?

-- 
Matthew Garrett | mjg59@srcf.ucam.org
--
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/