[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-sh
Subject:    [RFC DT style 0/4] Device Tree implementation for sh_flctl
From:       Bastian Hecht <hechtb () googlemail ! com>
Date:       2012-04-26 14:00:58
Message-ID: 1335448862-5201-1-git-send-email-hechtb () gmail ! com
[Download RAW message or body]

This is a prototype implementation of a device tree version of the flctl flash \
controller. I thought before posting anything on the mtd list, I get a review first \
at the "arch corner". Patch 3 contains all the stuff I was unable to figure out where \
to put - gpio setup and power domain handling. The controller runs smooth with the \
series booting with DT. So my main concerns are:

 - Do I miss anything important?
 - naming style is ok?
 - will patch 3 become completely unneccessary when DT support grows mature for
   mackerel? 
 - how to handle the evt2irq transformation? Simply supply the result to the device \
tree? (I omitted irqs in my patches)

Thanks,

 Bastian Hecht

Bastian Hecht (4):
  ARM: sh-mobile: Add sh_flctl to sh7372-mackerel device tree
  mtd: sh_flctl: Add device tree support
  Out-of-tree: sh_flctl: Add dirty hardware init code
  mtd: sh_flctl: Initial device tree binding specification

 .../devicetree/bindings/mtd/rmobile-flctl.txt      |   58 ++++++
 arch/arm/boot/dts/sh7372-mackerel.dts              |   36 ++++
 drivers/mtd/nand/sh_flctl.c                        |  207 +++++++++++++++++++-
 3 files changed, 300 insertions(+), 1 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/mtd/rmobile-flctl.txt

-- 
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-sh" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]