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 F32DEC636D6 for ; Thu, 23 Feb 2023 17:18:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229711AbjBWRSA (ORCPT ); Thu, 23 Feb 2023 12:18:00 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229454AbjBWRR6 (ORCPT ); Thu, 23 Feb 2023 12:17:58 -0500 Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3A7395FF8; Thu, 23 Feb 2023 09:17:56 -0800 (PST) Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 31NHHXY2037741; Thu, 23 Feb 2023 11:17:33 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1677172653; bh=o2Nb7KbFzvIYkv4sc2lMJ4n5HXWpmBwMln8gTDzt9K0=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=wMrtpCCafkPOnQwzlEcjxQqTlNCsWd4DnQS5l+Sq2uI++DrbqQIimEHXpsvDka0oT AzyGhbYvxo2IU9+JFFcrrmN/A8I/voZQOy/QOZIS+gseGrCJDGS7CQe1y1+spFJD7C MOoJHPc5W6N2YRtl3hIHBDIKr3TFfDI5LbLSIIck= Received: from DLEE106.ent.ti.com (dlee106.ent.ti.com [157.170.170.36]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 31NHHXUP072344 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 23 Feb 2023 11:17:33 -0600 Received: from DLEE100.ent.ti.com (157.170.170.30) by DLEE106.ent.ti.com (157.170.170.36) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16; Thu, 23 Feb 2023 11:17:32 -0600 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE100.ent.ti.com (157.170.170.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.16 via Frontend Transport; Thu, 23 Feb 2023 11:17:32 -0600 Received: from [10.250.32.101] (ileaxei01-snat2.itg.ti.com [10.180.69.6]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 31NHHWVx058665; Thu, 23 Feb 2023 11:17:32 -0600 Message-ID: Date: Thu, 23 Feb 2023 11:17:31 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Content-Language: en-US To: Colin Foster CC: , , , , Tony Lindgren , =?UTF-8?Q?Beno=c3=aet_Cousson?= , , Olof Johansson , Arnd Bergmann , Krzysztof Kozlowski , Rob Herring References: <20230222203847.2664903-1-colin.foster@in-advantage.com> <20230222203847.2664903-2-colin.foster@in-advantage.com> From: Andrew Davis In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/23/23 10:25 AM, Colin Foster wrote: > On Thu, Feb 23, 2023 at 10:00:50AM -0600, Andrew Davis wrote: >> On 2/22/23 2:38 PM, Colin Foster wrote: >>> Add yaml documentation for TI OMAP devices for the Phytec PCM-049 SoM and >>> the Phytec PCM-959 development kit. >>> >>> Signed-off-by: Colin Foster >>> --- >>> >>> v4 >>> * New patch, based on a WIP from Andrew Davis >>> >>> --- >>> .../devicetree/bindings/arm/ti,omap.yaml | 29 +++++++++++++++++++ >>> 1 file changed, 29 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/arm/ti,omap.yaml >> >> How will this work if I add the same file? Why not take my WIP patch, make >> the suggested changes from Rob, then have it as your first patch in this >> series? > > Is your WIP intended to convert all omap.txt to ti,omap.yaml? Or chunk > off devices one at a time? > > If the former, when your patch is done it should be a pretty simple > rebase conflict resolution. If the latter (which feels more digestable) > this offers that template. This was Rob's / Tony's suggestion, albeit > before you sent your patch set. > > > Anyway, I'm happy to do any of the following: > > 1. Take Andrew's patches, add these references and re-submit. > 2. Keep this set as-is (with the typo fix) and when Andrew's WIP is done > it should be an easy rebase before submission. > 3. Wait for Andrew's WIP to be done, then submit with this update. > > > I'd like to avoid #3 because I don't know where this might fall on your > priorities list. Low priority for me, I'd suggest #1 or they probably will not be converted anytime soon. Andrew