linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 08/10] mtd: st_spi_fsm: Provide documentation for boot device mask property
Date: Thu, 22 May 2014 12:24:06 +0100	[thread overview]
Message-ID: <1400757848-18075-9-git-send-email-lee.jones@linaro.org> (raw)
In-Reply-To: <1400757848-18075-1-git-send-email-lee.jones@linaro.org>

The system configuration registers which display which device the system
booted on are in the same place on all boards which support the FSM.
However, the bits do shift every so slightly.  To combat these we're
adding a new property which supplies the necessary mask used to abstract
the required information.

Cc: devicetree at vger.kernel.org
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
 Documentation/devicetree/bindings/mtd/st-fsm.txt | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/st-fsm.txt b/Documentation/devicetree/bindings/mtd/st-fsm.txt
index c248939..0523fd4 100644
--- a/Documentation/devicetree/bindings/mtd/st-fsm.txt
+++ b/Documentation/devicetree/bindings/mtd/st-fsm.txt
@@ -11,6 +11,8 @@ Optional properties:
   - st,syscfg          : Phandle to boot-device system configuration registers
   - st,boot-device-reg : Address of the aforementioned boot-device register(s)
   - st,boot-device-spi : Expected boot-device value if booted via this device
+  - st,boot-device-msk : Mask to use when extracting boot device from the
+			 above system config registers
 
 Example:
 	spifsm: spifsm at fe902000{
-- 
1.8.3.2

  parent reply	other threads:[~2014-05-22 11:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 11:23 [PATCH v2 00/10] mtd: st_spi_fsm: Align with ST's internal development Lee Jones
2014-05-22 11:23 ` [PATCH 01/10] mtd: st_spi_fsm: Extend fsm_clear_fifo to handle unwanted bytes Lee Jones
2014-05-22 11:24 ` [PATCH 02/10] mtd: st_spi_fsm: Obtain and use EMI clock if provided Lee Jones
2014-05-22 11:24 ` [PATCH 03/10] mtd: st_spi_fsm: Add support for Micron N25Q512A Lee Jones
2014-05-22 11:24 ` [PATCH 04/10] mtd: st_spi_fsm: Add support for N25Q512 and N25Q00A devices Lee Jones
2014-05-22 11:24 ` [PATCH 05/10] mtd: st_spi_fsm: Update the JEDEC probe to handle extended READIDs Lee Jones
2014-05-22 11:24 ` [PATCH 06/10] mtd: st_spi_fsm: Update Spansion device entries Lee Jones
2014-05-22 11:24 ` [PATCH 07/10] mtd: st_spi_fsm: Improve busy wait handling Lee Jones
2014-05-22 11:24 ` Lee Jones [this message]
2014-05-22 11:59   ` [PATCH v2 08/10] mtd: st_spi_fsm: Provide documentation for boot device mask property Lee Jones
2014-05-22 11:24 ` [PATCH 09/10] mtd: st_spi_fsm: Provide mask to obtain correct boot device pins Lee Jones
2014-05-22 11:47   ` Arnd Bergmann
2014-05-22 11:52     ` Lee Jones
2014-05-22 11:53       ` Arnd Bergmann
2014-05-22 11:56   ` [PATCH v2 " Lee Jones
2014-05-22 11:58     ` Lee Jones
2014-05-22 11:24 ` [PATCH 10/10] mtd: st_spi_fsm: General tidy-up Lee Jones

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=1400757848-18075-9-git-send-email-lee.jones@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).