Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp4520654ybp; Mon, 14 Oct 2019 06:04:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqw2axKDT7vgksC20aIOdW9SuVHjnf3Fo4Yvoc34zHDjYZBW2w0F+3thoVWaIRLWuCj01WZP X-Received: by 2002:a17:906:1dd3:: with SMTP id v19mr29009561ejh.35.1571058284808; Mon, 14 Oct 2019 06:04:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571058284; cv=none; d=google.com; s=arc-20160816; b=ca9rkomeu2mNkXl6T3oLtYX1b9w0GlQcvXmyYvOXc2NP4l0T2jOcUEMzMIU2BdSMi8 R231YNDNATNOJc8Z7fStz6j9k9iIFxei6GBhLCZ/vsKJkcY6F6PeGVADPdujiWKlt4T5 GSLb/plW/Q9qKvz7PP0cm+68ZdgjfECV9IS8PG4RYCNtNDYlApBHR2MeaKFie41fq6bz yW2XpCkE/HYDaIDWxXFZ8YWTBj4yoKwq1xDZV2t6czUmcwAeEg6frmvL5raWT5kuv3XP EAoAgD+JPJ1Csn9oUarnw++gS9Z+FosUAkVaBcHwDY5VirTbHh3ITsMncqXK3xmdMy1W NWXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=n+yPkcAtfV0uGXnqQ5l9CgswhmsyO7bUGevjjjP7SsU=; b=KheHRvC6hxS4pBnNF6Ulp1i9velOAz+cS6rvz7ZPtxkcBllPJ9XEJgLQVkMqDxgNyN l9TCPwb0YlJbbclGc9oN+DtJKu8RjS4+/ChSJ+A7PJJIKUucDlU5yH996QXcNWcFcYup mgvwKnKvYAS7+8gatFPEZNE4lVryWPt1vT3FVAlV8U34cWmdTNA2zptpvNd8jGXjhoY6 InNL+8BCNOLSrJeHK/6Ri5jkP2y0ulmww1TBJP+sQrBeSqrXi7C3LVI9MHH6rfcGwgHe tQjemLP8JWJr/CkJ65oE6A0n7X0p88xNPYgVTATr7FdTbgYJEwYJZgo+kLUo/fXer+cU 48zQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=A79ceiqR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d17si10559461edv.76.2019.10.14.06.04.19; Mon, 14 Oct 2019 06:04:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=A79ceiqR; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730830AbfJNMiz (ORCPT + 99 others); Mon, 14 Oct 2019 08:38:55 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:34339 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730800AbfJNMiz (ORCPT ); Mon, 14 Oct 2019 08:38:55 -0400 Received: by mail-wr1-f68.google.com with SMTP id j11so19572246wrp.1 for ; Mon, 14 Oct 2019 05:38:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=n+yPkcAtfV0uGXnqQ5l9CgswhmsyO7bUGevjjjP7SsU=; b=A79ceiqRSzseaHRlZZLlXa96+PS5g04Icp7X8OBGCpMjSWZMKo6YOwikpLf6/jQBMq fy340S/jR7Y1jWTQSQRys1d9vDsClxwWH30JJz5a9caRijoVmFpl1tPG3AosuzVtp7rP fMzukJ6d4v08D6FyVMdnpj+QAw3XCZlpVVmVGKRK61gmLAKVd4ti+q8CWQQXv7obywCj 06lRcOwuzTFo8oItdzoN8RpKOz2b8YkAtKrGvYtuBvBpWJx0wBnQCms/+f11dE23FDii VPYn6SrRQnKWrpVDmWTvuELG0ZI1jNBoKVhECHEeBhpUiP6PoKwYvoexLbVczKj1NYzt 92NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=n+yPkcAtfV0uGXnqQ5l9CgswhmsyO7bUGevjjjP7SsU=; b=qB5xYnnav161G2PG+WSlXefbN8mV6PU9zsHkWZoT+ZD39xD3rNSBfx24KNnBlmzGlM uU2cID+S8R0uxCfnTwfeonLZRh8ZVELGEoUUZnUu397BTS4+IpxPKn1OmjIcCgQqyvNN a8pnB6X6i8U+5PgA1lNZmA8ti/hUA1ctIitfXQFeiSSUXqS8tRE0oFaEKviqwU1xJseJ U9h9vN5DXhDnCF6Oj61v0asNufP/jN3MjPp+mf53D0RhO2JU64f/lMGPT808X4c5a1+0 jgX6k6lNWnW2yt/n3znJFbRo6OPQEoyFxGC1gtENFdjr/F0ppormjM+mqm2DFayJ7K9t uLQQ== X-Gm-Message-State: APjAAAX0Q7m8aaPZdNEF5M3nXe33XdPgoOF3g+J/c06yn7USwR+Ch95+ dCY4FmLWCcp+3Hj78qPZJeUE8Q== X-Received: by 2002:adf:ff87:: with SMTP id j7mr25395021wrr.360.1571056732536; Mon, 14 Oct 2019 05:38:52 -0700 (PDT) Received: from holly.lan (cpc141214-aztw34-2-0-cust773.18-1.cable.virginm.net. [86.9.19.6]) by smtp.gmail.com with ESMTPSA id c17sm21653738wrc.60.2019.10.14.05.38.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Oct 2019 05:38:51 -0700 (PDT) Date: Mon, 14 Oct 2019 13:38:49 +0100 From: Daniel Thompson To: Jean-Jacques Hiblot Cc: Pavel Machek , Jacek Anaszewski , linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org, dmurphy@ti.com, tomi.valkeinen@ti.com Subject: Re: [PATCH v5 3/3] leds: Add control of the voltage/current regulator to the LED core Message-ID: <20191014123849.fhvmqn7dyu6bminc@holly.lan> References: <20190923102059.17818-1-jjhiblot@ti.com> <20190923102059.17818-4-jjhiblot@ti.com> <3e648fab-638f-4aa0-dda9-8ddba6562751@gmail.com> <20191013120937.GK5653@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 14, 2019 at 12:49:07PM +0200, Jean-Jacques Hiblot wrote: > > On 13/10/2019 14:09, Pavel Machek wrote: > > Hi! > > > > > I must say I'm not a big fan of this change. > > > It adds a bunch of code to the LED core and gives small > > > functionality in a reward. It may also influence maximum > > > software blinking rate, so I'd rather avoid calling > > > regulator_enable/disable when timer trigger is set. > > > > > > It will of course require more code. > > > > > > Since AFAIR Pavel was original proponent of this change then > > > I'd like to see his opinion before we move on to discussing > > > possible improvements to this patch. > > Was I? > > > > Okay, this series looks quite confusing to me. First, 1/3 looks > > "interesting" (would have to analyze it way more). > > > > Second, 3/3... So we have a LED driver _and_ a regulator? So yes, the > > chip driving a LED is usually ... voltage/current regulator. What is > > second regulator doing there? Is that a common setup? > > This is quite common with current-sink LED drivers. > > The setup looks like this: > > +-----------+ > |?????????? | > | Regulator | > |?????????? +------------------------+ > |?????????? |??????????????????????? | > +-----------+????????????????????? __|__ > ?????????????????????????????????? \?? / > ???????? +---------------------+??? \ / led > ???????? |???????????????????? |???? V > ???????? |??? Led Driver?????? |?? --+-- > ???????? |???????????????????? |???? | > ???????? |???????????????????? |???? | > ???????? |??????????????? +----------+ > ???????? |????????????? \????? | > ???????? |?????????????? \???? | > ???????? |??????????????? +??? | > ???????? |??????????????? |??? | > ???????? +---------------------+ > ????????????????????????? | > ?????????????????????? +--+--+ > ?????????????????????? /////// > > > Only the regulator usually does not supply only one LED. Given questions have been raised about the complexity of the change I wondered whether, for a system with this topology, the regulator could/should be enabled when the LED driver driver probes? Daniel.