public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@mimc.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Allow AM33xx boards to setup GPMC chipselects.
Date: Mon, 18 Feb 2013 11:27:30 +0000	[thread overview]
Message-ID: <51221022.5030605@mimc.co.uk> (raw)
In-Reply-To: <87ppzxlwc5.fsf@dell.be.48ers.dk>

On 18/02/13 11:01, Peter Korsgaard wrote:
>>>>>> "Mark" == Mark Jackson <mpfj-list@mimc.co.uk> writes:
> 
>  Mark> Expose the enable_gpmc_cs_config() function so AM33xx based boards can register GPMC chip selects.
>  Mark> Changes in V3:
>  Mark> - Fix line wrapping
> 
>  Mark> Changes in V2:
>  Mark> - Indicate this is for AM33xx (not OMAP2)
> 
>  Mark> Signed-off-by: Mark Jackson <mpfj@newflow.co.uk>
>  Mark> ---
>  Mark>  arch/arm/include/asm/arch-am33xx/sys_proto.h |    2 ++
>  Mark>  1 file changed, 2 insertions(+)
> 
>  Mark> diff --git a/arch/arm/include/asm/arch-am33xx/sys_proto.h b/arch/arm/include/asm/arch-am33xx/sys_proto.h
>  Mark> index 588d8de..97ab60d 100644
>  Mark> --- a/arch/arm/include/asm/arch-am33xx/sys_proto.h
>  Mark> +++ b/arch/arm/include/asm/arch-am33xx/sys_proto.h
>  Mark> @@ -35,5 +35,7 @@ void ddr_pll_config(unsigned int ddrpll_M);
>  Mark>   void sdelay(unsigned long);
>  Mark>  void gpmc_init(void);
>  Mark> +void enable_gpmc_cs_config(const u32 *gpmc_config, struct gpmc_cs *cs, u32 base,
>  Mark> +            u32 size);
> 
> Checkpatch still complains. How about wrapping after *cs, and properly
> aligning the next line?
> 

Grrrr ... stupid mailer programs !!

Hopefully v4 is now correct ...

Mark J.

      reply	other threads:[~2013-02-18 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 10:08 [U-Boot] [PATCH v3] Allow AM33xx boards to setup GPMC chipselects Mark Jackson
2013-02-18 11:01 ` Peter Korsgaard
2013-02-18 11:27   ` Mark Jackson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51221022.5030605@mimc.co.uk \
    --to=mpfj-list@mimc.co.uk \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox