From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v2 07/18] drivers: reset: Add STM32 reset driver Date: Tue, 10 Mar 2015 21:21:33 +0100 Message-ID: <2455342.zT71E5iyaL@wuerfel> References: <1424455277-29983-1-git-send-email-mcoquelin.stm32@gmail.com> <2383270.cAJPOxrkvo@wuerfel> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-gpio-owner@vger.kernel.org To: Maxime Coquelin Cc: Uwe =?ISO-8859-1?Q?Kleine=2DK=F6nig?= , Andreas =?ISO-8859-1?Q?F=E4rber?= , Geert Uytterhoeven , Rob Herring , Philipp Zabel , Jonathan Corbet , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Daniel Lezcano , Thomas Gleixner , Linus Walleij , Greg Kroah-Hartman , Jiri Slaby , Andrew Morton , "David S. Miller" , Mauro Carvalho Chehab , Joe Perches , Antti Palosaari , Tejun List-Id: linux-api@vger.kernel.org On Tuesday 10 March 2015 16:44:24 Maxime Coquelin wrote: > 2015-03-10 16:02 GMT+01:00 Arnd Bergmann : > > On Friday 20 February 2015 19:01:06 Maxime Coquelin wrote: > >> +/* AHB1 */ > >> +#define GPIOA_RESET 0 > >> +#define GPIOB_RESET 1 > >> +#define GPIOC_RESET 2 > >> +#define GPIOD_RESET 3 > >> +#define GPIOE_RESET 4 > >> +#define GPIOF_RESET 5 > >> +#define GPIOG_RESET 6 > >> +#define GPIOH_RESET 7 > >> +#define GPIOI_RESET 8 > >> +#define GPIOJ_RESET 9 > >> +#define GPIOK_RESET 10 > >> > > > > As these are just the hardware numbers, it's better to not make the= m > > part of the binding at all. Instead, just document in the binding t= hat > > one is supposed to pass the hardware number as the argument. >=20 > The reset controller is part of the RCC (Reset & Clock Controller) IP= =2E > In this version, I only provided the reset registers to the reset > controller driver, but as per Andreas F=E4rber remark, I should avec = a > single DT node for both the resets and clocks. >=20 > In the next version I am preparing, the defines doesn't look as > trivial as in this version, GPIOA_RESET being 128 for instance. >=20 > Is it fine for you if I keep the defines part of the binding? >=20 >=20 It's always better to avoid these files entirely, as they are a frequent source of merge dependencies, and they make it less obvious what's going on than having binary values in the dtb that make sense. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html