Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp674229rwb; Wed, 16 Nov 2022 06:18:02 -0800 (PST) X-Google-Smtp-Source: AA0mqf5Jt3tU+avOzHBfcrmNdAi9WTYKSpmomIrgmiStJVB5OxCtUE4o1rJseO9PfCIIHnIgV1Yz X-Received: by 2002:a63:571b:0:b0:46f:1085:eeb6 with SMTP id l27-20020a63571b000000b0046f1085eeb6mr20671676pgb.266.1668608282546; Wed, 16 Nov 2022 06:18:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668608282; cv=none; d=google.com; s=arc-20160816; b=hFwTld4lmSG4DbQ+WectKWTTROfy9bs6ubXwf7KsDuX4Csqvy7N7grifV3h7F9Fxhn aa2ewGUQs0VXtylSMakGuPdAdu5z+4Gv3XQBE8SRXo/vG7eeKoikpz5XVpZc5ANYvIPO Ageu7ltrYJuDwqWpr4C+6MgnkKge56fU9AFw/eJJTfAE0vW+G90IdHGaWTNvBHKekUnY EUYZgXRwapajfxU6yP7pW0HYhg3gGCclCbopvugqCpdVa6bCP7F7PRygdzAOFc2qGUi9 +SQ5n/hVRk/Tz6Y0G29/NPG+P/bwpBIj2MgQo66F15u5Y1pkw1QCr6FQi4Vxy9ccT4lv IDPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=WebiL4n6ymCJnvOsrbdPOUTgEwekBwRnC50QnJQgp0k=; b=g/TkgFe1kva9/k+Qa3zksukASaD3TVGUIMKyl8FX31Hv4glUCfZdXsJDhk8Q1VRVvK fJ/x0ze9SW33ca7e36mxbwCFKegp4fs3RcPD1FRMw40DBctasvbq93EFRF4QCgJ4RKIS LF9yYlubSadeOyL+o6RNYsKxVHc0pbPiLd8lnIX2IiO7Qb0dXYw0Tkww/pBRXYHTeq4m 6hZhr/4vGXsmhq6DsfI1lCu4mc10QFeTr5wZWcQuCA4EcvjCUaLKyGWX7mwaHLLixV7N dk7fVgUNHqgizo5ADW16kfHoE6DYkiEy7GhjyD2RpaEbz83/BgDbN4r8XglFTL6c1eGy Lrcw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fiRd22VU; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f20-20020a63f114000000b00476bba7cbf7si4477557pgi.471.2022.11.16.06.17.47; Wed, 16 Nov 2022 06:18:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=fiRd22VU; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233918AbiKPNhD (ORCPT + 91 others); Wed, 16 Nov 2022 08:37:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50882 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233955AbiKPNgx (ORCPT ); Wed, 16 Nov 2022 08:36:53 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E710564EA; Wed, 16 Nov 2022 05:36:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668605813; x=1700141813; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=JELkfQUrNNjTFHvCmopSzT6F8rwD4FHhQPiEyR2Qkz0=; b=fiRd22VUhcPlY+LYsrYNBJDYtHtrC5Nh2hArsGJuSV6n2wAiWN3vN4u3 CXArsMogFjGFBqprITbvHdiyteCJVMq8wSkETrIXt5X8Dabb9hrQKV4P7 OpEy81KoHLOImPO6K4lMC2dqBvNNvL393oDC+D27FfYzv0JfwOHD1viEW i98ixEhWce1v22tBNoL3oClxvjoeseoD3+wBVhZj0Et4gmQlRkR9zhEkC fsHYjMpVWkCbbjthWbGkZVjyQsXYr7ZTq8OcwDVnI34iFlzoeTa5dSI8/ KY82FdnVW/bRuZdRXh3h1wpx5LeQPGIQxymkNqiHLePfOh2UQc0adRCeu Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10532"; a="312549354" X-IronPort-AV: E=Sophos;i="5.96,167,1665471600"; d="scan'208";a="312549354" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Nov 2022 05:36:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10532"; a="968424218" X-IronPort-AV: E=Sophos;i="5.96,167,1665471600"; d="scan'208";a="968424218" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga005.fm.intel.com with ESMTP; 16 Nov 2022 05:36:40 -0800 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ovIak-00D90f-0E; Wed, 16 Nov 2022 15:36:38 +0200 Date: Wed, 16 Nov 2022 15:36:37 +0200 From: Andy Shevchenko To: Rahul Tanwar Cc: "devicetree@vger.kernel.org" , "robh@kernel.org" , "tglx@linutronix.de" , "mingo@redhat.com" , "bp@alien8.de" , "dave.hansen@linux.intel.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "hpa@zytor.com" , "alan@lxorguk.ukuu.org.uk" , "dirk.brandewie@gmail.com" , "grant.likely@secretlab.ca" , "sodaville@linutronix.de" , "devicetree-discuss@lists.ozlabs.org" , linux-lgm-soc Subject: Re: [PATCH v2 2/2] x86/of: Convert & update Intel's APIC related binding schemas Message-ID: References: <5ba7963fbd82a859ffd99c6d8edb4d717fce0e6c.1668589253.git.rtanwar@maxlinear.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 16, 2022 at 10:52:59AM +0000, Rahul Tanwar wrote: > On 16/11/2022 6:42 pm, Andy Shevchenko wrote: > > On Wed, Nov 16, 2022 at 06:28:21PM +0800, Rahul Tanwar wrote: > >> Intel's APIC family of interrupt controllers support local APIC > >> (lapic) & I/O APIC (ioapic). Convert existing bindings for lapic > >> & ioapic from text to YAML schema. Separate lapic & ioapic schemas. > >> > >> Also, update more info and newly introduced optional property for > >> lapic to choose legacy PIC or virtual wire compatibility interrupt > >> delivery mode. > > > > Conversion should be split from a new property addition. > > > > Do you mean, i first update older text file with new property addition > and then later convert it into YAML i.e. for now i just update existing > text file with new addition and later convert them to YAML schema ? Thanks. Patch 1: Convert to YAML (no content changes except its format) Patch 2: Introducing a new property Patch 3: Updating code in x86 First two must be send to the DT people and have their Acks/Rb after all. -- With Best Regards, Andy Shevchenko