[PATCHv2 2/6] rtc: rtc-m48t86: add hooks to support driver side memory mapping

- amend the {read,write}byte driver functions to use u8 Signed-off-by: Alexander Clouter --- drivers/rtc/rtc-m48t86.c | 230 ++ 1 file changed, 173 insertions(+), 57 deletions(-) diff --git a/drivers/rtc/rtc-m48t86.c b/drivers/rtc/rtc-m48t86.c in

Re: [PATCH 2/6] rtc: rtc-m48t86: add hooks to support driver side memory mapping

On Tue, Apr 02, 2013 at 10:36:43AM +1100, Ryan Mallon wrote: On 02/04/13 10:22, Alexander Clouter wrote: If platform_data is not defined (as before), then named memory io ranges need to be defined ("rtc_index" and "rtc_data"). The driver then maps those regions and uses t

[PATCH 6/6] rtc: rtc-m48t86: add devicetree bindings

Add devicetree bindings (and documentation) for rtc-m48t86. Signed-off-by: Alexander Clouter --- Documentation/devicetree/bindings/rtc/rtc-m48t86.txt | 17 + drivers/rtc/rtc-m48t86.c | 12 ++-- 2 files changed, 27 insertions(+), 2

[PATCH 5/6] arm: ep93xx: move ts72xx to use rtc-m48t86 driver side memory interface

Remove platform_data hooks into rtc-m48t86 and use named resource regions. Signed-off-by: Alexander Clouter --- arch/arm/mach-ep93xx/ts72xx.c | 38 +++--- 1 file changed, 7 insertions(+), 31 deletions(-) diff --git a/arch/arm/mach-ep93xx/ts72xx.c b/arch/arm

[PATCH 4/6] arm: orion5x: move ts78xx to use rtc-m48t86 driver side memory interface

Remove platform_data hooks into rtc-m48t86 and use named resource regions. Signed-off-by: Alexander Clouter --- arch/arm/mach-orion5x/ts78xx-setup.c | 78 -- 1 file changed, 17 insertions(+), 61 deletions(-) diff --git a/arch/arm/mach-orion5x/ts78xx-setup.c b

[PATCH 3/6] rtc: rtc-m48t86: add detect method for RTC

The m48t86 has 114 bytes of user space available, so we can use this space to detect for the presence of the RTC. Signed-off-by: Alexander Clouter --- drivers/rtc/rtc-m48t86.c | 43 +++ 1 file changed, 43 insertions(+) diff --git a/drivers/rtc/rtc

[PATCH 2/6] rtc: rtc-m48t86: add hooks to support driver side memory mapping

path affected myself: drivers/rtc/rtc-m48t86.c: In function ‘m48t86_rtc_probe’: drivers/rtc/rtc-m48t86.c:180: warning: ‘res_index’ may be used uninitialized in this function drivers/rtc/rtc-m48t86.c:180: warning: ‘res_data’ may be used uninitialized in this function ---- Signed-off-b

[PATCHv2 0/6] add devicetree bindings for rtc-m48t86

into rtc-m48t86.c * converts both ts7[28]xx to use the new interface * enable devicetree hooks and include documentation Alexander Clouter (6): rtc: rtc-m48t86: move m48t86.h to platform_data rtc: rtc-m48t86: add hooks to support driver side memory mapping rtc: rtc-m48t86: add detect metho

[PATCH 1/6] rtc: rtc-m48t86: move m48t86.h to platform_data

The header for the rtc-m48t86 platform-data should be in include/linux/platform_data. Signed-off-by: Alexander Clouter --- arch/arm/mach-ep93xx/ts72xx.c |2 +- arch/arm/mach-orion5x/ts78xx-setup.c |2 +- drivers/rtc/rtc-m48t86.c

Re: [PATCH 0/3] add devicetree bindings for rtc-m48t86

On Tue, Apr 02, 2013 at 08:44:10AM +1100, Ryan Mallon wrote: On 01/04/13 08:56, Alexander Clouter wrote: Currently there are two users of rtc-m48t86 (mach-ep93xx/ts72xx.c and mach-orion5x/ts78xx-setup.c) and both just use {read,write}b against a memory mapped region. As I am devicetree'in

[PATCH 2/3] arm: orion5x: fixup ts78xx to be able to use the rtc-m48t86 again.

This patch fixes the board to be able to use the rtc-m48t86 driver again. Signed-off-by: Alexander Clouter --- arch/arm/mach-orion5x/ts78xx-setup.c | 79 -- 1 file changed, 18 insertions(+), 61 deletions(-) diff --git a/arch/arm/mach-orion5x/ts78xx-setup.c b

[PATCH 1/3] rtc: rtc-m48t86: add devicetree bindings

This patch allows rtc-m48t86 to be used via devicetree. Signed-off-by: Alexander Clouter --- .../devicetree/bindings/rtc/rtc-m48t86.txt | 17 ++ drivers/rtc/rtc-m48t86.c | 254 +++- include/linux/m48t86.h | 16

[PATCH 3/3] arm: ep93xx: fixup ts72xx to be able to use the rtc-m48t86 again.

This patch fixes the board to be able to use the rtc-m48t86 driver again. Signed-off-by: Alexander Clouter --- arch/arm/mach-ep93xx/ts72xx.c | 29 - 1 file changed, 8 insertions(+), 21 deletions(-) diff --git a/arch/arm/mach-ep93xx/ts72xx.c b/arch/arm/mach-ep93xx

[PATCH 0/3] add devicetree bindings for rtc-m48t86

umentation Awkward step, the first patch breaks both boards, the two following patches fix them. Happy to re-work this if folks give me a pointer on how to do this in an acceptable way. My vote is to break fast, fix fast, spend the time writing other code :) Signed-off-by: Alexander Clouter Alexand

Re: plat-nand DT support

h easier for you to get support and answers if you try to upstream. This is what I am trying to do. I am currently trying to port my board arch/arm/mach-orion5x/ts78xx-setup.c (that I am the maintainer for) to DT, the github page is just where I do development on. Cheers, and thanks again fo

Re: plat-nand DT support

Any comments...anyone? On Sun, Mar 03, 2013 at 03:52:26PM +, Alexander Clouter wrote: I have been busy porting an ARM board (that uses plat_nand) to devicetree and stumbled on John Crispin's patch from last year[1]. There was not much online about how to use it, so I went

plat-nand DT support

http://lists.infradead.org/pipermail/linux-mtd/2012-April/041025.html [2] could also support the NAND used by arch/arm/mach-ep93xx/ts72xx.c but the whole SoC has not been ported to DT -- Alexander Clouter .sigmonster says: How many weeks are there in a light year? diff --git a/Documentation/devicetree/bindings/mtd