Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2137596pxb; Thu, 28 Oct 2021 17:13:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJysrNj1JvCufXpgqcGGFu9OtQSNS6lYMcGe6Lhf3mvwNrGMehVFVi4jsvfFaq8L32HJGF8m X-Received: by 2002:a17:902:9b8d:b0:13e:b693:c23d with SMTP id y13-20020a1709029b8d00b0013eb693c23dmr6851764plp.11.1635466436224; Thu, 28 Oct 2021 17:13:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635466436; cv=none; d=google.com; s=arc-20160816; b=FO5YdLogZbKArkCu/O7pfoCDEeyw5OCEMfdUNN7dnPCnjIIImXjXmFQuk1kPyKbXdE 0zCu0fVSOeEGpgljn1ymMoofmZ3KR8yG2iKTCax+F1li2f5pL6aS/MjFJa2DBgmZoFKk bDibv7y6j+ivF09kqWOK8NdFUUaKCBPhz5j9K8HC3vM8wPdDlayVtJWwqoxmq0OGHqJf VXZzaE4FUhgGs0kCiWaIlpU6buK5uAsqkpgVTbpmLeUVUruYXHtU3qLP21i6BemWkUQB HXt+C8fhSML7rR0xiRxgeKThOd/C2JWe4GqVPZtq09Zw7AEjvhg6k2TuAy4Qs1qTgfBw Lp5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=Ke1RR/yh2Lw9wS2LgxkSgK8p4zl57sqmHmt240T7mE8=; b=IbUC2knvZ4I6dUH/UZrbjRD15e9M0EcQ7mQIW7lpHWz6W6vfpKwCK2IvtvnfaT+dwx oauCsl7NUDdu2tevSHY54mfAB/EkMDQSI5whMlUKHiQbUxmHjCW7Dzq8xIeQapQEndtD ZZrRXKNkdNNdM1GkXMO5yTI0zMI3SkaotJXcZg4pDBjn3Rw0nwJPNJmsWfeR9tQhM/Y4 gtZDZEPYpto1xrnGau5GnFRWiMydjmXOR1ODdb4G83yXJ6WCxWhGzDyc9nqr/2eRq/lq 3RhsqW4q/dfTaxtJDscGHeAVuiRmJ76JttN1VIdIxIXfBi6DY9rRITyRnX6LZPT6+/7W 0PHQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U4Ap5AYi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id q5si6863326pgg.304.2021.10.28.17.13.43; Thu, 28 Oct 2021 17:13:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=U4Ap5AYi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231217AbhJ2ALP (ORCPT + 99 others); Thu, 28 Oct 2021 20:11:15 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:53379 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230249AbhJ2ALO (ORCPT ); Thu, 28 Oct 2021 20:11:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635466127; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Ke1RR/yh2Lw9wS2LgxkSgK8p4zl57sqmHmt240T7mE8=; b=U4Ap5AYi7GusgbktA31XyOtBNCOK35ZdMtRWH+G+1NM4UrOcT5d9dizCl6QdNaiiTsShem 718emubJrfrkuJRwPRFGm/m8WY1TcsbJyErQu8ZqhEgMLTe7JRdu7cIuU7JI9BCUy59N3D 2N7l8JbpZKEdKdEh4yA1Hm4pMLRF7DI= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-458-n010S_1qMTaAWX8z4ZhYSw-1; Thu, 28 Oct 2021 20:08:45 -0400 X-MC-Unique: n010S_1qMTaAWX8z4ZhYSw-1 Received: by mail-qt1-f198.google.com with SMTP id x28-20020ac8701c000000b0029f4b940566so5595476qtm.19 for ; Thu, 28 Oct 2021 17:08:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ke1RR/yh2Lw9wS2LgxkSgK8p4zl57sqmHmt240T7mE8=; b=H5OZ4gg1oqh9Amp6mvhF3nfU9A8zddiynZOm2iWBFB7ecBBZuXtBpGRyxog2QplySh Nc6GSea/9QqmJBv+ios9K8xmmW1XTukLWFZSbA/x/mUg07iN9m4o9zGPMvDLqOuPSA82 fii1gzQh7+fbh3IMsdA1dxlH2IwA2MpzmBnMOVBgjf7Ernhcr3+wGeemMzBe9s52VBL5 2YyZgzLVB4djWeRI0w7rkat1Do7vMmS9b4wmj+OubOWtBhb/k3oIiNlRuWiBoq9CJaCW Knnp4psN5WPwQ/bBNLB1zyoFlrjg4sO5fK5OhpuTp4CKJNNOXNjnbC/1dDudqr4bMg3P fUtA== X-Gm-Message-State: AOAM531BqjBvIAYud1xxUy/7x2v4uZ4480Fgy6l74283lOkJXTjbiZK1 2x9T3XfaIHX8RfQz5HDcjs2UBL9ZuHAcm5FlB6VIgysZoRALl5pa4zEkkF2rUJlJ+GpVcQEwVwI 9aeif/qNm45LLn90vMUaryFxitWE9fW2A5P9FCRps X-Received: by 2002:a05:6214:2608:: with SMTP id gu8mr3538039qvb.18.1635466124339; Thu, 28 Oct 2021 17:08:44 -0700 (PDT) X-Received: by 2002:a05:6214:2608:: with SMTP id gu8mr3538003qvb.18.1635466123884; Thu, 28 Oct 2021 17:08:43 -0700 (PDT) MIME-Version: 1.0 References: <20211020095926.735938-1-flokli@flokli.de> In-Reply-To: <20211020095926.735938-1-flokli@flokli.de> From: Dennis Gilmore Date: Thu, 28 Oct 2021 19:08:32 -0500 Message-ID: Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Enable HDD power on helios64 To: Florian Klink Cc: Heiko Stuebner , Aditya Prayoga , Rob Herring , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM/Rockchip SoC support" , linux-rockchip@lists.infradead.org, open list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tested-by: Dennis Gilmore On Thu, Oct 28, 2021 at 11:37 AM Florian Klink wrote: > > This adds the hdd_{a,b}_power blocks present in the armbian helios64 > dts. [1] > > Without those powered up, no HDDs will appear (except one connected via > the m.2 slot). > > From https://wiki.kobol.io/helios64/sata/#hdd-power: > > > The power delivery of the HDDs is divided into two group: > > > > HDD Rail A (Max. 3x Drives) > > HDD Rail B (Max. 2x Drives) > > > > Helios64 implements a power staggering approach where HDD Rail A will be > > powered up first, then few seconds later HDD Rail B will be powered up. > > This power control scenario is performed to reduce the inrush current > > during disk spin-up. > > In practice, this power staggering approach will be included in the > bootloader (not in the kernel), as we might want to boot from a SATA > drive. > > From my experiments, if the bootloader doesn't implement the power > staggering, only one HDD will get recognized (probably cause the others > didn't boot due to few power). > > Still, it makes sense to expose this block in the device-tree, so the > kernel can ensure both rails are on (and this can be shared with > u-boot). > > [1] https://github.com/armbian/build/blob/744ea89a589d62cb6f409baab60fc6664520bc39/patch/kernel/archive/rockchip64-5.14/add-board-helios64.patch > > Signed-off-by: Florian Klink > --- > .../dts/rockchip/rk3399-kobol-helios64.dts | 32 +++++++++++++++++++ > 1 file changed, 32 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts b/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts > index 738cfd21df3e..93745dcc2af6 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts > +++ b/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts > @@ -82,6 +82,30 @@ led-1 { > }; > }; > > + hdd_a_power: hdd-a-power { > + compatible = "regulator-fixed"; > + enable-active-high; > + gpio = <&gpio1 RK_PA0 GPIO_ACTIVE_HIGH>; > + pinctrl-0 = <&hdd_a_power_en>; > + pinctrl-names = "default"; > + regulator-always-on; > + regulator-boot-on; > + regulator-name = "hdd_a_power"; > + startup-delay-us = <2000000>; > + }; > + > + hdd_b_power: hdd-b-power { > + compatible = "regulator-fixed"; > + enable-active-high; > + gpio = <&gpio1 RK_PA1 GPIO_ACTIVE_HIGH>; > + pinctrl-0 = <&hdd_b_power_en>; > + pinctrl-names = "default"; > + regulator-always-on; > + regulator-boot-on; > + regulator-name = "hdd_b_power"; > + startup-delay-us = <2000000>; > + }; > + > pcie_power: pcie-power { > compatible = "regulator-fixed"; > enable-active-high; > @@ -422,6 +446,14 @@ pmic_int_l: pmic-int-l { > }; > > power { > + hdd_a_power_en: hdd-a-power-en { > + rockchip,pins = <1 RK_PA0 RK_FUNC_GPIO &pcfg_pull_none>; > + }; > + > + hdd_b_power_en: hdd-b-power-en { > + rockchip,pins = <1 RK_PA1 RK_FUNC_GPIO &pcfg_pull_none>; > + }; > + > vcc5v0_usb_en: vcc5v0-usb-en { > rockchip,pins = <1 RK_PC6 RK_FUNC_GPIO &pcfg_pull_none>; > }; > -- > 2.33.0 > -- Dennis Gilmore Multiple Architecture Portfolio Enablement T: +1-312-660-3523