All of lore.kernel.org
 help / color / mirror / Atom feed
From: jteki at openedev.com <jteki@openedev.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND 1/2] stm32: stm32f4: move flash driver to mtd driver location
Date: Thu, 10 Mar 2016 00:01:31 -0500	[thread overview]
Message-ID: <6b6ce923f1664b2591fe74f121e44dfc@openedev.com> (raw)
In-Reply-To: <9B6E6443-7AC3-4650-8885-CB3B1A1C79FD@st.com>

On 2016-03-09 23:18, Vikas MANOCHA wrote:
> Hi Jagan ,
> 
>> On Mar 9, 2016, at 6:53 PM, Jagan Teki <jteki@openedev.com> wrote:
>> 
>>> On Thursday 10 March 2016 04:48 AM, Vikas Manocha wrote:
>>> Same flash driver can be used by other stm32 families like stm32f7.
>>> Better place for this driver would be mtd driver location.
>> 
>> What kind of flash is it, parallel or serial NOR?
> 
> It is embedded 256 bit NOR flash.

OK, I thought it's similar to SST25L.

Can't we detect this through cfi_flash framework?

--
Jagan.

  reply	other threads:[~2016-03-10  5:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 23:18 [U-Boot] [RESEND 1/2] stm32: stm32f4: move flash driver to mtd driver location Vikas Manocha
2016-03-09 23:18 ` [U-Boot] [RESEND 2/2] stm32f746-disco: enable flash support Vikas Manocha
2016-03-27 22:23   ` [U-Boot] [U-Boot, RESEND, " Tom Rini
2016-03-10  2:52 ` [U-Boot] [RESEND 1/2] stm32: stm32f4: move flash driver to mtd driver location Jagan Teki
2016-03-10  4:18   ` Vikas MANOCHA
2016-03-10  5:01     ` jteki at openedev.com [this message]
2016-03-10 17:41       ` Vikas MANOCHA
2016-03-10 17:46         ` Jagan Teki
2016-03-10 17:52           ` Vikas MANOCHA
2016-03-10 17:58             ` Jagan Teki
2016-03-10 18:17               ` Vikas MANOCHA
2016-03-10 18:38                 ` Jagan Teki
2016-03-21 21:53                   ` Vikas MANOCHA
2016-03-27 22:23 ` [U-Boot] [U-Boot, RESEND, " Tom Rini

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=6b6ce923f1664b2591fe74f121e44dfc@openedev.com \
    --to=jteki@openedev.com \
    --cc=u-boot@lists.denx.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.