Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1187831ybp; Fri, 4 Oct 2019 10:45:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqz0yeXQD0I5ZQ383+53hxGzEMjqxGC/zJofRS1y+feqUfllsmA/lwuPWNPxO+UD/qpn/+Nw X-Received: by 2002:a05:6402:2cb:: with SMTP id b11mr16824781edx.285.1570211139338; Fri, 04 Oct 2019 10:45:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570211139; cv=none; d=google.com; s=arc-20160816; b=a7+qiLpuM19AgYcywAFTMvTpWt74EjRO2zOYdvxOxPEa5sZAw7zAwFI88CllPWml55 RzusjJofFmyDynfNACDCL7z4vrh7nnORMkty5cYKomDwAQwpIZY11p9VVgPdJcF64Nw3 VG+Zj2SasACgAZcF1xLhhREGycN26e5rS1UtTM3NLmLHV3+k86er/yJAf6iyCcPjUPVm P82XTYiln2vNWzwILhfBRS7k1QIwxdso0brTMe5nILAEAMJcdwL9996cbGebVWJVjlMQ wU5iVHcj6IbOnh6v4EhD0zlmmSGqkQC76cKII++B2vdFO7mXUSbD1GdGHaxnITuxsolr +K0A== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=SAkQpxESi/jK/m+F0rStFnkhrz33ICzQ+DcDMRtBMOc=; b=nbUnXw3HAJdHoE6Hx2dZ8hN2/GSnHt+ukdYHOUTC1RSA37T34CXFJ194KvSaeNuCMj LIPTvxsGOf6vDI0FJ1G8e0Vl7suL2dlKFVGlaFIsvzClRZQBRHoGZIif83pPHuxoYfhp zeL2cn1s3C/diy+c41uqPNtL2gmAEXl0hjVpH5WoP1uYoH8Px5qFTATGM3ts36iS2B5a MqjveVAa+0BYp85zwUwJQ/qNyw/olsHvoH1xRC+8XahROCI6/syCkrmmj1nTehxcXV/k 6tsPLUfOj0SnFSod+C3flQNS/mEGtfHxFYZgnlq/WqD3CUopiaay2FX45srWPycdGQZS jiXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=okGkzQUW; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t9si3361294ejr.29.2019.10.04.10.45.14; Fri, 04 Oct 2019 10:45:39 -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=fail header.i=@sirena.org.uk header.s=20170815-heliosphere header.b=okGkzQUW; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388573AbfJDRmm (ORCPT + 99 others); Fri, 4 Oct 2019 13:42:42 -0400 Received: from heliosphere.sirena.org.uk ([172.104.155.198]:33848 "EHLO heliosphere.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387428AbfJDRmm (ORCPT ); Fri, 4 Oct 2019 13:42:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sirena.org.uk; s=20170815-heliosphere; h=In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=SAkQpxESi/jK/m+F0rStFnkhrz33ICzQ+DcDMRtBMOc=; b=okGkzQUW1797du/qbiyU6EyTw kqBvY+MybQMETrMgtajMpbz4dL/mwe/X9jSDkTvVk0+l1N+Z0BcM9MBpoS8fxIe58uQ5iGsTmDPHy +kBUdi0rmHeK/AmZLnqHWshr8L32Qcfu5Hm4ideAmeVG2xuJKILTkT2bJgwei093dPNSE=; Received: from cpc102320-sgyl38-2-0-cust46.18-2.cable.virginm.net ([82.37.168.47] helo=ypsilon.sirena.org.uk) by heliosphere.sirena.org.uk with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iGRb8-0003s3-Gr; Fri, 04 Oct 2019 17:42:34 +0000 Received: by ypsilon.sirena.org.uk (Postfix, from userid 1000) id 78CA62741EF0; Fri, 4 Oct 2019 18:42:33 +0100 (BST) Date: Fri, 4 Oct 2019 18:42:33 +0100 From: Mark Brown To: Jean-Jacques Hiblot Cc: mark.rutland@arm.com, daniel.thompson@linaro.org, Liam Girdwood , tomi.valkeinen@ti.com, Sebastian Reichel , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, robh+dt@kernel.org, Jacek Anaszewski , pavel@ucw.cz, lee.jones@linaro.org, linux-leds@vger.kernel.org, dmurphy@ti.com Subject: Re: Should regulator core support parsing OF based fwnode? Message-ID: <20191004174233.GF4866@sirena.co.uk> References: <20191003183554.GA37096@sirena.co.uk> <25b9614f-d6be-9da5-0fe5-eb58c8c93850@gmail.com> <20191003194140.GE6090@sirena.co.uk> <20191004113942.GB4866@sirena.co.uk> <20191004144029.GC4866@sirena.co.uk> <6df68ecb-f92e-fd9c-7f55-f66fa463263a@ti.com> <20191004155838.GE4866@sirena.co.uk> <95a43632-57d0-2705-a2d3-d64827212692@ti.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="HCdXmnRlPgeNBad2" Content-Disposition: inline In-Reply-To: <95a43632-57d0-2705-a2d3-d64827212692@ti.com> X-Cookie: core error - bus dumped User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --HCdXmnRlPgeNBad2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Oct 04, 2019 at 06:12:52PM +0200, Jean-Jacques Hiblot wrote: > On 04/10/2019 17:58, Mark Brown wrote: > > Regulator supplies are supposed to be defined at the chip level rather > > than subfunctions with names corresponding to the names on the chip. ... > > good chance that they come up with the same mapping. The supply_alias > > interface is there to allow mapping these through to subfunctions if > > needed, it looks like the LED framework should be using this. > In case of current-sink LED drivers, each LED can be powered by a different > regulator, because the driver is only a switch between the LED cathod and > the ground. Sure, it's common for devices to have supplies that are only needed by one part of the chip which is why we have the supply_alias interface for mapping things through. > > That said if you are doing the above and the LEDs are appearing as > > devices it's extremely surprising that their of_node might not be > > initialized. > That is because this is usually done by the platform core which is not > involved here. The surprise is more that it got instantiated from the DT without keeping the node around than how it happened. --HCdXmnRlPgeNBad2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl2XhIgACgkQJNaLcl1U h9Ax0wf7BtlHwZ3DGTnXuJN85FVOLdmgDfERGDVQS+pR3WFG/BLI42EXa+OfXl6S VF7r82YlzCBgY4z9Qm+DXbEkxdRyYzDu+fXp7iT/gEpuN8tS+y/vEAlfz8TVxbmi P1cNkSnXcO4kKFGwW6mzVKOWE9Odxw1kFu0srade53RfiIC0xhXGafHXplRiIM+7 2saUeJgmWDYsOAcSO7IBvnoicuXNOn0+FPV9O+Raj+1vw5BCD6wJGdbCQPI+OYSl DfaR1UmYKJkXH5wCjCHsaAkMI3Y/1u04Xoik5Y2cle8e1DdE6w1a/vzIEhLIqup2 Nzc07kK12LcFNNRdcqE4MiRNMNpS+Q== =FQdn -----END PGP SIGNATURE----- --HCdXmnRlPgeNBad2--