public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Wagner <david.wagner@free-electrons.com>
To: David Wagner <david.wagner@free-electrons.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 1/2] Macro for getting the BASEADDRESS field in omap's gpmc configuration
Date: Thu, 11 Aug 2011 17:00:23 +0200	[thread overview]
Message-ID: <4E43EE87.8050900@free-electrons.com> (raw)
In-Reply-To: <1312470395-19672-1-git-send-email-david.wagner@free-electrons.com>

	Hi,

On 08/04/2011 05:06 PM, David Wagner wrote:
> BASEADDRESS is located in the 6 lower bits of the CONFIG7 register.
> See OMAP 35x Technical Reference Manual, p. 1169.
> 
> Signed-off-by: David Wagner <david.wagner@free-electrons.com>

I'm not subscribed to the linux-omap mailing list but I saw no answer on
this patch and the next one in the archive.

The second one (replaces bitwise operations in board-igep0020.c with
GPMC macros) partly depends on the first one, but can be split so that
part of it can be standalone. Should I do so and resubmit or is it ok
like this ?

Regards,
David.

-- 
David Wagner, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2011-08-11 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 15:06 [PATCH 1/2] Macro for getting the BASEADDRESS field in omap's gpmc configuration David Wagner
2011-08-04 15:06 ` [PATCH 2/2] Use existing GPMC macros instead of bit manipulation David Wagner
2011-08-04 15:15   ` David Wagner
2011-08-11 15:00 ` David Wagner [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=4E43EE87.8050900@free-electrons.com \
    --to=david.wagner@free-electrons.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.com \
    /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