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 77425ECAAD5 for ; Fri, 2 Sep 2022 16:35:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235631AbiIBQfn (ORCPT ); Fri, 2 Sep 2022 12:35:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59114 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230257AbiIBQfm (ORCPT ); Fri, 2 Sep 2022 12:35:42 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9D22757224; Fri, 2 Sep 2022 09:35:40 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id C6E0F62163; Fri, 2 Sep 2022 16:35:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 29C82C43143; Fri, 2 Sep 2022 16:35:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662136539; bh=CyXZslGC6xMHuFvaJ2y8P9mcnKdxUher6ZDcEysyZM4=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=inHkQYqQd1Ylei3Vn2o0zDzCCdpJmBllYZqgx68F0KRYC5ul6UDxGh8YL0SPmdepT 4G+uxFTXEf2tk85OGXqEdFHSoDi7t4Mmb/pj3TQGwBtt3TkObWNZ5dhFRFnrSe0bt0 KMhVBrb59aMHbzGTfrU598mUFdLmIg7/ld97347efEMtMmumS2bqdQYYZ5sAa/aXvz nFt2pFp2zeQE73RiGGfSujrRIVBebk9xUcQieOaFsTeI1OyrfSXEAe46DZ8g+B/afW AY1adak0OO0Fuwu8WDVvdV7PxfXhgWUav/bF7VwngeIt3unuWmwOu1I57933qRH0tO 8MxOseUWXJ9vg== Received: by mail-vk1-f171.google.com with SMTP id t82so1225353vkb.6; Fri, 02 Sep 2022 09:35:39 -0700 (PDT) X-Gm-Message-State: ACgBeo0EdQyeQR1YDU6vVQBJZqnk1X6+69mAwG+Ix1FgMLIMemcTrvlt k8W4f6FfEvHvKId2n6KH1MIZworTKI1jf/xheQ== X-Google-Smtp-Source: AA6agR7dwq63N6NQLKD/7IAKcnFBWx79Ln0WNBprwZv5blc/HPzGPu7Vyie82utDNhAe8IsODz3wLIsUaG4BPhD83bI= X-Received: by 2002:a1f:d241:0:b0:398:3e25:d2dd with SMTP id j62-20020a1fd241000000b003983e25d2ddmr1223vkg.15.1662136538025; Fri, 02 Sep 2022 09:35:38 -0700 (PDT) MIME-Version: 1.0 References: <20220822155130.2491006-1-Frank.Li@nxp.com> <20220822155130.2491006-4-Frank.Li@nxp.com> <20220825212130.GA1705214-robh@kernel.org> <871qt2x38f.wl-maz@kernel.org> <87zgfqvfvv.wl-maz@kernel.org> In-Reply-To: <87zgfqvfvv.wl-maz@kernel.org> From: Rob Herring Date: Fri, 2 Sep 2022 11:35:26 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [EXT] Re: [PATCH v7 3/4] dt-bindings: irqchip: imx mu work as msi controller To: Marc Zyngier Cc: Frank Li , "tglx@linutronix.de" , "krzysztof.kozlowski+dt@linaro.org" , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" , "kw@linux.com" , "bhelgaas@google.com" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-pci@vger.kernel.org" , Peng Fan , Aisheng Dong , "jdmason@kudzu.us" , "kernel@pengutronix.de" , "festevam@gmail.com" , dl-linux-imx , "kishon@ti.com" , "lorenzo.pieralisi@arm.com" , "ntb@lists.linux.dev" , "lznuaa@gmail.com" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Fri, Aug 26, 2022 at 4:44 PM Marc Zyngier wrote: > > On Fri, 26 Aug 2022 19:59:44 +0100, > Frank Li wrote: > > > > > And I stand by my initial request. "a" doesn't convey any sort of > > > useful information. Why not "I" and "II", while we're at it? Or > > > something even funkier? > > > > MU spec use term "a" and "b", user have to map "I" an "II" to > > "a" and "b" when read MU spec and code. it is not straightforward. > > > > I quote a part of spec. > > " The MU is connected as a peripheral under the Peripheral bus on both sides-on > > the Processor A-side, the Processor A Peripheral Bus, and on the Processor B side, > > the Processor B Peripheral Bus." > > > > Rob Herring and Marc Zynginer: > > I can change to any name, which you agree both. > > > > Some options: > > 1. "a", "b" > > 2. "a-side", "b-side" > > 3. "a-facing", "b-facing" > > 4. "I", "II" > > Use the wording indicated in the spec: "processor-a-side", and > "processor-b-side". This is what I asked the first place. I would pick 2 (or nothing), but whatever... As long as there aren't spaces. Rob