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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A6244C27C53 for ; Wed, 19 Jun 2024 23:46:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:MIME-Version: Content-Transfer-Encoding:Content-Type:References:In-Reply-To:Date:Cc:To:From :Subject:Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=0rrDHG6GQ3ZPTEMZclkJ055uBnnGraoUKkuWTroE0M4=; b=31ge88iWWkPxP3PYY0imuQbx9x XzvcaOneWdE02eKgNweNRGubuOJsrW7ocQJMQMsmKwHrDEDFxa6SSgwXWe6X3gPDK1iWBIJfSGPgl t7c4TZSCHzzLk51fnJyLxsaAvFf7QpcAKrEUWkJjg8i/Q3CUfcD+/JC+5wJuHgyGMAtCY2WQtLuvz mWnkT4g1i7hGSHao24wh7b3NMDIhd1KQ8TQ/XAzR7P1NKPFyOztBxPoZQSiimyjYGfOUIYDNHt47X gd0fjhGVJrbuWUUTV6U5ZFemobUXLt0bgribcqb3Uugtf/sBaLb/sLz3wsPOsoLCZnwL0ApgkkAYm M5xji7RA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sK50B-000000032iE-2okE; Wed, 19 Jun 2024 23:46:07 +0000 Received: from pi.codeconstruct.com.au ([203.29.241.158] helo=codeconstruct.com.au) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sK505-000000032hO-2ooF for linux-arm-kernel@lists.infradead.org; Wed, 19 Jun 2024 23:46:06 +0000 Received: from [192.168.68.112] (ppp118-210-79-194.adl-adc-lon-bras32.tpg.internode.on.net [118.210.79.194]) by mail.codeconstruct.com.au (Postfix) with ESMTPSA id E2FFC20154; Thu, 20 Jun 2024 07:45:49 +0800 (AWST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codeconstruct.com.au; s=2022a; t=1718840753; bh=0rrDHG6GQ3ZPTEMZclkJ055uBnnGraoUKkuWTroE0M4=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=dohAyRhpTxw/33WRPJ9Mdqdis4t5zfM7m2r0c1IETWbFfzW8o2bc/bsGafowhlV+P m/WrOnFyU3V75fhr0Qx8HqVZ6QE+fosWnPRsiumeCwa++ucEUuXhZsHtgRQm3I+25n ip8KqrtQD0qK1ZmJqi1OXHP2lLhvM0Z7z4Dkxr1JWYWrbO5XY721k5aLSkc7e8wwsM uNlh4h54Uq00W49U6koh5DWhhaidC7eT1saqTfxy8+lX1j1agu7jl55Arxt1QaC6GP SnujxMbHVrqYL6GepkQZvk2+7yhur9jCzW3W5AzVDLJxJwKHbNep5WmKl1apYVHMEF ImCCkpwzBusCA== Message-ID: <4eb1830db13cc3aa8d23d2c6075f744c0b75bda1.camel@codeconstruct.com.au> Subject: Re: [PATCH 1/1] pinctrl: aspeed-g6: Add NCSI pin group config From: Andrew Jeffery To: Potin Lai Cc: Linus Walleij , Joel Stanley , linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Patrick Williams , Cosmo Chou , Potin Lai Date: Thu, 20 Jun 2024 09:15:48 +0930 In-Reply-To: References: <20240613080725.2531580-1-potin.lai.pt@gmail.com> <946f44526e3016f595bfe463cf0a7f5b4eaa084a.camel@codeconstruct.com.au> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.46.4-2 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240619_164601_944849_CA7321A7 X-CRM114-Status: GOOD ( 14.99 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, 2024-06-19 at 19:24 +0800, Potin Lai wrote: > On Mon, Jun 17, 2024 at 3:33=E2=80=AFPM Andrew Jeffery > wrote: > >=20 > > On Thu, 2024-06-13 at 16:07 +0800, Potin Lai wrote: > > > In the NCSI pin table, the reference clock output pin (RMIIXRCLKO) is= not > > > needed on the management controller side. > > >=20 > > > To optimize pin usage, add new NCSI pin groupis that excludes RMIIXRC= LKO, > > > reducing the number of required pins. > >=20 > > Hmm, I'm not convinced this is specific to NCSI (and it's an > > unfortunate mistake on my part), but we do need to call the groups > > something different than RMII[34]. Did you have any other suggestions? > >=20 > I don't have better name for now. > In ast2600 data sheet, it also mentioned "RMII" & "NCSI" together most > of the time, is it ok to use "NCSI" as a new group name? Perhaps we go with "NCSI", because the other thoughts I had are all much less succinct. Can you please add a note to the description in the binding that discusses the difference between the RMII and NCSI groups? Andrew