Received: by 2002:ac0:8c8e:0:0:0:0:0 with SMTP id r14csp232403ima; Tue, 5 Feb 2019 22:08:38 -0800 (PST) X-Google-Smtp-Source: AHgI3IaxSYM0dRfdD10mJ6t8lKobR0qtg1bX+j6XBYRl974ycsNHNevLVow1K1iPUkEETZSnO2XC X-Received: by 2002:a62:6303:: with SMTP id x3mr9164350pfb.110.1549433318672; Tue, 05 Feb 2019 22:08:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549433318; cv=none; d=google.com; s=arc-20160816; b=rgBG5pEnrDAlxDTCOXi4LWTxn/dVIgMrDENerg18scs0vs7WdpkA1GxENOkftafmA5 jHkpmCr7P2v90r/hwva/MgwvavDSNns6rq9pshGhxdMZD50Kcd2mzYB5oYJzgZbm3zzU Wbx9ZD8pSo5/H6Um6aGHCkDqFXMtB9VKVvohNTA88InufaeO7ZQPHlttDDsZNFmaa375 IYp8HVfUQXX7qZs5ZcBxvKotm8aH98eskGt+kWLXAxcon6vy6U3t6EDd8gR/cUXyVaYC Kev8Pc+A3MHJCZ3cIrjycE2Qxv4cDCdwsuyn2q303vJ5bmeUIrpnQOKyF174ZyNJZ4Od m6QA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=wOd5SR6fWyxKt22IQVsP2Wb/v11Trd9vKBbBZTGtnaM=; b=y8WLB4kKWMa/hntg0MakiMcYLuT7p1CP+rox9gEBAx2gcK4cqGr4DqEoLbZMwPYtaM RSm/hiWmNlt0/g+CnBupciPl0bVlU0ChT0aFYzTS+FYGAMgJRyahV74YU8RIi094Qyj2 M+P8qqCIpPIppqPnXgt12WR9BqLObji/GabO12+qXWNlN3Ua30DPMRJGwMLu6ODB2nNY 53VVqy3JoNQYotKaODekegQLu7GN59hmNyptoheoDN65/y8CTQBkg8N5WZ0B+xv8+KG1 WY9bzMe5ND8xAlbJSgR1YXDBkIqIOcnf0vObglEXAc2ubDi6sHbhQEDXYagOa0e4GoWL n+/A== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id bf4si4234775plb.163.2019.02.05.22.08.20; Tue, 05 Feb 2019 22:08:38 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726722AbfBFGGR (ORCPT + 99 others); Wed, 6 Feb 2019 01:06:17 -0500 Received: from olimex.com ([184.105.72.32]:49339 "EHLO olimex.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726001AbfBFGGR (ORCPT ); Wed, 6 Feb 2019 01:06:17 -0500 Received: from 195.238.85.143 ([195.238.85.143]) by olimex.com with ESMTPSA (ECDHE-RSA-AES128-GCM-SHA256:TLSv1.2:Kx=ECDH:Au=RSA:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username stefan@olimex.com, mechanism PLAIN) for ; Tue, 5 Feb 2019 22:06:13 -0800 Subject: Re: [PATCH 5/5] arm: dts: axpxx: add charge led node To: Chen-Yu Tsai , Stefan Mavrodiev Cc: Rob Herring , Mark Rutland , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "open list:X-POWERS MULTIFUNCTION PMIC DEVICE DRIVERS" References: <20190131082308.22522-1-stefan@olimex.com> <20190131082308.22522-5-stefan@olimex.com> From: Stefan Mavrodiev Message-ID: <4493d1cb-d1bb-bcc9-c37d-68c79f33e762@olimex.com> Date: Wed, 6 Feb 2019 08:06:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/5/19 6:16 PM, Chen-Yu Tsai wrote: > On Thu, Jan 31, 2019 at 4:25 PM Stefan Mavrodiev wrote: >> Add dt node for axp20x-led driver controlling CHGLED. >> Default status is disabled, since it may be not used. >> >> Signed-off-by: Stefan Mavrodiev > Please include a cover letter for such a patch series. Sorry, I will. > > Also, do any boards actually use this? I know the Pine64 does, but the > LED is left to the user to populate. I would really like to have an in > kernel user of this function, so that we can verify it. All boards made by Olimex has this led populated. The development and the testing of the driver was done on A64-OLinuXino board. Should I make another patch, enabling the LED for the mention board? Best regards, Stefan Mavrodiev > > ChenYu > >> --- >> arch/arm/boot/dts/axp209.dtsi | 5 +++++ >> arch/arm/boot/dts/axp22x.dtsi | 5 +++++ >> arch/arm/boot/dts/axp81x.dtsi | 5 +++++ >> 3 files changed, 15 insertions(+) >> >> diff --git a/arch/arm/boot/dts/axp209.dtsi b/arch/arm/boot/dts/axp209.dtsi >> index 0d9ff12bdf28..f972b6f3ecd0 100644 >> --- a/arch/arm/boot/dts/axp209.dtsi >> +++ b/arch/arm/boot/dts/axp209.dtsi >> @@ -69,6 +69,11 @@ >> #gpio-cells = <2>; >> }; >> >> + axp_led: led { >> + compatible = "x-powers,axp20x-led"; >> + status = "disabled"; >> + }; >> + >> battery_power_supply: battery-power-supply { >> compatible = "x-powers,axp209-battery-power-supply"; >> status = "disabled"; >> diff --git a/arch/arm/boot/dts/axp22x.dtsi b/arch/arm/boot/dts/axp22x.dtsi >> index 65a07a67aca9..92a0b64252b1 100644 >> --- a/arch/arm/boot/dts/axp22x.dtsi >> +++ b/arch/arm/boot/dts/axp22x.dtsi >> @@ -62,6 +62,11 @@ >> #io-channel-cells = <1>; >> }; >> >> + axp_led: led { >> + compatible = "x-powers,axp20x-led"; >> + status = "disabled"; >> + }; >> + >> battery_power_supply: battery-power-supply { >> compatible = "x-powers,axp221-battery-power-supply"; >> status = "disabled"; >> diff --git a/arch/arm/boot/dts/axp81x.dtsi b/arch/arm/boot/dts/axp81x.dtsi >> index bd83962d3627..22e243cc40d5 100644 >> --- a/arch/arm/boot/dts/axp81x.dtsi >> +++ b/arch/arm/boot/dts/axp81x.dtsi >> @@ -74,6 +74,11 @@ >> }; >> }; >> >> + axp_led: led { >> + compatible = "x-powers,axp20x-led"; >> + status = "disabled"; >> + }; >> + >> battery_power_supply: battery-power-supply { >> compatible = "x-powers,axp813-battery-power-supply"; >> status = "disabled"; >> -- >> 2.17.1 >>