[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120403171112.GH19952@sequoia.sous-sol.org>
Date: Tue, 3 Apr 2012 10:11:12 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Wolfram Sang <w.sang@...gutronix.de>
Cc: Chris Wright <chrisw@...s-sol.org>,
Ivo Sieben <meltedpianoman@...il.com>,
linux-kernel@...r.kernel.org, Jean Delvare <khali@...ux-fr.org>,
Kevin Hilman <khilman@...prootsystems.com>
Subject: Re: [PATCH-v3] Support M95040 SPI EEPROM
* Wolfram Sang (w.sang@...gutronix.de) wrote:
> On Tue, Apr 03, 2012 at 09:53:20AM -0700, Chris Wright wrote:
> > * Ivo Sieben (meltedpianoman@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists