Premi, Sanjeev wrote:
> [sp] Actually, I realized that PATCH 1 in the series depends upon:
> http://marc.info/?l=u-boot&m=131515805732292&w=2
>
> I had mentioned 2 patches in the cover letter. Of the two,
> one is already included in u-boot-arm/master. This one is
> still no
gpio: Use generic API
> (instead of custom)
> > -Original Message-
> > From: Luca Ceresoli [mailto:luca.ceres...@comelit.it]
> > Sent: Wednesday, September 07, 2011 2:54 PM
> > To: Premi, Sanjeev
> > Cc: u-boot@lists.denx.de
> > Subject: Re: [U-Boot] [PA
> -Original Message-
> From: Luca Ceresoli [mailto:luca.ceres...@comelit.it]
> Sent: Wednesday, September 07, 2011 2:54 PM
> To: Premi, Sanjeev
> Cc: u-boot@lists.denx.de
> Subject: Re: [U-Boot] [PATCH 0/3] omap: gpio: Use generic API
> (instead of custom)
>
&g
Hi Sanjeev,
Sanjeev Premi wrote:
> The OMAP boards use a custom api for GPIO operations. While
> it works, it doesn't help when when we don't know existence
> of the customization.
...
> Changes since RFC[1]:
> 1) While the original RFC was based against the master of
> u-boot.git. This ser
>
> Sanjeev Premi (3):
> omap: gpio: Use generic API
> omap: gpio: generic changes after changing API
> omap: gpio: Adapt board files to use generic API
>
> arch/arm/cpu/armv7/omap-common/gpio.c | 113
> -
> arch/arm/cpu/armv7/omap4/clocks.c |5 +
The OMAP boards use a custom api for GPIO operations. While
it works, it doesn't help when when we don't know existence
of the customization.
I earlier encountered the problem when looking for GPIO
related changes when submitting prev set of patches. Since
the search for gpio_request() in omap sou
6 matches
Mail list logo
