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 32E0AC433F5 for ; Mon, 18 Apr 2022 12:04:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237971AbiDRMG6 (ORCPT ); Mon, 18 Apr 2022 08:06:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34590 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237968AbiDRMG5 (ORCPT ); Mon, 18 Apr 2022 08:06:57 -0400 Received: from ssl.serverraum.org (ssl.serverraum.org [176.9.125.105]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5011B15FDA; Mon, 18 Apr 2022 05:04:18 -0700 (PDT) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 34DB422175; Mon, 18 Apr 2022 14:04:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1650283456; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OOruPXULnAoAti7zK9CIqg2Yvot+7zRgvmQ60wa4z+o=; b=M8C4AIhWHlFgBT/ZWxIY6IFRlmKw7xBLhdPb0w5dc/BusXwRU1ZVXxb4Gj+J9buPd/VjEg DbSwmcgcwAGOmjlASvzxAgodj/RSp7+Re4q4xX5bDsGWAwrc1rbW3Ivf1CBiIuvitgjM95 aZfqXyrmJ0sXVfw0TuuzGdlwXhjyJhQ= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 18 Apr 2022 14:04:16 +0200 From: Michael Walle To: Krzysztof Kozlowski Cc: Linus Walleij , Rob Herring , Lars Povlsen , Steen Hegelund , Thomas Bogendoerfer , Gregory CLEMENT , Paul Burton , Quentin Schulz , Antoine Tenart , Kavyasree Kotagiri , Nicolas Ferre , "David S . Miller" , UNGLinuxDriver@microchip.com, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org Subject: Re: [PATCH v3 6/6] dt-bindings: pinctrl: convert ocelot-pinctrl to YAML format In-Reply-To: References: <20220319204628.1759635-1-michael@walle.cc> <20220319204628.1759635-7-michael@walle.cc> User-Agent: Roundcube Webmail/1.4.13 Message-ID: <735863d6476605e4ff72032d8971ac0d@walle.cc> X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Am 2022-04-18 13:13, schrieb Krzysztof Kozlowski: > On 18/04/2022 10:19, Michael Walle wrote: >> [resend, use Krysztof's new email address] >> >> Am 2022-04-18 01:41, schrieb Linus Walleij: >>> On Sat, Mar 19, 2022 at 9:47 PM Michael Walle >>> wrote: >>> >>>> Convert the ocelot-pinctrl device tree binding to the new YAML >>>> format. >>>> >>>> Additionally to the original binding documentation, add interrupt >>>> properties which are optional and already used on several SoCs like >>>> SparX-5, Luton, Ocelot and LAN966x but were not documented before. >>>> >>>> Also, on the sparx5 and the lan966x SoCs there are two items for the >>>> reg property. >>>> >>>> Signed-off-by: Michael Walle >>> >>> So is this single patch something I should apply to the pin control >>> tree? >> >> The first five patches will fix the validation errrors once the >> binding is converted to the YAML format. So, do they need to go >> through the same tree? >> >> Also as mentioned, there is this pending series [1] which is the >> reason I've converted the binding to YAML in the first place. So >> at least the first patch of this series will have to go through >> the same tree as the YAML conversion patch. >> >> How can we move forward here? Krzysztof, maybe all of the dt >> bindings patches can go through your tree and I'll reposting >> the second patch of [1] afterwards? > > I think you got all necessary acks for this pinctrl bindings change and > the dependency ("add reset property"), so both can go via Linus' tree. > That's preferred. > > DTS patches goes through your SoC maintainer tree. Ah, ok, I wasn't aware of that. Then yes, please go ahead and pick this and the first patch of [1] up, Linus. Of course if you like you can pick the second patch of [1], too. But I can also repost it without the RFC tag if that is preferred. -michael [1] https://lore.kernel.org/linux-gpio/20220313154640.63813-1-michael@walle.cc/