All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@newflow.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 3/4] ARM: AM33xx: Move s_init to a common place
Date: Wed, 21 Aug 2013 16:51:12 +0100	[thread overview]
Message-ID: <5214E1F0.2050800@newflow.co.uk> (raw)
In-Reply-To: <51F76C68.2050602@denx.de>

On 30/07/13 08:34, Heiko Schocher wrote:
> Hello Lokesh,
> 
> Am 30.07.2013 07:18, schrieb Lokesh Vutla:
>> From: Heiko Schocher<hs@denx.de>
>>
>> s_init has the same outline for all the AM33xx based
>> board. So making it generic.
>> This also helps in addition of new Soc with minimal changes.

There's a new function now defined ...

void enable_norboot_pin_mux(void)

... but our board *always* boots via NOR.  All the required
pinmux config is handled by enable_board_pin_mux().

Should I just define this an empty function ?

Or should it be a "maybe unused" function ?

Mark J.

  reply	other threads:[~2013-08-21 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  5:18 [U-Boot] [PATCH V2 0/4]ARM: AM33xx: Cleanup clocks and hwinit Lokesh Vutla
2013-07-30  5:18 ` [U-Boot] [PATCH V2 1/4] ARM: AM33xx: Cleanup dplls data Lokesh Vutla
2013-07-30  7:33   ` Heiko Schocher
2013-07-30  5:18 ` [U-Boot] [PATCH V2 2/4] ARM: AM33xx: Cleanup clocks layer Lokesh Vutla
2013-07-30  7:33   ` Heiko Schocher
2013-07-30  5:18 ` [U-Boot] [PATCH V2 3/4] ARM: AM33xx: Move s_init to a common place Lokesh Vutla
2013-07-30  7:34   ` Heiko Schocher
2013-08-21 15:51     ` Mark Jackson [this message]
2013-08-21 16:26       ` Tom Rini
2013-08-23  9:28   ` Mark Jackson
2013-08-23 10:25     ` Lokesh Vutla
2013-08-23 10:55       ` Mark Jackson
2013-08-28 12:58         ` Mark Jackson
2013-07-30  5:18 ` [U-Boot] [PATCH V2 4/4] musb: Disable extra prints Lokesh Vutla
2013-07-30  7:34   ` Heiko Schocher
2013-08-16 13:34 ` [U-Boot] [PATCH V2 0/4]ARM: AM33xx: Cleanup clocks and hwinit Tom Rini

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=5214E1F0.2050800@newflow.co.uk \
    --to=mpfj-list@newflow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.