public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: linux-mtd@lists.infradead.org, spi-devel-general@lists.sourceforge.net
Cc: olivier.clergeaud@st.com, angus.clark@st.com
Subject: [RFC] New SPI based Serial Flash Controller driver
Date: Mon, 11 Nov 2013 13:48:58 +0000	[thread overview]
Message-ID: <20131111134858.GI22184@lee--X1> (raw)

Hi,

I'm in the process of porting a BSP SPI based Serial Flash Controller
to the latest kernel version with a view to pushing it upstream.

Historically, this driver was based on some basic functionality
pilfered from the m25p80 driver (mainly the device look-up-table and
thelike), but since then has forked into a fully functional driver in
its own right - due to lack of Dual and Quad Mode support in
Mainline. I am under the impression that support for these modes are
due to land shortly, or the patches are at least on the MLs.

The current theory is that we can start to utilise some of the m25p80
driver, which would alleviate a great deal of duplication by our own
driver. We would still be required to add a smallish driver to
intercept the messages to ensure they are written to the controller in
the correct manor.

Can you tell me if there are any other controllers which work in this
way? If there are can you point me to them please? If not, tell me I'm
spouting nonsense and feel free to advice me on the correct method
that these kinds of things should be handled.

Any help will be gratefully received.

Kind regards,
Lee

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

                 reply	other threads:[~2013-11-11 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131111134858.GI22184@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=angus.clark@st.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=olivier.clergeaud@st.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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