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 24226C2BD09 for ; Thu, 27 Jun 2024 15:45:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Cc:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date:Reply-To :Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=UqFbCb6tczokF1dXxkNrdIjF8KGwyOsHiNWofmOIpJg=; b=gqJ84i2ZqftY3R4cc6OBWqj9wf ETA/78uS/APvL1dC1vyLXqBXqepWMTrpN8dGYczf8Qlrz0SoC0YwVy7BYWolxp/SJxzkLX/A46pqu SRTkthsGtVwukNLuXkz45saLCDjld+vCjfTrnDP4AypWdYXxICOFRkLXsbV2KwANsoYfhz0AUzjd9 aJrSkkleIZEVjcRIjHrW5J7DxnafQMTVmg5otyJKeF+VQ0Nq1+qF4FKhOFfuxRKb5qYtNeLzAREHD T21icJpAx+vfYuTsQ5F9agf/bSiGuFsR8S2y6K2S4Nq21kIQBPx7VkhW5Fi8ZxfMjMunOzYdx7m+m GAIRxDpQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sMrJ8-0000000AvK3-3YrV; Thu, 27 Jun 2024 15:45:10 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sMrIz-0000000AvHd-0SIA for linux-arm-kernel@lists.infradead.org; Thu, 27 Jun 2024 15:45:04 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id A0EA861ED9; Thu, 27 Jun 2024 15:44:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5B95FC2BBFC; Thu, 27 Jun 2024 15:44:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1719503099; bh=t9RDTqcnY5vGFNoxkmThHGvrq09KQuDh0EnptxEQZ6E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RON9hzvcadQQBER5cjIGLISL96po8BKIAuEeuoq816vKtfbrJsAH7t3ERXPot+caG GUB8fJuaeALa7rYJSlhAadsxoiNAdTpNTe02q4ITePGDwL1HqP59lF697e0aNrANFD 8qo2x+xKgR3pLL6i35TO8H/kxRLBRK4PPzcFz6uC1Ddtq33IGpDEIMrfSLWOXg+S0t 41faZLx77Qpc4/j2uAZk1bxI1hNEQgVZOfR5RvTUoq2Od0vnccJFfOBiMrGT3IGPw9 jB8jP/atn1jd16kXmVM28WiFhw3mGc840WDrp0suWrDT0Cobl+21osutOzlQbwSXjm K6M/7ye/YXbnQ== Date: Thu, 27 Jun 2024 16:44:54 +0100 From: Conor Dooley To: Manikandan.M@microchip.com Subject: Re: [PATCH v2 4/5] dt-bindings: gpio: convert Atmel GPIO to json-schema Message-ID: <20240627-share-dry-edfd5d86051e@spud> References: <20240625043525.279711-1-manikandan.m@microchip.com> <20240625043525.279711-5-manikandan.m@microchip.com> <20240625-clerical-manicure-ebc8a1d1b16b@spud> <96898000-1ef4-40c7-83de-3759d48c9ace@microchip.com> <20240626-fondly-batboy-e99846fd6c45@spud> <20240627-imminent-unmovable-8c3b743c94ca@spud> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3uVSIurMqFrDKnH/" Content-Disposition: inline In-Reply-To: <20240627-imminent-unmovable-8c3b743c94ca@spud> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240627_084502_901055_72EA1201 X-CRM114-Status: GOOD ( 25.56 ) 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: , Cc: robh@kernel.org, conor+dt@kernel.org, arnd@arndb.de, alexandre.belloni@bootlin.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linus.walleij@linaro.org, claudiu.beznea@tuxon.dev, linux-gpio@vger.kernel.org, Durai.ManickamKR@microchip.com, krzk+dt@kernel.org, brgl@bgdev.pl, linux-arm-kernel@lists.infradead.org Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --3uVSIurMqFrDKnH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 27, 2024 at 04:42:24PM +0100, Conor Dooley wrote: > > >>>> +properties: > > >>>> + compatible: > > >>>> + oneOf: > > >>>> + - items: > > >>>> + - enum: > > >>>> + - atmel,at91sam9x5-gpio > > >>>> + - microchip,sam9x60-gpio > > >>>> + - const: atmel,at91rm9200-gpio > > >>>> + - items: > > >>>> + - enum: > > >>>> + - microchip,sam9x7-gpio > > >>>> + - const: microchip,sam9x60-gpio > > >>>> + - const: atmel,at91rm9200-gpio > > >>> It's worth pointing out that this is required, because the driver > > >>> implements a different set of ops for the sam9x60. There's not just= more > > >>> of them, they're different too. > > >>> Are the sam9x60 and at91rm9200 are actually compatible, or is the > > >>> fallback here some mistake that originated in the dts? > > >>> > > >> The PIO3 pinctrl driver uses the compatible "atmel,at91rm9200-gpio" = to > > >> find the number of active GPIO banks and also to differentiate them = =66rom > > >> the pinmux child nodes.The driver probe fails if the at91rm9200 is n= ot > > >> present in the GPIO bank compatible property list. > > >> For sam9x7, "microchip,sam9x60-gpio" is used as the fallback compati= ble > > >> and "atmel,at91rm9200-gpio" is added by default to avoid probe issues > > >> and help find the number of GPIO banks by the driver. > > > That's unfortunately not what I asked. Forget about > > > at91_pinctrl_child_count() for a minute and answer the question again: > > > Are the sam9x60 and at91rm9200 actually compatible? > > >=20 > > > Hints: > > > - Do the registers that are in the at91rm9200 have the same behaviour= in > > > the sam9x60? > > The registers in at91rm9200 have the same behavior as sam9x60 expect=20 > > that the former supports only 2 Peripheral function per pin while=20 > > sam9x60 supports 4. > > > - Are the new registers in sam9x60 optional, so that if all sam9x60 c= ode > > > was deleted from the driver, the driver would still work for the s= ubset > > > of features that the at91rm9200 already supports? > > at91rm9200 function will work for sam9x60 but not up-to its full=20 > > potential.The new registers in sam9x60 for drive-strength, slew-rate,= =20 > > debounce, pull-down will help drive the the current pinmux configs for= =20 > > sam9x60/9x7 board DT. >=20 > Right. The compatible setup makes sense then, just an explanation for > why should go into your commit message. Gah, I forgot to say, with that: Reviewed-by: Conor Dooley Thanks, Conor. --3uVSIurMqFrDKnH/ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZn2I9gAKCRB4tDGHoIJi 0guUAQCBs7A9g0UHPdDI+bwue3lPWbQbqE2EHT1YyfSulcKekwEA/LL+2N1Rx62b muhAOLUh2mn3/jt5goUkBX7NXJi9wwo= =Fs49 -----END PGP SIGNATURE----- --3uVSIurMqFrDKnH/--