Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp884459rdb; Fri, 22 Dec 2023 07:49:37 -0800 (PST) X-Google-Smtp-Source: AGHT+IEaOXFt4UNc1dXs5vbg4sAx/mh9jKHrradC/PUlcTZK6Bb7TDO7XksOIXXNyCLSKerIkZaW X-Received: by 2002:a62:ab0f:0:b0:6ce:2731:47bd with SMTP id p15-20020a62ab0f000000b006ce273147bdmr1981060pff.29.1703260176712; Fri, 22 Dec 2023 07:49:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703260176; cv=none; d=google.com; s=arc-20160816; b=R9IdG9T331iuzcxET4R6QXU6LemqK7TrFjD/PgxEGxASTe172tTHBmfvB7bozExhJ2 CtBcam8p61KOcEOsrHbZxsJFAE59cRscng9xhWtj3cMK90HXycxCoWMDe1hojOzkg+po t/2niCGgRynYjQ2PSBYm0I8ZY8YGKwNGaNLaazNfaOCsDLD0jI7QmBm0PWf171R+9lfF NemWvp4ECB2aGYz1stmEeUbNBsmXTUL/CcaWTRBwqIlqRAXU6NL/IDqkw4p/nR3sHfYp bEKN0R7G1kM0HtieaR5pXJ4QQ+2N66DztSO6nu2qIn1aKKUGDONF+zEVlCdFMGYxXH6b j2UQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=Ef32YElP2BbDQz2dK/HFsBjNQE4fPIX1yJrkUy0kFpM=; fh=c0Ot37klKxp4Przplm9csdEIIibHggmFz6bNAbWZLRk=; b=Lt6Jxhq8n2Tcn9UUp6x7MfDg/LeNNL12JPwbhOorYEjGHJnHdhmQEByyfYJu2EPEn7 8Ppq25TinXbGq87refNvKwokjoA8rpd/nrbKnOrMQNtibsSexKK8nUoD4cJGAGxJ8dlm L3bwUk44mMrJBlFk0yju8FVslC0KqYFwopOtqudxzaRgRu8QVlj5g/QF5STE+7sHyl98 GlLy/ks7WWnaBnESLqzt3DMwdy2EtNQNbnzBkD3wrri9RRk3qs/uuo35lQdSbbG29wKd GlHUyGanmxb6+/wUlhYQyKJjzm8UY7o2A+v1g64sbAeDAGl9pkRgzKDmaqXTQEuD2Ijc SscQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=VlDxRxG5; spf=pass (google.com: domain of linux-kernel+bounces-9854-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9854-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id a21-20020a62e215000000b006d28370354esi3411854pfi.262.2023.12.22.07.49.36 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Dec 2023 07:49:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-9854-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=VlDxRxG5; spf=pass (google.com: domain of linux-kernel+bounces-9854-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-kernel+bounces-9854-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id E5B2B286688 for ; Fri, 22 Dec 2023 15:49:33 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id E0FAE241EA; Fri, 22 Dec 2023 15:49:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="VlDxRxG5" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 17ED423765; Fri, 22 Dec 2023 15:49:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A6B0AC433C7; Fri, 22 Dec 2023 15:49:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703260162; bh=Ag0mzWcsnW1g3n91UWrk0/4qwvTZgSOiJlVaZYR4sxk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=VlDxRxG5wy4qKpfb3iXAPj2Uc6r15R51pEALVoOguck+w7rxTUgs1Xgby3rJZNH4X aie0n5cySZhL8SQ0JI70Zn4Jeexb+FDiM52jtiZqhjvg6LvIDcmcg29wi4eem6TTdD P50+IEjlxIsiOcm9fcWgSSzDH7PJUBusRPKGFbWNr4gISpI+/bmuMHTreF5WTcVIrm pIrpZVrkAQdSsebQ9W90K6cHkkF0JHyjU3EXoteXRH2y3Ei+iPCWckqgI6NaSPbvro vXNQTvmHG14Uw6zVmpqGD25Rg4sL+c0jd52jqN2lvzDHXbQiC0xPq8l2pznqs+GUg2 HoSzyldwEOq+w== Date: Fri, 22 Dec 2023 21:19:18 +0530 From: Vinod Koul To: Can Guo Cc: bvanassche@acm.org, mani@kernel.org, adrian.hunter@intel.com, beanhuo@micron.com, avri.altman@wdc.com, junwoo80.lee@samsung.com, martin.petersen@oracle.com, linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org, Andy Gross , Bjorn Andersson , Konrad Dybcio , Kishon Vijay Abraham I , Dmitry Baryshkov , Abel Vesa , Johan Hovold , "open list:GENERIC PHY FRAMEWORK" , open list Subject: Re: [PATCH v8 09/10] phy: qualcomm: phy-qcom-qmp-ufs: Rectify SM8550 UFS HS-G4 PHY Settings Message-ID: References: <1701520577-31163-1-git-send-email-quic_cang@quicinc.com> <1701520577-31163-10-git-send-email-quic_cang@quicinc.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On 22-12-23, 15:41, Can Guo wrote: > Hi Vinod, > > On 12/22/2023 1:13 AM, Vinod Koul wrote: > > On 02-12-23, 04:36, Can Guo wrote: > > > The registers, which are being touched in current SM8550 UFS PHY settings, > > > and the values being programmed are mainly the ones working for HS-G4 mode, > > > meanwhile, there are also a few ones somehow taken from HS-G5 PHY settings. > > > However, even consider HS-G4 mode only, some of them are incorrect and some > > > are missing. Rectify the HS-G4 PHY settings by strictly aligning with the > > > SM8550 UFS PHY Hardware Programming Guide suggested HS-G4 PHY settings. > > > > This fails for me, as I have picked Abels offset series, can you please > > rebase these two patches and send > > > In v8, I rebased the two changes to linux-next. Is the ask there to rebase > the two changes to phy/next? Yes these two failed to apply for me, pls rebase and post -- ~Vinod