linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Savinay Dharmappa <savinay.dharmappa@ti.com>
Cc: amakarov@ru.mvista.com,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-mtd@lists.infradead.org,
	'David Griego' <dgriego@mvista.com>
Subject: Re: [PATCH v2 1/2] mtd: NOR flash driver for OMAP-L137/AM17x
Date: Thu, 18 Nov 2010 15:09:00 +0300	[thread overview]
Message-ID: <4CE5175C.2080505@mvista.com> (raw)
In-Reply-To: <003c01cb8716$ce4bb750$6ae325f0$@dharmappa@ti.com>

Hello.

On 18-11-2010 14:50, Savinay Dharmappa wrote:

>>> OMAP-L137/AM17x has limited number of dedicated EMIFA
>>> address pins, enough to interface directly to an SDRAM.
>>> If a device such as an asynchronous flash needs to be
>>> attached to the EMIFA, then either GPIO pins or a chip
>>> select may be used to control the flash device's upper
>>> address lines.

>>> This patch adds support for the NOR flash on the OMAP-L137/
>>> AM17x user interface daughter board using the latch-addr-flash
>>> MTD mapping driver which allows flashes to be partially
>>> physically addressed. The upper address lines are set by
>>> a board specific code which is a separate patch.

>>      Please add back my signoff, omitted in this version. Some of the code,
>> including a bug fix, was authored by me.

> I'll surely do this. What about your Sign-off on 2/2 patch?

    Already replied.

> Also shall I add
> Aleksey's Sign-off on this patch

    AFAIR, there was his signoff on it, so yes.

> and David's Sign-off on 2/2 patch?

    David didn't touch patch 2/2.

> Thanks,
> Savinay.

WBR, Sergei

      reply	other threads:[~2010-11-18 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12  8:01 [PATCH v2 1/2] mtd: NOR flash driver for OMAP-L137/AM17x Savinay Dharmappa
2010-11-18 11:22 ` Sergei Shtylyov
2010-11-18 11:50   ` Savinay Dharmappa
2010-11-18 12:09     ` Sergei Shtylyov [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=4CE5175C.2080505@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=amakarov@ru.mvista.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=dgriego@mvista.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=savinay.dharmappa@ti.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;
as well as URLs for NNTP newsgroup(s).