From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) (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 44C4429D273 for ; Wed, 28 Jan 2026 11:21:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.65 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769599263; cv=none; b=R8DcB84Gc28lZ5v1BCyxqwkQ7ta4z0zXgJ0jo/MC/C9Bf7FvKxQ+7CFYtvQf6pdz23sYYCVD4mh/mZwKYVg/vFPyD3SMMyQxal8uZBfIiNJwyEDhU7DAO5e8ofDSNt6agc9tTEtCZUIoij/5hZ5DWq+bDBHEnfGjJCRrJI8Vrag= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769599263; c=relaxed/simple; bh=wosS8gSZQwNatY59Tw5xbh3t7QOl2V3ezMLzg/qyqP0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=tvWa+Z45YT+vTi88Ge8hl53C1ScysgrYmfH4D6kfW57dKxx5Yjv0sDfZ3+1DQe4Kif7fH11AzAcGZhCvXmNn48VEulHfL2HWJqtdt31K/FDXnjxkm6yRAbpxn3a7MukL94qeNHEU8h7k+Z+pQ9iqldWJQ9wRDwMehvuE0d6rEfE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=riscstar.com; spf=pass smtp.mailfrom=riscstar.com; dkim=pass (2048-bit key) header.d=riscstar-com.20230601.gappssmtp.com header.i=@riscstar-com.20230601.gappssmtp.com header.b=3f7kyQJi; arc=none smtp.client-ip=209.85.128.65 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=riscstar.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=riscstar.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=riscstar-com.20230601.gappssmtp.com header.i=@riscstar-com.20230601.gappssmtp.com header.b="3f7kyQJi" Received: by mail-wm1-f65.google.com with SMTP id 5b1f17b1804b1-4801ea9bafdso27783005e9.3 for ; Wed, 28 Jan 2026 03:21:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riscstar-com.20230601.gappssmtp.com; s=20230601; t=1769599260; x=1770204060; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=wosS8gSZQwNatY59Tw5xbh3t7QOl2V3ezMLzg/qyqP0=; b=3f7kyQJiVxjHELXA4HQAbjkI5vTJ5Pwe5iijLrNLeOEP9tiquUiuL+cDN23L9fCiGa ljNkUR47Qv2FRTFvR3hGGXUhlKwiKMFGwukZaDO406Y5SAWegqU9M8hDIzKkiFVJNoKq w6sUtPZ9UtILnQ5sJeo3zsS4pGmN3x5CXxKlptOB3ea+16C5dESdRyylWRJPpnWUxPFn jfFwxTj4htTnIWuw6zWwPoCPfhCyp5eTH/mWMyJEXFzkxPwSN69j1o1iSeXu1WgKp8i6 e9/hbvMEH1mB+210rf2PnZhxmt34F0Rl4vI+yxJNASGhkxfouPfhaOsIyshd/dLLTrRg D3Xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769599260; x=1770204060; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wosS8gSZQwNatY59Tw5xbh3t7QOl2V3ezMLzg/qyqP0=; b=fjA4FzdtMf5BHjk/pM1YlOzYJ+qn9NB7By7wcA0kWPPGRF2brk88WNFwcuVCzNtfaK vAw42WYrgccwN9cHu8Edi/12qhObrggr1eIKm4g+O4tIQPNQG+tYxIGsEFdyJr/KA+J1 bQrIE2zLwkkFRRq9yqP+2pGR9DhpgRzYKnL8nHhajN37Ajy6Xfm+m1Od+kuHMTqusu3N qCde10GU6cWNHtTenBZOr0PzZGqE4mgg+81TgTfRqNehPE0tFfqfJAq5dVjgXA1FSbpD mB9+s2qac4E2IH0BRjlp/NvLILzGrupdJDwBL4cLJj98EtSY/Bdn6nK5GO8I3V5T/ZAP GkYw== X-Forwarded-Encrypted: i=1; AJvYcCViqpj3K2JLmUaAAX9Sy5QCtdePRNyjxPi1ybhO8Nq6K1K+k35ZK7QnodTVKmr7I4FmB7YnL9RSrchb@vger.kernel.org X-Gm-Message-State: AOJu0YwAh1XLkYrzhdtA2fiJf5V+uZQ1MCZoaUoqpNX6imd5P8CPGAF+ iJRx76cLFEUf4UvOLPbljUeUksj0pCrFdoPg9jWPYyZB1UVAkHKFh0LXADMNwfGS+4E= X-Gm-Gg: AZuq6aK3Ir3Rxt4PCetpKWQ5NKI1pQ4RNAvocloOLMTbyHrcfSGnKtZOPKYTg10W5iB S0WnW3UwwxA3/UGqx4WUyZWFjuOc7Ib4MH+jrVemDtrkU5IXt3aL6D5/YjnIeKeavbKZdYdk4PH TYxh6t++RSaC0JRBtapXOrlXN6PUSPKDk5SywxjQzodxlrmQ0q3R9nazAW8S+fZYGiA1ajbTMEN og1DhpKmOxAnDuqxDSWwKrHXXW4TxKc6r4Uv/owbd1c8r9MLKkk258Y8ad+2pTBtks1NYtJcs7x cb37Sg5qyLtX5ggqEyGbucYPOYgYpaNcT6NO9ohvT168+GuQNkGcu+CJRpu1lXuNUlODIBxx9zu B6w89rDWjp0TD/byLAH1ZkUFHydMs/CQK1+0CmEmqXu4dd4+yXqpjHrzdbJENhHFHz3yVA5f1wA YGlEduJsagePVIMmIwl9zxyAABuGt3iO0PbU9DIPs276Sxd+VUV8mUWf/DP0gs85eC+rqy5PluJ GhlYN82r1UXDFqXeCsVVAmZ5SA4eC7Hl/xDykJyY08I9RaNCOXZvzonObpkjRf4toMgpIea X-Received: by 2002:a05:600c:8b61:b0:46e:32dd:1b1a with SMTP id 5b1f17b1804b1-48069bfad7fmr63503125e9.7.1769599259657; Wed, 28 Jan 2026 03:20:59 -0800 (PST) Received: from aspen.lan (aztw-34-b2-v4wan-166919-cust780.vm26.cable.virginm.net. [82.37.195.13]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4806e2e5ffcsm4307315e9.18.2026.01.28.03.20.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Jan 2026 03:20:59 -0800 (PST) Date: Wed, 28 Jan 2026 11:20:56 +0000 From: Daniel Thompson To: Krzysztof Kozlowski Cc: tessolveupstream@gmail.com, lee@kernel.org, danielt@kernel.org, jingoohan1@gmail.com, deller@gmx.de, pavel@kernel.org, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-leds@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] dt-bindings: backlight: gpio-backlight: allow multiple GPIOs Message-ID: References: <20260120125036.2203995-1-tessolveupstream@gmail.com> <20260120125036.2203995-2-tessolveupstream@gmail.com> <3f3c47ea-1660-4bd4-ab89-3bdf58217995@kernel.org> <54d156ba-e177-4059-a808-2505983b4e2e@gmail.com> <500b603d-5abc-4c45-8d56-bbc88fc85b83@kernel.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <500b603d-5abc-4c45-8d56-bbc88fc85b83@kernel.org> On Wed, Jan 28, 2026 at 11:11:33AM +0100, Krzysztof Kozlowski wrote: > On 23/01/2026 12:11, tessolveupstream@gmail.com wrote: > > > > > > On 20-01-2026 20:01, Krzysztof Kozlowski wrote: > >> On 20/01/2026 13:50, Sudarshan Shetty wrote: > >>> Update the gpio-backlight binding to support configurations that require > >>> more than one GPIO for enabling/disabling the backlight. > >> > >> > >> Why? Which devices need it? How a backlight would have three enable > >> GPIOs? I really do not believe, so you need to write proper hardware > >> justification. > >> > > > > To clarify our hardware setup: > > the panel requires one GPIO for the backlight enable signal, and it > > also has a PWM input. Since the QCS615 does not provide a PWM controller > > for this use case, the PWM input is connected to a GPIO that is driven > > high to provide a constant 100% duty cycle, as explained in the link > > below. > > https://lore.kernel.org/all/20251028061636.724667-1-tessolveupstream@gmail.com/T/#m93ca4e5c7bf055715ed13316d91f0cd544244cf5 > > That's not an enable gpio, but PWM. > > You write bindings for this device, not for something else - like your > board. Sudarshan: I believe at one point the intent was to model this hardware as a pwm-backlight (using enables GPIOs to drive the enable pin) attached to a pwm-gpio (to drive the PWM pin). Did this approach work? Daniel.