From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.tuxedocomputers.com (mail.tuxedocomputers.com [157.90.84.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3AA791DFC1; Thu, 18 Jan 2024 22:32:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=157.90.84.7 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705617173; cv=none; b=tG79gLIxzMEDuCgxfQgUDP9ckw7gW891QHi9cI5ZPVFu7DLyxCEUNLjakZqc0QfjA66e/Aq/7WqePVL3COumbNwE72T4EPxD2beKmxgUuWUL5Eb4e3A9C6MGrdaA1Amv8jrEwJgrPU8ROvoTfHL25I4p7iayiYtUTg3mBtCWGg0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705617173; c=relaxed/simple; bh=vlRhOFuJHHUE/Y2iOF6G7uGmlqOi2NbuVZwVBWP4ZIU=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=vATPdIzTHHnIPRnxBinsmPcC7BFL3rLRHtUqyCje/eLy6gjl8lGJMW4hLL0jTtOyuKEQMzLYiUBvXhzF8sNQ25q3bxp7XgOhOi6z01HEufeuBF0mFPcuBjpTJ9ITOUD/MTkRVD9sazODkiUFuGAVkPYzLJqhLhlX8jHoZUahhQw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=tuxedocomputers.com; spf=pass smtp.mailfrom=tuxedocomputers.com; dkim=pass (1024-bit key) header.d=tuxedocomputers.com header.i=@tuxedocomputers.com header.b=skrnqaFi; arc=none smtp.client-ip=157.90.84.7 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=tuxedocomputers.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=tuxedocomputers.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=tuxedocomputers.com header.i=@tuxedocomputers.com header.b="skrnqaFi" Received: from [192.168.42.20] (p5de453e7.dip0.t-ipconnect.de [93.228.83.231]) (Authenticated sender: wse@tuxedocomputers.com) by mail.tuxedocomputers.com (Postfix) with ESMTPSA id AC7DC2FC0077; Thu, 18 Jan 2024 23:32:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuxedocomputers.com; s=default; t=1705617166; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TcAihJqhysfhWWUhnS+B4zIl0C6+wxno+qUkxODtDPs=; b=skrnqaFiJ30IpZ0KeddjZA0Z9cIyIwoe8HLgXuaXz4KKqIqEgsudvsukql3T+IOW2uDbHP jbaMWKK87uEsRCg4DQDKW+Bhy5QKSKPozbH+Z1GqYBHr+Ux753Hg5FX87UfK6mrFBDVuPi v6Aw2KkthLlUGXtzlf1gUT2gzI0QhP4= Authentication-Results: mail.tuxedocomputers.com; auth=pass smtp.auth=wse@tuxedocomputers.com smtp.mailfrom=wse@tuxedocomputers.com Message-ID: <5f144fb7-647e-4488-af20-211e95679d1c@tuxedocomputers.com> Date: Thu, 18 Jan 2024 23:32:45 +0100 Precedence: bulk X-Mailing-List: linux-input@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Implement per-key keyboard backlight as auxdisplay? To: Pavel Machek Cc: Hans de Goede , Jani Nikula , jikos@kernel.org, Jelle van der Waa , Miguel Ojeda , Lee Jones , linux-kernel@vger.kernel.org, "dri-devel@lists.freedesktop.org" , linux-input@vger.kernel.org, ojeda@kernel.org, linux-leds@vger.kernel.org References: <87sf61bm8t.fsf@intel.com> <8096a042-83bd-4b9f-b633-79e86995c9b8@redhat.com> <4222268b-ff44-4b7d-bf11-e350594bbe24@redhat.com> Content-Language: en-US From: Werner Sembach In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Am 18.01.24 um 18:45 schrieb Pavel Machek: > Hi! > >> We have an upcoming device that has a per-key keyboard backlight, but does >> the control completely via a wmi/acpi interface. So no usable hidraw here >> for a potential userspace driver implementation ... >> >> So a quick summary for the ideas floating in this thread so far: >> >> 1. Expand leds interface allowing arbitrary modes with semi arbitrary >> optional attributes: >>     - Con: >> >>         - Violates the simplicity paradigm of the leds interface (e.g. with >> this one leds entry controls possible multiple leds) > Let's not do this. > >> 2. Implement per-key keyboards as auxdisplay >> >>     - Pro: >> >>         - Already has a concept for led positions >> >>         - Is conceptually closer to "multiple leds forming a singular entity" >> >>     - Con: >> >>         - No preexisting UPower support >> >>         - No concept for special hardware lightning modes >> >>         - No support for arbitrary led outlines yet (e.g. ISO style enter-key) > Please do this one. 2 more maybe cons to add to this that popped into my mind just now: - How would lightbars, or mice fit into this? - How do 3-zone, 4-zone, n-zone keyboards fit into this? aka how many zones to be considered an aux display? > >> 3. Implement in input subsystem >> >>     - Pro: >> >>         - Preexisting concept for keys and key purpose >> >>     - Con: >> >>         - Not in scope for subsystem >> >>         - No other preexisting light infrastructure > Or negotiate with input people to do this. > >> 4. Implement a simple leds driver only supporting a small subset of the >> capabilities and make it disable-able for a userspace driver to take over > No. Kernel should abstract this away. > > Best regards, > Pavel Kind regards, Werner