From: Chris Wright <chrisw@sous-sol.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
Ivo Sieben <meltedpianoman@gmail.com>,
linux-kernel@vger.kernel.org, Jean Delvare <khali@linux-fr.org>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH-v3] Support M95040 SPI EEPROM
Date: Tue, 3 Apr 2012 10:11:12 -0700 [thread overview]
Message-ID: <20120403171112.GH19952@sequoia.sous-sol.org> (raw)
In-Reply-To: <20120403170708.GC2477@pengutronix.de>
* Wolfram Sang (w.sang@pengutronix.de) wrote:
> On Tue, Apr 03, 2012 at 09:53:20AM -0700, Chris Wright wrote:
> > * Ivo Sieben (meltedpianoman@gmail.com) wrote:
> > > + instr = AT25_READ;
> > > + if (at25->chip.flags & EE_INSTR_BIT3_IS_ADDR)
> > > + if (offset >= (1U << (at25->addrlen * 8)))
> > > + instr |= AT25_INSTR_BIT3;
> > > + *cp++ = instr;
> > <snip>
> > > + /*
> > > + * Certain EEPROMS have a size that is larger than the number of address
> > > + * bytes would allow (e.g. like M95040 from ST that has 512 Byte size
> > > + * but uses only one address byte (A0 to A7) for addressing.) For
> > > + * the extra address bit (A8, A16 or A24) bit 3 of the instruction byte
> > > + * is used. This instruction bit is normally defined as don't care for
> > > + * other AT25 like chips.
> > > + */
> > > +#define EE_INSTR_BIT3_IS_ADDR 0x0010
> >
> > Is there some guarantee that this chip flag will always have this
> > meaning?
>
> ? This is a driver flag.
Sorry, I don't see it set anywhere, so unclear on where it comes from.
I thought it was from a generic spi probe.
thanks,
-chris
next prev parent reply other threads:[~2012-04-03 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 6:25 [PATCH-v3] Support M95040 SPI EEPROM Ivo Sieben
2012-04-03 16:46 ` Wolfram Sang
2012-04-03 16:53 ` Chris Wright
2012-04-03 17:07 ` Wolfram Sang
2012-04-03 17:11 ` Chris Wright [this message]
2012-04-03 17:17 ` Wolfram Sang
2012-04-04 7:21 ` Ivo Sieben
2012-04-04 7:59 ` Wolfram Sang
2012-04-05 15:11 ` Ivo Sieben
2012-04-05 16:43 ` Greg KH
2012-04-06 8:16 ` Remy Bohmer
2012-04-06 18:22 ` Wolfram Sang
2012-04-17 14:43 ` Ivo Sieben
2012-04-17 20:47 ` Greg KH
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=20120403171112.GH19952@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=khali@linux-fr.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meltedpianoman@gmail.com \
--cc=w.sang@pengutronix.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.