From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9DF48C3DA79 for ; Mon, 26 Dec 2022 15:10:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229581AbiLZPKi (ORCPT ); Mon, 26 Dec 2022 10:10:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229496AbiLZPKh (ORCPT ); Mon, 26 Dec 2022 10:10:37 -0500 Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEBBDC05 for ; Mon, 26 Dec 2022 07:10:35 -0800 (PST) Received: by mail-lf1-x129.google.com with SMTP id bp15so16208944lfb.13 for ; Mon, 26 Dec 2022 07:10:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=7/4vIavePf24Y5E57dKW/d4hKpsKl8TaQWv7+5+2RYA=; b=uU4NHW77ug4oYnSdjBRbFvuzXnFN63F8yeG9pj6NH7aJVhTbS4e7dxcFGCN8HHZVM1 V65lyagghCGGJ3HVjxvAavDeGCMx5HvZ0AJn8hf6DtzlkDMl+gTXKKHalhydWZrJn2M5 ehW6YjmbvfgbxTDEQYwxVpS/qYb3Bn2lFodjt4AtEBBgh0rFkhu4sderjj/o85npV6n0 hEoJcKCFLBDIqz7d6M6h+56FFDhaQ7HWnb/tZ8m6muhQzVsatdNaz+maDwwuKqInKOeo AJJuWfDEQapXrp7uYwlypWbZm2IA9OVRJTzoN62ESBfi0KqLnLOnun5XnU6evA471Oyq glRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7/4vIavePf24Y5E57dKW/d4hKpsKl8TaQWv7+5+2RYA=; b=EObB9m8vx/YpsjwizdsJtjDMvvnBFMAxGhLKnIEquIXFE7XyV53p0PsnoVaDqkgI0j hTOPj00xmQswJ083C8hGPjQgbkFSjBEfEKgBYpIullbPy5tuUfJmR9vtRUZGRZNmV/w3 rCWe7AHObxq3YMcq3hZyXgaeeOD5+UN5VTef3uHMnc3ncO1HT3VAoSJbcmTDPXc2zwm2 IzK1absaLB9HRDi8tDIDbEv6wSfpZDqP6CfWxElLtUjhyqxYzF57eZhySsyeWmNCfHQr 2DtxtyiRmLikiLOkhPyR+hvoHg4m5fGdci2CxdHrlowLYIYfBvtvc7vUBgKpT7xPP9KZ o7LQ== X-Gm-Message-State: AFqh2kqQeUJ3WdjL8pMptaK44Fk7Pyp5QY9woGW3fWFqbBfarGcMmsor aTtr+Y17DjVkoHsA1+2KKUT81g== X-Google-Smtp-Source: AMrXdXsU88kmLp0G5KL5khCv7pOiaZv4YSBEkD5kb5OBp7DxQ2BF4lkzmUlTHHQIaUMmgUmLWPo+Cg== X-Received: by 2002:a05:6512:3e24:b0:4cb:c11:d01f with SMTP id i36-20020a0565123e2400b004cb0c11d01fmr455333lfv.22.1672067434220; Mon, 26 Dec 2022 07:10:34 -0800 (PST) Received: from [192.168.0.20] (088156142067.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.67]) by smtp.gmail.com with ESMTPSA id v21-20020ac258f5000000b004cb09fd48ebsm370872lfo.149.2022.12.26.07.10.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Dec 2022 07:10:33 -0800 (PST) Message-ID: Date: Mon, 26 Dec 2022 16:10:32 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH] arm64: dts: fsd: fix PUD values as per FSD HW UM To: Padmanabhan Rajanbabu , robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org, alim.akhtar@samsung.com, s.prashar@samsung.com, pankaj.dubey@samsung.com Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20221129095516.89132-1-p.rajanbabu@samsung.com> Content-Language: en-US From: Krzysztof Kozlowski In-Reply-To: <20221129095516.89132-1-p.rajanbabu@samsung.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 29/11/2022 10:55, Padmanabhan Rajanbabu wrote: > PUD values used for UFS, SPI and UART are not reflecting > the default values recommended by FSD HW UM. Therefore, > changing the same to comply with HW UM recommendation. > > Signed-off-by: Padmanabhan Rajanbabu > --- > arch/arm64/boot/dts/tesla/fsd-pinctrl.dtsi | 14 +++++++------- This patch does not apply, please rebase on my for-next or linux-next (once released). Best regards, Krzysztof