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 A9E60C433FE for ; Mon, 18 Apr 2022 08:16:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237153AbiDRISz (ORCPT ); Mon, 18 Apr 2022 04:18:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237149AbiDRISx (ORCPT ); Mon, 18 Apr 2022 04:18:53 -0400 Received: from ssl.serverraum.org (ssl.serverraum.org [IPv6:2a01:4f8:151:8464::1:2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 81836167D5; Mon, 18 Apr 2022 01:16:14 -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 530CF22239; Mon, 18 Apr 2022 10:16:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1650269772; 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=9+JeLm6TahuxrZU78uCicymdF3GylKVG8FLqiH1KSU4=; b=X69WuQ9+VFYcZyfZuEWMf2RQTlOHWjqC+9geHKufQpPiB1DuOQxp1h57NTQJMgNV+XBlL5 anKm8RfpilE7JjUTjBt5SlPCFc5b4aIDMqVx9QTKEmISOBNFeb8GLhic5k+m/JEZYEQC5l PcZNUXz0Z90dY9rkB4KEVrVrpf8eMHI= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 18 Apr 2022 10:16:10 +0200 From: Michael Walle To: Linus Walleij Cc: Rob Herring , Krzysztof Kozlowski , 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: X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org 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? -michael [1] https://lore.kernel.org/linux-gpio/20220313154640.63813-1-michael@walle.cc/