All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: add lock fixup for AT49BV640D and AT49BV640DT chips
Date: Tue, 3 Nov 2009 08:44:33 +0100	[thread overview]
Message-ID: <20091103084433.7bc4d9fb@hcegtvedt.norway.atmel.com> (raw)
In-Reply-To: <1257231914.21596.39.camel@localhost>

On Tue, 03 Nov 2009 09:05:14 +0200
Artem Bityutskiy <dedekind1@gmail.com> wrote:

<snipp Atmel AT49BV640D(T) powerup lock fixup patch>

> >  static void fixup_use_write_buffers(struct mtd_info *mtd, void *param)
> >  {
> >  	struct map_info *map = mtd->priv;
> > @@ -313,6 +319,8 @@ static struct cfi_fixup fixup_table[] = {
> >  	 * we know that is the case.
> >  	 */
> >  	{ CFI_MFR_ANY, CFI_ID_ANY, fixup_use_point, NULL },
> > +	{ CFI_MFR_ATMEL, AT49BV640D, fixup_use_at49bv640dx_lock, NULL },
> > +	{ CFI_MFR_ATMEL, AT49BV640DT, fixup_use_at49bv640dx_lock, NULL },
> >  	{ 0, 0, NULL, NULL }
> >  };
> 
> Why you add this to the fixup_table, not cfi_fixup_table?
> 

It would probably be more appropriate to place it after the first Atmel
fixup in the cfi_fixup_table, yes.

Really unsure why I ended up putting it in the fixup_table, because I
used the fixup_unlock_powerup_lock as reference.

It is probably more correct that I set the FeatureSupport 0x20 (32)
feature to indicate that the flash has "Instant block lock". I'll
submit a v2 for the latter unless you have some other feedback?

-- 
Best regards,
Hans-Christian Egtvedt

  reply	other threads:[~2009-11-03  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 12:05 [PATCH] mtd: add lock fixup for AT49BV640D and AT49BV640DT chips Hans-Christian Egtvedt
2009-11-03  7:05 ` Artem Bityutskiy
2009-11-03  7:44   ` Hans-Christian Egtvedt [this message]
2009-11-03  7:47     ` Artem Bityutskiy

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=20091103084433.7bc4d9fb@hcegtvedt.norway.atmel.com \
    --to=hans-christian.egtvedt@atmel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.