Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp262548rwb; Tue, 25 Jul 2023 15:37:28 -0700 (PDT) X-Google-Smtp-Source: APBJJlGckxmMGdtZbh0BZu4H4k9RTuBYafuJCH+PIDNJBYBqc3zLF2NL6FwPwzIMtJpXCnb9N/GV X-Received: by 2002:a05:6358:2920:b0:132:dc58:b372 with SMTP id y32-20020a056358292000b00132dc58b372mr88135rwb.19.1690324648017; Tue, 25 Jul 2023 15:37:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690324647; cv=none; d=google.com; s=arc-20160816; b=lHP91Oax7vXfFZRDrBfk3IK9ZRIBkw5obdFrY/cqQDYHNtv6vnAH9BrrogRqpKglc+ gxDjasgIFR47Hi+T3pQfy+IaerLzEhcv88XQQnqcosOh3SD8Du5HqaepUjYH4S5CWQJ8 RaUl4dNgivECZNKCOQX1PsYMhDSRfzroEYgfls+ecovz7D67geFl/DbgSikVIaeQfAmz wxpcbBRadVTT23erg9N2u8BiJrOlEYaRmIfxLED1F2p4nSnp4tdKAM+3qsGAbdzBFqd8 aYPvhuaxEfWV78WOpLI9Vq7MgSOI4CttIft74VZ9wcw/AdvhPW/pSvoTXKCUzIpDmMFx TOEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=Melm6/J1BB5km5pizgjvl9Yb8xIN/1Veuqiikhv3KRo=; fh=kTp50MLoHM7d8OzhAirEnklwgfJypXcCehjhMFHxR9U=; b=ZVHe/fXp1kIF3cMpM2sROS6uVL4+QmboV0YWLJ49n7mKfnjGRqJBtemHFozje58tKd gFQWkL9IQR9Tk4QyzJa0diIu2udoQk0pk8ZI3ZIJypDcPyqmjB2gHXID+yslqm7I/9xv jqMqhRT68Uvw0APoTdmNeb0fS2hcOC60eTFCjIwmFKbGyoo1TQXDo25PMOwhQwU27kDY KAP4UG4kZSUJZSKXAvfFuSgE4IQ3wpzwjRw/a1otaCjEagbdWuSqhtOUwLLTE/P0X2Ts x00KGe7FlbnjHfLPXVruf+7RLnza3WDQlOrmuZkbnrFb+/YygvC6t6DXkpR5UuRy2I26 mUdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EmZ4uDqe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s25-20020a63af59000000b005409058c8d7si10558830pgo.126.2023.07.25.15.37.14; Tue, 25 Jul 2023 15:37:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=EmZ4uDqe; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S230043AbjGYVvo (ORCPT + 99 others); Tue, 25 Jul 2023 17:51:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42154 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229929AbjGYVvm (ORCPT ); Tue, 25 Jul 2023 17:51:42 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A2592127 for ; Tue, 25 Jul 2023 14:50:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1690321854; 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=Melm6/J1BB5km5pizgjvl9Yb8xIN/1Veuqiikhv3KRo=; b=EmZ4uDqezYqZCmUJozcqVQZCLAZnNsK3LRMK0hRDqVcN5AcZwp4IuYT6t3A+K4V+7nypSs hk47kl4z+PEgwq7+rqkqy77H4I+0vb+/aAKUxQmPvacc323UbdBqX643FmYMeg6LVCqGbZ Fe/1BLwffgyCl46fmC7JlcmhviU3iSQ= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-580-yIYbU35XMj6JLXS5iV6YoQ-1; Tue, 25 Jul 2023 17:50:53 -0400 X-MC-Unique: yIYbU35XMj6JLXS5iV6YoQ-1 Received: by mail-qk1-f200.google.com with SMTP id af79cd13be357-7683cdabcb7so810045985a.3 for ; Tue, 25 Jul 2023 14:50:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690321852; x=1690926652; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Melm6/J1BB5km5pizgjvl9Yb8xIN/1Veuqiikhv3KRo=; b=bG5drsXA9gNhoH0aqnD3ILE5/DwD+1We8OkYieFFRsJVuDI230nQmFXTkH9KHnvYEY j3OelOW2H/KQpw2D6TsPHFT6jIyQj+qSmmQWPiFBoK4Z0tGxhaAuSlkeR9D3b5QbaSjI 0CENd7j4nbuX+r2VVSoQFCG0ccFC58fGyjS+52iaFhmOMslQ+9ySUkXRbdmfUtpdK1sv VZUXnOfjWN+fr43CUjrasVfJlAlYzZ9Pq3PwEsZWaMlXE3bSeeJbsDn6ZQtdv6mmmYpi gtmi1s600+Nvlip0u0G87TwiGRaXsPlpoK4WwfbFVBKd82xJdWvEk/xaDVxKbHPh5c+L yvoA== X-Gm-Message-State: ABy/qLaL14MY7yzL2DCKFRGOp6y4iroAHwLYd8ZZYbgugtSUjbxwBZgi Z9QwqYPUAFBnGka0qaRusXZSGsvaPpwgUAqsKA+3iNHnvFgKm1rCV7Vp3LqlTYywm0smBjcE3cj EmGN3mK+azgvUnHtb5X5Y8YTj X-Received: by 2002:a37:9387:0:b0:768:75c:a323 with SMTP id v129-20020a379387000000b00768075ca323mr189186qkd.30.1690321852561; Tue, 25 Jul 2023 14:50:52 -0700 (PDT) X-Received: by 2002:a37:9387:0:b0:768:75c:a323 with SMTP id v129-20020a379387000000b00768075ca323mr189174qkd.30.1690321852320; Tue, 25 Jul 2023 14:50:52 -0700 (PDT) Received: from fedora ([2600:1700:1ff0:d0e0::17]) by smtp.gmail.com with ESMTPSA id q29-20020a05620a039d00b00767177a5bebsm3909301qkm.56.2023.07.25.14.50.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Jul 2023 14:50:51 -0700 (PDT) Date: Tue, 25 Jul 2023 16:50:49 -0500 From: Andrew Halaney To: Naveen Kumar Goud Arepalli Cc: quic_nitirawa@quicinc.com, agross@kernel.org, andersson@kernel.org, konrad.dybcio@linaro.org, robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V1] arm64: dts: qcom: sa8775p-ride: Remove min and max voltages for L8A Message-ID: References: <20230725100007.14775-1-quic_narepall@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230725100007.14775-1-quic_narepall@quicinc.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 25, 2023 at 03:30:07PM +0530, Naveen Kumar Goud Arepalli wrote: > L8A is the supply for UFS VCC, UFS specification allows different VCC > configurations for UFS devices. > -UFS 2.x devices: 2.70V - 3.60V > -UFS 3.x devices: 2.40V - 2.70V > > As sa8775p-ride supports both ufs 2.x and ufs 3.x devices, remove min/max > voltages for L8A regulator. Initial voltage of L8A will be set to 2.504v > or 2.952v during PON depending on the UFS device type. On sa8775, UFS is > the only client in Linux for L8A and this regulator will be voted only > for enabling/disabling. > > Signed-off-by: Naveen Kumar Goud Arepalli > --- > arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts > index ed76680410b4..6f3891a09e59 100644 > --- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts > +++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts > @@ -98,8 +98,6 @@ > > vreg_l8a: ldo8 { > regulator-name = "vreg_l8a"; > - regulator-min-microvolt = <2504000>; > - regulator-max-microvolt = <3300000>; > regulator-initial-mode = ; > regulator-allow-set-load; > regulator-allowed-modes = -- > 2.17.1 > Reviewing with very little expertise in the area.... A few questions below that would help me understand this a bit better. Does it make sense to *not* set the range of the regulator at all?: 1. A board dts knows its UFS device 2. Is UFS backwards compatible with respect to UFS2/UFS3? I don't know how the version is determined, but if it's a "start at UFS2, go to UFS3" should it be scaled as that goes? Relying on the bootloader to set up the device before the kernel starts seems like a direction that should be actively avoided instead of depended on in my opinion. Thanks, Andrew