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 535C7C433FE for ; Fri, 14 Jan 2022 07:49:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233954AbiANHto (ORCPT ); Fri, 14 Jan 2022 02:49:44 -0500 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]:60754 "EHLO smtp-relay-internal-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233851AbiANHtk (ORCPT ); Fri, 14 Jan 2022 02:49:40 -0500 Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 3F3693F1EA for ; Fri, 14 Jan 2022 07:49:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1642146578; bh=OfGvrCtC8xlimA6cEB+wdrguTqUYJCj+ZRy5BPwVdRo=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=L/EgHIHbJdR8oHWtWf3LqUEgvfA86riHomk6b0iBFStDGkxfG35H4H8dfnBR6Pq1u INQ6IFWKTdyK5FMN+okz3qQBFsUaSeHBHMpoMqKzoli09WvF9UkQumFydLHHF6Od4k pF98S5YJNr247xBtWqrvVJqrb6ZTVb5GBdixRTxk5+b8bTx8gvFKq94FQmxpLm80zi jerHUaDo4MSiiKPlecMiFK+w+Q/wYbZtKT3B9NUGhomgiNyUotRLWEg8FRhP2Zw4dE p7ZDEaBsfWnezruJmFKcnuBn0c45mHEVIZTqBIP32XVUCC7+tVxiXfYGFaHOEb73vC XpEFBO1mNuFqQ== Received: by mail-ed1-f72.google.com with SMTP id z10-20020a05640235ca00b003f8efab3342so7655736edc.2 for ; Thu, 13 Jan 2022 23:49:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=OfGvrCtC8xlimA6cEB+wdrguTqUYJCj+ZRy5BPwVdRo=; b=07AKkChkWPa6A0KK18rffHza/IeqIw03HCZ2qxWGyBkreK//hCdo4ed5beVHLk9tWs iuO4IeTEv/+og5jQn79VAeNJ/yusKlOS2GZDRLpI75OfXpKD2ZwklFzyMKcrovbP+iAx yUOT5LiU1XFGAsheSPPHHn/qdoFtCVh8Y+SJ9gzxkdFRS6MdHj6ky9FiGE4+WEFk3Fc4 zZGraegPK67GjM3LljpTe4QFueyQpzkE26V/h7xj9FXsrBYFjvPW38eiUoMP21VQa6jS p6J68ZCNmsMIyfKKQEBMiCv6WrtKlUzimOyE50/5M9xlwRPn+63hbpcHNd0LxiV8DU6T Wrqw== X-Gm-Message-State: AOAM5322lV1FdGC2NVj62LOhJX38CjzYmmOhoO79DMtfqHgnh6+zB4UJ f1WOmwZ1qn5GWL+/kskGio/xxxUNEpjvVaWLCdxG/H5Ehd/5W6+c17ehhGXC+VmYw0rFVQXb1Nw mlmemgGh8e1Nb49XV9cKhtNOAGM6FVhwndhgZxHx1Zg== X-Received: by 2002:a05:6402:2685:: with SMTP id w5mr7710425edd.151.1642146578014; Thu, 13 Jan 2022 23:49:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJx28rjBXLGcKe6hIBmUk/lmPK/ygVLWajiItPMzl6kJqav/dcWM9ZuCOshtlFa/+UuDpfMTkw== X-Received: by 2002:a05:6402:2685:: with SMTP id w5mr7710414edd.151.1642146577885; Thu, 13 Jan 2022 23:49:37 -0800 (PST) Received: from [192.168.0.30] (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id jg41sm1602954ejc.101.2022.01.13.23.49.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Jan 2022 23:49:37 -0800 (PST) Message-ID: <65e6f034-278a-81fa-844d-10a1865a25a4@canonical.com> Date: Fri, 14 Jan 2022 08:49:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.1 Subject: Re: [PATCH 10/23] dt-bindings: pinctrl: samsung: Add compatible for Tesla FSD SoC Content-Language: en-US To: Alim Akhtar , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: soc@kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, olof@lixom.net, linus.walleij@linaro.org, catalin.marinas@arm.com, robh+dt@kernel.org, s.nawrocki@samsung.com, linux-samsung-soc@vger.kernel.org, pankaj.dubey@samsung.com, linux-fsd@tesla.com References: <20220113121143.22280-1-alim.akhtar@samsung.com> <20220113121143.22280-11-alim.akhtar@samsung.com> <849c7772-0f7e-32ff-6ea6-c46aa6837bb4@canonical.com> <076101d80909$d5849060$808db120$@samsung.com> From: Krzysztof Kozlowski In-Reply-To: <076101d80909$d5849060$808db120$@samsung.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14/01/2022 06:44, Alim Akhtar wrote: > > >> -----Original Message----- >> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@canonical.com] >> Sent: Thursday, January 13, 2022 5:57 PM >> To: Alim Akhtar ; linux-arm- >> kernel@lists.infradead.org; linux-kernel@vger.kernel.org >> Cc: soc@kernel.org; linux-clk@vger.kernel.org; devicetree@vger.kernel.org; >> olof@lixom.net; linus.walleij@linaro.org; catalin.marinas@arm.com; >> robh+dt@kernel.org; s.nawrocki@samsung.com; linux-samsung- >> soc@vger.kernel.org; pankaj.dubey@samsung.com; linux-fsd@tesla.com >> Subject: Re: [PATCH 10/23] dt-bindings: pinctrl: samsung: Add compatible for >> Tesla FSD SoC >> >> On 13/01/2022 13:11, Alim Akhtar wrote: >>> Add compatible for Tesla Full Self-Driving SoC. The pinctrl hardware >>> IP is similar to what found on most of the exynos series of SoC, so >>> this new compatible is added in samsung pinctrl binding. >>> >>> Cc: linux-fsd@tesla.com >>> Signed-off-by: Alim Akhtar >>> --- >>> Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git >>> a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> index b8b475967ff9..ba972998a0e4 100644 >>> --- a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> +++ b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> @@ -24,6 +24,7 @@ Required Properties: >>> - "samsung,exynos7-pinctrl": for Exynos7 compatible pin-controller. >>> - "samsung,exynos850-pinctrl": for Exynos850 compatible pin-controller. >>> - "samsung,exynosautov9-pinctrl": for ExynosAutov9 compatible pin- >> controller. >>> + - "tesla,fsd-pinctrl": for Tesla FSD SoC compatible pin-controller. >>> >> >> Please rebase this on my latest Samsung pinctrl dtschema patches. You also >> need a tesla vendor prefix patch (separate). >> > Sure will rebase when sending v2, your latest patches are in Linux-next or still in your tree? The SPI (v3) and pinctrl (v2) dtschema patches are on mailing lists. They seem to be done, so after merge window they will make to linux-next. If you want earlier, grab them from mailing list or from branches: https://github.com/krzk/linux/tree/n/dt-bindings-samsung-spi-schema-v3 https://github.com/krzk/linux/tree/n/dt-bindings-samsung-pinctrl-schema-v2 Best regards, Krzysztof 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 209EEC433EF for ; Fri, 14 Jan 2022 07:51:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=+dIcSM4UcZst3XJm2JdjXvsi5dGIoCUPhLB/BTUckws=; b=lhftSBZlAMzFPD yZ5CgJSJEBHm6SALhWWVuNrQlG4ouSUWBIOsGHa9oeNMan/X2og1XOCL274TDvsW5sJ/CH4nSKhSE WbKUfw2tE3jgGpP/XhEr/7q3Qj3twgr9OruDqB8vc3NdrPG/s5GbnH4eMZ8zduRyijttrRdp2Vk+T 2BoAG8OYGyTQfm9+Go2O2q3qw4XTK/icCt2r2AacsM+lxxxBvN2NwbKlU9RfdMD01PJ8xlIR8dp/w GhGXuhjmfkiO3uRXKxyYonDLWnDIAXTbd2BdSRb5L+9708XKw05UvoIs9SI9alT+fedo5ZyNL39L2 EAYT7VtsE0JFNk9Bij/Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n8HLL-0087AQ-7D; Fri, 14 Jan 2022 07:49:51 +0000 Received: from smtp-relay-internal-0.canonical.com ([185.125.188.122]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n8HLI-00879O-6i for linux-arm-kernel@lists.infradead.org; Fri, 14 Jan 2022 07:49:49 +0000 Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id 6A897402A5 for ; Fri, 14 Jan 2022 07:49:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1642146578; bh=OfGvrCtC8xlimA6cEB+wdrguTqUYJCj+ZRy5BPwVdRo=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=L/EgHIHbJdR8oHWtWf3LqUEgvfA86riHomk6b0iBFStDGkxfG35H4H8dfnBR6Pq1u INQ6IFWKTdyK5FMN+okz3qQBFsUaSeHBHMpoMqKzoli09WvF9UkQumFydLHHF6Od4k pF98S5YJNr247xBtWqrvVJqrb6ZTVb5GBdixRTxk5+b8bTx8gvFKq94FQmxpLm80zi jerHUaDo4MSiiKPlecMiFK+w+Q/wYbZtKT3B9NUGhomgiNyUotRLWEg8FRhP2Zw4dE p7ZDEaBsfWnezruJmFKcnuBn0c45mHEVIZTqBIP32XVUCC7+tVxiXfYGFaHOEb73vC XpEFBO1mNuFqQ== Received: by mail-ed1-f70.google.com with SMTP id x19-20020a05640226d300b003f8b80f5729so7579541edd.13 for ; Thu, 13 Jan 2022 23:49:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=OfGvrCtC8xlimA6cEB+wdrguTqUYJCj+ZRy5BPwVdRo=; b=vBjaNLWEIjwPzxzOmRATZOEHlQaOvd2p0HZTvUtcGuQe59YgKCeaoFGbNM56rM/NeV N0lopxn2cZ6WJnRzLCloGkC0BrkoVXw7fA1kdohmqj4R/9atsoiqUEPU3Sh/ybAPLLyx y8ZXU+cdIalwh4CKv5OnwDOwrgTSOZR+JFG0k+4xI82Qr8R/yUvUwCZ2zRcejKnvF+Fz LJCNKwlHSwOGxQHGtJz0sDKbNnLK5G8HzDc683ts1iRrEmq6oi+kM5ng2Hi8oX73RYm+ ihZH1Ji0AeyuhCeO5//ICZB9IWg/48ahjUrQsw6cnltpW4HaBH8RaNn5JG5aE4FazHBs Vj1w== X-Gm-Message-State: AOAM531Rwcwm3+ISeJWB78vZVFTDlxE5Azipn7LLovPnAaZYKos6NAXo eU3Uq9gHkEBqwW/WPSbh5HaoZ8LL8Q2lcxTVczARmyNjLDYel1nrUWzNnuQh01pL8TVOoY4TfTP boiZxuv2wChpZmjBtXZIj+TXNoYXcqwiArBpli3RFTut7WzzNGAvL X-Received: by 2002:a05:6402:2685:: with SMTP id w5mr7710428edd.151.1642146578014; Thu, 13 Jan 2022 23:49:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJx28rjBXLGcKe6hIBmUk/lmPK/ygVLWajiItPMzl6kJqav/dcWM9ZuCOshtlFa/+UuDpfMTkw== X-Received: by 2002:a05:6402:2685:: with SMTP id w5mr7710414edd.151.1642146577885; Thu, 13 Jan 2022 23:49:37 -0800 (PST) Received: from [192.168.0.30] (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id jg41sm1602954ejc.101.2022.01.13.23.49.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 13 Jan 2022 23:49:37 -0800 (PST) Message-ID: <65e6f034-278a-81fa-844d-10a1865a25a4@canonical.com> Date: Fri, 14 Jan 2022 08:49:36 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.1 Subject: Re: [PATCH 10/23] dt-bindings: pinctrl: samsung: Add compatible for Tesla FSD SoC Content-Language: en-US To: Alim Akhtar , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Cc: soc@kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, olof@lixom.net, linus.walleij@linaro.org, catalin.marinas@arm.com, robh+dt@kernel.org, s.nawrocki@samsung.com, linux-samsung-soc@vger.kernel.org, pankaj.dubey@samsung.com, linux-fsd@tesla.com References: <20220113121143.22280-1-alim.akhtar@samsung.com> <20220113121143.22280-11-alim.akhtar@samsung.com> <849c7772-0f7e-32ff-6ea6-c46aa6837bb4@canonical.com> <076101d80909$d5849060$808db120$@samsung.com> From: Krzysztof Kozlowski In-Reply-To: <076101d80909$d5849060$808db120$@samsung.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220113_234948_419560_D7D32A2F X-CRM114-Status: GOOD ( 15.62 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 14/01/2022 06:44, Alim Akhtar wrote: > > >> -----Original Message----- >> From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@canonical.com] >> Sent: Thursday, January 13, 2022 5:57 PM >> To: Alim Akhtar ; linux-arm- >> kernel@lists.infradead.org; linux-kernel@vger.kernel.org >> Cc: soc@kernel.org; linux-clk@vger.kernel.org; devicetree@vger.kernel.org; >> olof@lixom.net; linus.walleij@linaro.org; catalin.marinas@arm.com; >> robh+dt@kernel.org; s.nawrocki@samsung.com; linux-samsung- >> soc@vger.kernel.org; pankaj.dubey@samsung.com; linux-fsd@tesla.com >> Subject: Re: [PATCH 10/23] dt-bindings: pinctrl: samsung: Add compatible for >> Tesla FSD SoC >> >> On 13/01/2022 13:11, Alim Akhtar wrote: >>> Add compatible for Tesla Full Self-Driving SoC. The pinctrl hardware >>> IP is similar to what found on most of the exynos series of SoC, so >>> this new compatible is added in samsung pinctrl binding. >>> >>> Cc: linux-fsd@tesla.com >>> Signed-off-by: Alim Akhtar >>> --- >>> Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff --git >>> a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> index b8b475967ff9..ba972998a0e4 100644 >>> --- a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> +++ b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt >>> @@ -24,6 +24,7 @@ Required Properties: >>> - "samsung,exynos7-pinctrl": for Exynos7 compatible pin-controller. >>> - "samsung,exynos850-pinctrl": for Exynos850 compatible pin-controller. >>> - "samsung,exynosautov9-pinctrl": for ExynosAutov9 compatible pin- >> controller. >>> + - "tesla,fsd-pinctrl": for Tesla FSD SoC compatible pin-controller. >>> >> >> Please rebase this on my latest Samsung pinctrl dtschema patches. You also >> need a tesla vendor prefix patch (separate). >> > Sure will rebase when sending v2, your latest patches are in Linux-next or still in your tree? The SPI (v3) and pinctrl (v2) dtschema patches are on mailing lists. They seem to be done, so after merge window they will make to linux-next. If you want earlier, grab them from mailing list or from branches: https://github.com/krzk/linux/tree/n/dt-bindings-samsung-spi-schema-v3 https://github.com/krzk/linux/tree/n/dt-bindings-samsung-pinctrl-schema-v2 Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel