From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com [209.85.128.54]) (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 CE7F13BE627 for ; Mon, 23 Mar 2026 18:12:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.54 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774289534; cv=none; b=rvui8G/uCy+VTWGpN7NbnsmBMyta4EsqVJD0kMshkNgUSOtJSmJkOUZblMd1s2Me/JJaILx8p9wnchOUigWZVy7SWiOR637n2ariRbo9inBufafAVOW4zoOSCZywfEGDxPpekXWwnp67EnDYG4Lh+J4df6/1gT30U5jGlV6/CnY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774289534; c=relaxed/simple; bh=xF2bAPNppAbfTBIBcDCV+LZAzGseQQW9IhFcftMAsW4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=A/6UaKUsYm/FX+nwihw1tFbA45krBdPY+lapLJV9ro1RMLPIbcc1s2mYShztGBklf5ZcFEZtNTuJqHI8CqFyQZxAzxWMFZP+UDdGeHRErifaYcbcYyBokAtR6KAK1KrOL92t2cOwVXMNlWrGwRIups1/ReV1Xdx5GOboo6n9Qj0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=YdmLDwPR; arc=none smtp.client-ip=209.85.128.54 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="YdmLDwPR" Received: by mail-wm1-f54.google.com with SMTP id 5b1f17b1804b1-48702d51cd0so30336955e9.2 for ; Mon, 23 Mar 2026 11:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1774289531; x=1774894331; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=CIyRKh/yzbhrSofJPevkwLbR5QRnYf8Ol5laJ4H1+4U=; b=YdmLDwPRAFDXjri6eNne1/45dZWmLd/XyM6dddFTLm5BGMW4TPmdzqaJwOxN9crkI1 Wlg7vZlv7r6AlucbmnxyJ2DhzpOUeFux6Q22QItATdBKLCZFIfWSrTv4ZuqeVn5guyS3 3HR+GRcEhgQkB5dtulXl8FLyZhd9GpnYOgUnRF9p0zxTSP3MGPn+RuNDoAqohCNUc1n8 xt2UIgZDqMlXR6WW5cn3JqT59fM5P6RYTM3MOP4TSmUEvy3crQn8ZROLNAGcubKp4kAW SesBncEzWVnj54lAXJtg6FJy4hYPjLFwEPDmIT7lwrRPn03dkYIHaZZTIL7C8uPrqMVt rP5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774289531; x=1774894331; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CIyRKh/yzbhrSofJPevkwLbR5QRnYf8Ol5laJ4H1+4U=; b=UwVEW8AxAtcYvNiftz6Ex+V9RB537BRvx3kyVUhfnhy8KsXtJLwFJVFGHvoOhBL+Vg YAxidpgiZjSsoiRNbBP+agM0aljHhdj5oYttroHpHtg9YvHnjC3MnSVzd67BXuOUmITP oW6YmvfpIpJ8sC8tID/wTzsqpH2BQqWKzvrnfdo6Xlk2UUxxaSCyuyKnES30Rz65jrHm GKFDycRf6+6Gf7H0fkDIncx1vXwoL2mxj9CufiFjmZSY1hJH6qTW6x1804u8sHriR3h5 M5N3xn9NEB7RaDROXFfRiuyx6cLXXaC5iN8JL2VRkpclPiP6dvpqeAVXlIpenItX28qU Wc8w== X-Forwarded-Encrypted: i=1; AJvYcCXWKZ0XwXCMdU9A6/Bc4k5cnfKlnYoUkGPuapGPIpEuRgJGNjyJ910IV6uRmHusHyEK58/eAZG6PdU=@vger.kernel.org X-Gm-Message-State: AOJu0YzrPVh6EKIiIVGqytWfKXF4KZOJnvbzIi6Be/RlJ35MjEA0zRqR hVH5qZvscWOveMM1xoPetU2WMaAOXxM4KajldewFXaTd/qlk5GcdGORf2PXKAw== X-Gm-Gg: ATEYQzziYOgEp5lVEGVM657Xpm7Nm+sgyFxsX+QmHgebs40gBy/XU/KOxB7KuIxv8B9 bGxYv/8pUUCuvaD3/Hk4E9IekPXvKTgkFan5BNbE39wFgRT+OAoG15k/MlYTsrjHfUpC0vpt7r5 9eQnkCwjUDJRmXjGtEN+yuYWfmAYE/USwrP0WqQWuF3C+aHlxGpRaeL5rapLaKOIG7sOttGgPr7 aIgB+3NlUuxQUmO7sa3tNlRkwvY9Wb1XJ8sUGdAx7cS8DZLuh15kH9Km/dZQ5nmgcDcZx9Yaj// z6FhMvUQAJNhi0wNyGQ33zpLA6Bg1f5ozOirDrULv47zGABc4kJW0Z/+S4suxAPohn6Bhk0GNdH J6R6LY917UT3WlNIiQ74LuUj/F0KdNslHDd+ymiTIwcb73uxhPI8QAJWZRe39fuoCuIF+VwxLs4 mfYhx7BP/kjAPWqx2Kk3Nd7qMjXOPyCvfn1TM= X-Received: by 2002:a05:600c:a418:b0:485:3423:727d with SMTP id 5b1f17b1804b1-486ff03f502mr147150825e9.26.1774289530991; Mon, 23 Mar 2026 11:12:10 -0700 (PDT) Received: from [192.168.0.193] ([194.183.54.57]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4870f6e9646sm386325e9.19.2026.03.23.11.12.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Mar 2026 11:12:10 -0700 (PDT) Message-ID: <9a6cc642-aa66-4358-9ad7-9e4cc381a07a@gmail.com> Date: Mon, 23 Mar 2026 19:12:09 +0100 Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC PATCH 1/1] leds: Introduce the multi_max_intensity sysfs attribute To: Armin Wolf , lee@kernel.org, pavel@kernel.org Cc: corbet@lwn.net, skhan@linuxfoundation.org, linux-leds@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, wse@tuxedocomputers.com, pobrn@protonmail.com References: <20260314230107.65444-1-W_Armin@gmx.de> <20260314230107.65444-2-W_Armin@gmx.de> Content-Language: en-US From: Jacek Anaszewski In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 3/23/26 11:22 AM, Armin Wolf wrote: [...] >>> led-class-multicolor.h >>> index db9f34c6736e..67ac0ac0fd54 100644 >>> --- a/include/linux/led-class-multicolor.h >>> +++ b/include/linux/led-class-multicolor.h >>> @@ -9,10 +9,33 @@ >>>   #include >>>   #include >>>   +#define LED_USE_MAX_BRIGHTNESS 0 >>> + >>> +/** >>> + * struct mc_subled - Color component description. >>> + * @color_index: Color ID. >>> + * @brightness: Scaled intensity. >>> + * @intensity: Current intensity. >>> + * @max_intensity: Maximum supported intensity value. >>> + * @channel: Channel index. >>> + * >>> + * Describes a color component of a multicolor LED. Many multicolor >>> LEDs >>> + * do no support gobal brightness control in hardware, so they use >>> + * the brightness field in connection with >>> led_mc_calc_color_components() >>> + * to perform the intensity scaling in software. >>> + * Such drivers should set max_intensity to LED_USE_MAX_BRIGHTNESS >> >> I'd just mention here that the field needs to be left initialized to 0, >> to let the LED subsystem to adjust it to max_brightness. Note that in >> case of max_brightness we allow for the same - if it is 0, then >> led-class.c adjusts it to legacy LED_FULL (255). >> > OK, do you think that having LED_USE_MAX_BRIGHTNESS makes sense? Not really, let's drop it. -- Best regards, Jacek Anaszewski