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 96298C433F5 for ; Tue, 18 Jan 2022 07:52:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234433AbiARHwh (ORCPT ); Tue, 18 Jan 2022 02:52:37 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:39988 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235942AbiARHwg (ORCPT ); Tue, 18 Jan 2022 02:52:36 -0500 Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (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-1.canonical.com (Postfix) with ESMTPS id 4E89B40515 for ; Tue, 18 Jan 2022 07:52:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1642492355; bh=aNtiM+Mkd9efU1H0Wh+stfJIqfRGDAuGYHwSDx2cIxk=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=pUEsfnD4G8rzpPF1W6GCucVZvTUXP6TTMslAC6eB+nKtKLpTmsIBtPdM435v3YobL CJ/Rca7bY4fKXDP6LlNt0ipz/hfM2wS9TVqiDyCI/2tY0f0TRFta1XdEPUETKQ8HeV nXVme2Ec83QCAVlAO04ADZRvpjFesLr+Yy8AknVRTywmm50MlASnea40Gc9NAtO/l6 SjoF7a0i2oXG7AtQzQUTqFMYpCFmTts48mcC9IFElg1tmcFGBSZUMsw/0yVZP6EPo3 TR+vj5cZA8+FIPC4Twcf5KmKpvnv+uqsk2SlDNbjWkLrgZNsFLSl9tYFN01VAg+rD3 IdbmZ4IigM5HQ== Received: by mail-ed1-f69.google.com with SMTP id o10-20020a056402438a00b00403212b6b1aso3123175edc.13 for ; Mon, 17 Jan 2022 23:52:35 -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=aNtiM+Mkd9efU1H0Wh+stfJIqfRGDAuGYHwSDx2cIxk=; b=myhOjhYyJcsesAo1BTECUDmtNJj8gZdi8jskP1PymQ+FCUpwnnOxqgGBISN57BonHC k9RTeuBBPNDB1xSxQEMm21Dgd/yJ81kg+QnsA0583BUS2Ee1kurQXHidNUuO+T9IXgzR qSQcR/XuuyOe7elkqxGG4sOasVkBjclvHRzu4AC0ACNUxxqRoKv4ZvvNQ3aBlh11FcVJ rrGrYLA2oLgAw2F/38/iswFVZpt41vG3Pghwn+GEaIOTJWip7givqJhKIppy9XAslgcP Pq8G/FTTJZwksfo34PyiZ5d7PD3VDqzIbDBsiTAAdD+A49AB4FXDeQxZo7zDQMMNg+Jg AbVg== X-Gm-Message-State: AOAM533vSkcKMtIGjXQjv//rmxmzoBgCD1diEuJu9cVbGKxreYspX6u8 YzdbLKMXtFnhXDjbKNbJ8Zl3Wt3kVPIgzKyNI/Dce5gaMxLQT+Y6AyOqx82eagja8LfmOAq9XXD B/eRcCOWKivXNyI+dxavV+3V4T8McrgYrsNiSMcw= X-Received: by 2002:a17:907:1b0d:: with SMTP id mp13mr19153543ejc.29.1642492354936; Mon, 17 Jan 2022 23:52:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJwBxln2AY6zvpOpDMIrbY3pJ2WqNGAK6xMIm4ZKaNEKJULRafQ8SSXBijKpYwqfIhylcmfhEA== X-Received: by 2002:a17:907:1b0d:: with SMTP id mp13mr19153526ejc.29.1642492354785; Mon, 17 Jan 2022 23:52:34 -0800 (PST) Received: from [192.168.0.40] (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id a3sm5071801ejd.34.2022.01.17.23.52.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Jan 2022 23:52:34 -0800 (PST) Message-ID: <794f39ed-3436-432c-767d-8fa60779d510@canonical.com> Date: Tue, 18 Jan 2022 08:52:33 +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 v2 24/28] dt-bindings: pinctrl: samsung: convert to dtschema Content-Language: en-US To: Olof Johansson Cc: Linus Walleij , Arnd Bergmann , Tomasz Figa , Sylwester Nawrocki , Rob Herring , Linux ARM Mailing List , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , "open list:GPIO SUBSYSTEM" , DTML , Linux Kernel Mailing List , Marek Szyprowski , Sam Protsenko , Chanho Park , Alim Akhtar , Rob Herring References: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> <20220111201722.327219-18-krzysztof.kozlowski@canonical.com> <5047da7c-d3a6-5472-b0ca-7ed3dbe8a5fe@canonical.com> <77bd8fa4-2b35-352c-da07-ef91fcbed454@canonical.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On 17/01/2022 21:26, Olof Johansson wrote: > On Sun, Jan 16, 2022 at 11:45 PM Krzysztof Kozlowski > wrote: >> >> On 16/01/2022 22:38, Linus Walleij wrote: >>> On Sun, Jan 16, 2022 at 6:10 PM Krzysztof Kozlowski >>> wrote: >>> >>>> Anyway DTS and dtschema will have to wait for one release, because they >>>> depend on samsung pinctrl driver change (patch #2). >>> >>> What about I put that (and maybe this schema) on an immutable >>> branch so you can pull the commit into your for-arm-soc branch and >>> put the DTS changes on top? >> >> That would be a solution if not a policy for arm-soc of keeping DTS >> separate. Arnd and Olof since some time are not happy when DTS branch >> receives any driver updates. >> >> Arnd, Olof, >> This is a set of dtschema conversion + DTS alignment with new schema: >> 1. Driver change necessary to accept new DTS (driver depends on node >> names and this has to change because of dtschema), >> 2. DTS commits depending on above, which convert node name to new format, >> 3. Finally dtschema requiring new naming of the GPIO nodes. >> >> If I got correctly, the policy of not mixing drivers and DTS requires >> that #2 above (DTS changes) will wait for one more release. During the >> time, if dtschema (#3 above) is applied, there will be new warnings >> about non-compliant DTS. >> >> Do you see any chance of merging driver + DTS + dtschema via same tree >> in same release? > > Our general guidance to separate DTS and driver changes is to avoid > large entangled changes between the two, and to discourage a developer > mentality of "the implementation is the binding". > > I think this is a good example of when it makes sense to bring in what > is a fairly small and clean driver change to deal with this. So the > right answer here is to stage such a stable branch and merge into both > arm-soc and the pinctrl subsystem trees as proposed. Thanks for clarification, I'll go with this approach. 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 CCA1EC433FE for ; Tue, 18 Jan 2022 07:54:03 +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=0KThwIdDNToqmaANDOgF4R3mmjq4UpDV3gPdRoHRZRM=; b=o+FBxtgAgnrhBG T657NXsWUliYIMAGtvN4G/XBL9Ww04vy8EUsa4LDANnQxfGAkzW+fIGMRJnFTC+7fQOUPW1DJVHQ9 1g5dTLhhx+AGP4jXzFd14Z59YjPa2a2Rdt80KFtJACRrFK1T9M/sxaaRtAQm3cBvTg89LRgdaX+Hh z+EJ/zxG7PXp4k5Nb2T/ZHNGcnWJpOx2Si3MIjNUkCjHFaHUn8J7DOuYuSYspP8IGtenycj2S4Mhj G+P3XdjowMlam3VsC9D+HFT3Zi+CDpsA87hoqXE4Z2Isld43vI2jO7F+h8hmtzdF077uFjDhLNndg WheZpe8I9PjqJAp8IY0w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n9jIL-000e10-2R; Tue, 18 Jan 2022 07:52:45 +0000 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n9jIH-000e0S-Vf for linux-arm-kernel@lists.infradead.org; Tue, 18 Jan 2022 07:52:43 +0000 Received: from mail-ed1-f69.google.com (mail-ed1-f69.google.com [209.85.208.69]) (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-1.canonical.com (Postfix) with ESMTPS id 6B4E6407F3 for ; Tue, 18 Jan 2022 07:52:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1642492355; bh=aNtiM+Mkd9efU1H0Wh+stfJIqfRGDAuGYHwSDx2cIxk=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=pUEsfnD4G8rzpPF1W6GCucVZvTUXP6TTMslAC6eB+nKtKLpTmsIBtPdM435v3YobL CJ/Rca7bY4fKXDP6LlNt0ipz/hfM2wS9TVqiDyCI/2tY0f0TRFta1XdEPUETKQ8HeV nXVme2Ec83QCAVlAO04ADZRvpjFesLr+Yy8AknVRTywmm50MlASnea40Gc9NAtO/l6 SjoF7a0i2oXG7AtQzQUTqFMYpCFmTts48mcC9IFElg1tmcFGBSZUMsw/0yVZP6EPo3 TR+vj5cZA8+FIPC4Twcf5KmKpvnv+uqsk2SlDNbjWkLrgZNsFLSl9tYFN01VAg+rD3 IdbmZ4IigM5HQ== Received: by mail-ed1-f69.google.com with SMTP id h21-20020aa7c955000000b0040390b2bfc5so569759edt.15 for ; Mon, 17 Jan 2022 23:52:35 -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=aNtiM+Mkd9efU1H0Wh+stfJIqfRGDAuGYHwSDx2cIxk=; b=JiLc1ypTTysTauWVqATAe10c+RszrLY9cf8lyx+67dDzsyqiyIQ+Cq0KTy1inUiQwH 956tOX1p/b9lPkwiBRZnhHYe9/FWJ1A4d86Ebs6J5b5XgarCBQqHLfv86xdqnsPp2+U+ 6JrO9ekbr5PSF4SrUPepOePGHesu0u87tJHeZroZVxWyGd9NyL8AhpnWXwdUpEZOmEdu 9g22BRVVN5DKw7ePEVjjkSHrda/OcikRQK2XG1tIzPd6luJ8nUh1qxB8WClDoFrCHZ3K l+i8YqeYS0V6hH1pNJ/cxfnIAZsq1/bjhIBR0O55w2EJDFjLrONMtmVS5ZwYUdpgouQJ CF6g== X-Gm-Message-State: AOAM5339W6w/zOPkTOBWc/HYegQgL/PlykYT8c16oBAaF/uR5yzJN5+I nekB6RuuCiS0ixIXkeRu0CEo0BXhx/YERXGk9m0/2FuZ9VRLlGZYZm1YKdoy4B38EFSAI9eX6hp B3x19kcNtxkgyB49nN7OFbHX3A/havUVnbmBR+TWNc7Ft2Cn47QhJ X-Received: by 2002:a17:907:1b0d:: with SMTP id mp13mr19153547ejc.29.1642492355018; Mon, 17 Jan 2022 23:52:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJwBxln2AY6zvpOpDMIrbY3pJ2WqNGAK6xMIm4ZKaNEKJULRafQ8SSXBijKpYwqfIhylcmfhEA== X-Received: by 2002:a17:907:1b0d:: with SMTP id mp13mr19153526ejc.29.1642492354785; Mon, 17 Jan 2022 23:52:34 -0800 (PST) Received: from [192.168.0.40] (xdsl-188-155-168-84.adslplus.ch. [188.155.168.84]) by smtp.gmail.com with ESMTPSA id a3sm5071801ejd.34.2022.01.17.23.52.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 17 Jan 2022 23:52:34 -0800 (PST) Message-ID: <794f39ed-3436-432c-767d-8fa60779d510@canonical.com> Date: Tue, 18 Jan 2022 08:52:33 +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 v2 24/28] dt-bindings: pinctrl: samsung: convert to dtschema Content-Language: en-US To: Olof Johansson Cc: Linus Walleij , Arnd Bergmann , Tomasz Figa , Sylwester Nawrocki , Rob Herring , Linux ARM Mailing List , "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" , "open list:GPIO SUBSYSTEM" , DTML , Linux Kernel Mailing List , Marek Szyprowski , Sam Protsenko , Chanho Park , Alim Akhtar , Rob Herring References: <20220111201426.326777-1-krzysztof.kozlowski@canonical.com> <20220111201722.327219-18-krzysztof.kozlowski@canonical.com> <5047da7c-d3a6-5472-b0ca-7ed3dbe8a5fe@canonical.com> <77bd8fa4-2b35-352c-da07-ef91fcbed454@canonical.com> From: Krzysztof Kozlowski In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220117_235242_193657_2C9D5208 X-CRM114-Status: GOOD ( 27.09 ) 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 17/01/2022 21:26, Olof Johansson wrote: > On Sun, Jan 16, 2022 at 11:45 PM Krzysztof Kozlowski > wrote: >> >> On 16/01/2022 22:38, Linus Walleij wrote: >>> On Sun, Jan 16, 2022 at 6:10 PM Krzysztof Kozlowski >>> wrote: >>> >>>> Anyway DTS and dtschema will have to wait for one release, because they >>>> depend on samsung pinctrl driver change (patch #2). >>> >>> What about I put that (and maybe this schema) on an immutable >>> branch so you can pull the commit into your for-arm-soc branch and >>> put the DTS changes on top? >> >> That would be a solution if not a policy for arm-soc of keeping DTS >> separate. Arnd and Olof since some time are not happy when DTS branch >> receives any driver updates. >> >> Arnd, Olof, >> This is a set of dtschema conversion + DTS alignment with new schema: >> 1. Driver change necessary to accept new DTS (driver depends on node >> names and this has to change because of dtschema), >> 2. DTS commits depending on above, which convert node name to new format, >> 3. Finally dtschema requiring new naming of the GPIO nodes. >> >> If I got correctly, the policy of not mixing drivers and DTS requires >> that #2 above (DTS changes) will wait for one more release. During the >> time, if dtschema (#3 above) is applied, there will be new warnings >> about non-compliant DTS. >> >> Do you see any chance of merging driver + DTS + dtschema via same tree >> in same release? > > Our general guidance to separate DTS and driver changes is to avoid > large entangled changes between the two, and to discourage a developer > mentality of "the implementation is the binding". > > I think this is a good example of when it makes sense to bring in what > is a fairly small and clean driver change to deal with this. So the > right answer here is to stage such a stable branch and merge into both > arm-soc and the pinctrl subsystem trees as proposed. Thanks for clarification, I'll go with this approach. Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel