...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/id.c | 25 +++--
arch/arm/mach-omap2/soc.h |8 ++--
2 files changed, 9 insertions(+), 24 deletions(-)
diff --git a/arch/arm/mach-omap2/id.c b
...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Acked-by: Nishanth Menon n...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/id.c | 25 +++--
arch/arm/mach-omap2/soc.h |8 ++--
2
lost
while resuming.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/input/keyboard/gpio_keys.c | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/gpio_keys.c
b/drivers/input/keyboard/gpio_keys.c
index
-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/input/keyboard/gpio_keys.c | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/drivers/input/keyboard/gpio_keys.c
b/drivers/input/keyboard/gpio_keys.c
index 62bfce4..aa49aef 100644
--- a/drivers
The flag mask are incorrect, so fix it.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/prcm.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/prcm.c b/arch/arm/mach-omap2/prcm.c
index 0f51e03..dc45156 100644
The address of PRM_RSTST register and flag mask are incorrect,
so fix it.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/prcm.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/prcm.c b/arch/arm/mach-omap2/prcm.c
index
According to TRMs the assigned shifts are wrong, so correct them.
---
arch/arm/mach-omap2/prm44xx.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/prm44xx.h b/arch/arm/mach-omap2/prm44xx.h
index 22b0979..8ee1fbd 100644
---
According to TRMs the assigned shifts are wrong, so correct them.
---
arch/arm/mach-omap2/prm44xx.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/prm44xx.h b/arch/arm/mach-omap2/prm44xx.h
index 22b0979..8ee1fbd 100644
---
To read reset sources registers we have to use PRM_DEVICE_INST
---
arch/arm/mach-omap2/prm44xx.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index 7498bc7..0b61b8d 100644
--- a/arch/arm/mach-omap2/prm44xx.c
In the map for reset sources register we use defines intended for
using with PRM_RSTCTRL register. So fix it.
---
arch/arm/mach-omap2/prm44xx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index
In the map for reset sources register we use defines intended for
using with PRM_RSTCTRL register. So fix it.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/prm44xx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2
To read reset sources registers we have to use PRM_DEVICE_INST
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/prm44xx.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/prm44xx.c b/arch/arm/mach-omap2/prm44xx.c
index
From: Nishanth Menon n...@ti.com
RSTTIME is offset 0x8 and RSTST is offset 0x04 for OMAP4430 and
OMAP4460.
Signed-off-by: Nishanth Menon n...@ti.com
[ivan.khoronz...@ti.com: ported from k3.4]
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/mach-omap2/prm44xx.h |4 ++--
1
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
The keystone arch uses the same IP watchdog, so add ti,keystone-wdt
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Some SoCs, like Keystone 2, can support more than one WDT and each
watchdog device has to use it's own base address, clock source,
watchdog device, so add new davinci_wdt_device structure to hold
device data.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar
watchdog entry
replaced ti,keystone-wdt compatible on
ti,keystone-wdt,ti,davinci-wdt
Ivan Khoronzhuk (6):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog: davinci: add GET_TIMELEFT
it in
order to set timeout period.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
---
arch/arm/mach-davinci/da8xx-dt.c |2 +-
arch/arm/mach-davinci/devices-da8xx.c |4 +-
arch
The keystone arch uses the same IP watchdog, so add ti,keystone-wdt
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh
Add watchdog entry to keystone device tree.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Guenter Roeck li...@roeck-us.net
---
arch/arm/boot/dts/keystone.dtsi |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/keystone.dtsi b/arch/arm/boot/dts
and bus width.
It is done by AEMIF driver.
To get rid of davinci-nand driver dependency on aemif platform code
we moved aemif code to davinci platform.
The platform AEMIF code (aemif.c) has to be removed once Davinci
will be converted to DT and use ti-aemif.c driver.
Signed-off-by: Ivan Khoronzhuk
it in
order to set timeout period.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/watchdog/Kconfig |2 +
drivers/watchdog/davinci_wdt.c | 147
li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/watchdog/davinci-wdt.txt | 12 ++--
drivers/watchdog/Kconfig |4 ++--
drivers/watchdog/davinci_wdt.c |2 +-
3 files changed, 13
...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/watchdog/davinci_wdt.c | 74 ++--
1 file changed, 48 insertions(+), 26 deletions(-)
diff --git a/drivers/watchdog/davinci_wdt.c b/drivers/watchdog/davinci_wdt.c
index 9595e70..2d46c43
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
merged with above patch
Ivan Khoronzhuk (5):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog: davinci: add GET_TIMELEFT option support
watchdog: davinci: add timeout-sec property
watchdog: davinci: reuse
As we switch to use the watchdog core which permits more than one
active watchdog in the system, rename platform driver to
davinci-wdt to be identifiable.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
based on:
https://lkml.org/lkml/2013/11/27/164
CC:
Sekhar Nori nsek...@ti.com
davinci_ntosd2_nandflash_device was renamed
to ntosd2_nandflash as requested by Sekhar Nori, because after
adding changes the line is so broken that its almost unreadable.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
v2..v1:
- enabled AEMIF clock
- removed EXPORT_SYMBOL(davinci_aemif_setup
it in
order to set timeout period.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/watchdog/Kconfig |2 +
drivers/watchdog/davinci_wdt.c | 152 ++--
2 files changed, 39 insertions
: reuse driver for keystone arch
use consistent formatting
- watchdog: davinci: add clocks property
merged with above patch
Ivan Khoronzhuk (6):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/watchdog/davinci_wdt.c | 26
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
.../devicetree/bindings/watchdog/davinci
Add watchdog entry to keystone device tree.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Guenter Roeck li...@roeck-us.net
---
arch/arm/boot/dts/keystone.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/keystone.dts b/arch/arm/boot/dts
The keystone arch use the same IP watchdog, so add ti,keystone-wdt
compatible and correct identity.
The Keystone arch is using clocks in DT and source clock for watchdog
has to be specified, so add this to binding.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar
Some SoCs, like Keystone 2, can support more than one WDT and each
watchdog device has to use it's own base address, clock source,
watchdog device, so add new davinci_wdt_device structure to hold
device data.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar
The property ti,davinci-chipselect is required. So we have to check
if it is set.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/nand/davinci_nand.c
Move bindings under mtd. Do this in order to make davinci-nand
driver usable by keystone architecture.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
.../devicetree/bindings/arm/davinci/nand.txt | 46
to be made with core mechanism.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/mtd/nand/davinci_nand.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/nand
In case when memory allocation is failed the driver should return
ENOMEM instead of ENODEV.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/davinci_nand.c b
Extend bindings for davinci_nand driver to be more clear.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/mtd/davinci-nand.txt | 77 ++--
1 file changed, 54 insertions(+), 23 deletions(-)
diff --git a/Documentation/devicetree/bindings
The properties davinci-ecc-mode, davinci-nand-use-bbt, davinci-nand-buswidth
are MTD generic. Correct names for them are: nand-ecc-mode, nand-on-flash-bbt,
nand-bus-width accordingly. So rename them in dts and documentation.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
There is not needed to use a lot of names for err handling.
It complicates code support and reading.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/mtd/nand/davinci_nand.c | 46 +++
1
This series contains fixes and updates of Davinci nand driver, in
order to prepare it to be reused for Keystone platform.
V1:
https://lkml.org/lkml/2013/11/11/352
Ivan Khoronzhuk (7):
mtd: nand: davinci: fix driver registration
mtd: nand: davinci: return ENOMEM if memory allocation is failed
These patches introduce Async External Memory Interface (EMIF16/AEMIF)
controller driver for Davinci/Keystone archs.
V1:
https://lkml.org/lkml/2013/11/11/352
Ivan Khoronzhuk (2):
memory: ti-aemif: introduce AEMIF driver
memory: ti-aemif: add bindings for AEMIF driver
.../bindings/memory
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../bindings/memory-controllers/ti-aemif.txt | 198
1 file changed, 198 insertions(+)
create mode 100644
Documentation/devicetree/bindings/memory
-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/memory/Kconfig| 11 ++
drivers/memory/Makefile |1 +
drivers/memory/ti-aemif.c | 415
cannot request it twice, just ioremap.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
---
drivers/mtd/nand/davinci_nand.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/nand/davinci_nand.c b
://lkml.org/lkml/2013/11/11/352
Ivan Khoronzhuk (3):
mtd: nand: davinci: reuse driver for Keystone arch
mtd: nand: davinci: don't set timings if AEMIF is used
mtd: nand: davinci: don't request AEMIF address range
.../devicetree/bindings/mtd/davinci-nand.txt |8 +--
drivers/mtd/nand
.
It is done by AEMIF driver (drivers/memory/ti-aemfi.c).
The timings code has to be removed together with Davinci aemif
platform code (aemif.c), once Davinci will be converted to DT and use
ti-aemif.c driver.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c
The Keystone arch has compatible nand device, so reuse it.
In case with Keystone it depends on TI_AEMIF because AEMIF
driver is responsible to set timings.
See http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/mtd
These patches introduce Async External Memory Interface (EMIF16/AEMIF)
controller driver for Davinci/Keystone archs.
v1..v2:
- added ti.cs-chipselect property instead to represent chipselect
number in cs node name.
Ivan Khoronzhuk (2):
memory: ti-aemif: introduce AEMIF driver
memory: ti
-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf
Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/memory/Kconfig| 11 ++
drivers/memory/Makefile |1 +
drivers/memory/ti-aemif.c | 415
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../bindings/memory-controllers/ti-aemif.txt | 201
1 file changed, 201 insertions(+)
create mode 100644
Documentation/devicetree/bindings/memory
to be made with core mechanism.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
---
drivers/mtd/nand/davinci_nand.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
://lkml.org/lkml/2013/11/20/315
Ivan Khoronzhuk (10):
mtd: nand: davinci: fix driver registration
mtd: nand: davinci: return ENOMEM if memory allocation is failed
mtd: nand: davinci: check required ti,davinci-chipselect property
mtd: nand: davinci: simplify error handling
mtd: nand: davinci
driver for keystone arch
use consistent formatting
- watchdog: davinci: add clocks property
merged with above patch
Ivan Khoronzhuk (5):
watchdog: davinci: change driver to use WDT core
watchdog: davinci: use davinci_wdt_device structure to hold device
data
watchdog
...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/watchdog/davinci_wdt.c | 74 ++--
1 file changed, 48 insertions(+), 26 deletions(-)
diff --git a/drivers/watchdog/davinci_wdt.c b/drivers/watchdog/davinci_wdt.c
index 3701f06
li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/watchdog/davinci-wdt.txt | 12 ++--
drivers/watchdog/Kconfig |4 ++--
drivers/watchdog/davinci_wdt.c |2 +-
3 files changed, 13
it in
order to set timeout period.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/watchdog/Kconfig |1 +
drivers/watchdog/davinci_wdt.c | 147
Since Davinci WDT has been switched to use WDT core, it became able
to support timeout-sec property, so add it to it's binding description.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
Currently, the davinci watchdog can be read while counting,
so we can add ability to report the remaining time before
the system will reboot.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
it in
order to set timeout period.
Davinci WDT can't be stopped and once it's expired - it can be
rearmed only after hardware reset, that's why nowayout feature
is enforced.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Ivan
Extend bindings for davinci_nand driver to be more clear.
This is clarification only, without semantic changes.
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/mtd
to be made with core mechanism.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |3 ++-
1 file
-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/mtd/davinci-nand.txt | 25
drivers/mtd/nand/davinci_nand.c| 11 ++---
2 files changed, 28 insertions(+), 8 deletions(-)
diff --git
cannot request it twice, just ioremap.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |8 +---
1
Move bindings under mtd. Do this in order to make davinci-nand
driver usable by keystone architecture.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk
There is not needed to use a lot of names for err handling.
It complicates code support and reading.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz
changeset description
- mtd: nand: davinci: reuse driver for Keystone arch
removed ti,keystone-nand compatible from driver
Ivan Khoronzhuk (9):
mtd: nand: davinci: fix driver registration
mtd: nand: davinci: return ENOMEM if memory allocation is failed
mtd: nand: davinci: check
In case when memory allocation is failed the driver should return
ENOMEM instead of ENODEV.
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |5 -
1
The property ti,davinci-chipselect is required. So we have to check
if it is set.
Reviewed-by: Grygorii Strashko grygorii.stras...@ti.com
Reviewed-by: Taras Kondratiuk ta...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/mtd/nand/davinci_nand.c |3 +++
1 file
...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../devicetree/bindings/mtd/davinci-nand.txt |8 +---
drivers/mtd/nand/Kconfig |6 +++---
2 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings
nsek...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
v3..v2:
- rebased on following patch series:
[PATCH v3 0/9] Reuse davinci-nand driver for Keystone arch
http://www.spinics.net/lists/arm-kernel/msg291723.html
- removed AEMIF setup from next boards:
arch
The domain register range for clkfftc1 has to be 0x0235004c
instead of 0x023504c0.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi
b/arch/arm/boot
The control register range for clktsio interferes with clkaemifspi clock.
And it causes issues for NAND/AEMIF. So fix it.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
Only comment is corrected.
arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion
-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/memory/Kconfig| 11 ++
drivers/memory/Makefile | 1 +
drivers/memory/ti-aemif.c | 427 ++
3 files changed, 439 insertions(+)
create mode 100644 drivers/memory/ti-aemif.c
diff --git
to it,
as result we can't encode CS number in reg for AEMIF child devices
(NAND/NOR/etc), as it will break bindings compatibility.
In this patch, NAND node is used just as an example of child node.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
in cs node name.
Ivan Khoronzhuk (2):
memory: ti-aemif: introduce AEMIF driver
memory: ti-aemif: add bindings for AEMIF driver
.../bindings/memory-controllers/ti-aemif.txt | 210 ++
drivers/memory/Kconfig | 11 +
drivers/memory/Makefile
probably you should apply this change to k2l-clocks.dtsi too.
--
Regards,
Ivan Khoronzhuk
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Enable reset driver support in order to have opportunity
to reboot SoC by watchdog and by software.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
CC: Russell King li...@arm.linux.org.uk
CC: Santosh Shilimkar santosh.shilim...@ti.com
arch/arm/configs/keystone_defconfig | 3 +++
1
to use.
So add keystone reset driver to handle all this stuff.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
CC: Dmitry Eremin-Solenikov dbarysh...@gmail.com
CC: David Woodhouse dw...@infradead.org
CC: Grant Likely grant.lik...@linaro.org
CC: Rob Herring robh...@kernel.org
drivers
Remove reset stuff in flavour of using keystone reset driver:
driver/power/reset/keystone-reset.c
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
CC: Santosh Shilimkar santosh.shilim...@ti.com
CC: Russell King li...@arm.linux.org.uk
arch/arm/mach-keystone/keystone.c | 35
...@codeaurora.org
CC: Rob Landley r...@landley.net
CC: Santosh Shilimkar santosh.shilim...@ti.com
CC: Russell King li...@arm.linux.org.uk
Ivan Khoronzhuk (5):
Power: reset: keystone-reset: introduce keystone reset driver
Power: reset: add bindings for keystone reset driver
ARM: keystone: remove
or not.
Additionally soft or hard reset can be configured.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
CC: Rob Herring robh...@kernel.org
CC: Pawel Moll pawel.m...@arm.com
CC: Mark Rutland mark.rutl...@arm.com
CC: Ian Campbell ijc+devicet...@hellion.org.uk
CC: Kumar Gala ga...@codeaurora.org
CC
.
Also add range for reset multiplex registers for SoC on the device.
These registers are located in Bootcfg memory space and needed
to setup behaviour after appropriate watchdog is triggered.
Add ti,wdt_list option to declare what watchdog are used to reboot
the SoC.
Signed-off-by: Ivan Khoronzhuk
On 02/18/2014 10:30 PM, Greg KH wrote:
On Wed, Feb 05, 2014 at 09:46:13PM +0200, Ivan Khoronzhuk wrote:
Add new AEMIF driver for EMIF16 Texas Instruments controller.
The EMIF16 module is intended to provide a glue-less interface to
a variety of asynchronous memory devices like ASRA M, NOR
to it,
as result we can't encode CS number in reg for AEMIF child devices
(NAND/NOR/etc), as it will break bindings compatibility.
In this patch, NAND node is used just as an example of child node.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../bindings/memory-controllers/ti-aemif.txt
driver
- memory: ti-aemif: add bindings for AEMIF driver
added ti.cs-chipselect property instead of representing chipselect
number in cs node name.
Ivan Khoronzhuk (2):
memory: ti-aemif: introduce AEMIF driver
memory: ti-aemif: add bindings for AEMIF driver
.../bindings/memory
-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/memory/Kconfig| 11 ++
drivers/memory/Makefile | 1 +
drivers/memory/ti-aemif.c | 427 ++
3 files changed, 439 insertions(+)
create mode 100644 drivers/memory/ti-aemif.c
diff --git
On 02/19/2014 04:34 PM, Greg KH wrote:
On Wed, Feb 19, 2014 at 12:32:02PM +0200, Ivan Khoronzhuk wrote:
+ aemif-clk = devm_clk_get(dev, NULL);
+ if (IS_ERR(aemif-clk)) {
+ dev_err(dev, cannot get clock 'aemif'\n);
+ return PTR_ERR(aemif-clk);
No freeing
On 02/19/2014 08:11 PM, Mark Rutland wrote:
On Wed, Feb 19, 2014 at 01:40:10PM +, Ivan Khoronzhuk wrote:
Add bindings for TI Async External Memory Interface (AEMIF) controller.
The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
provide a glue-less interface
On 02/20/2014 03:44 PM, Rob Herring wrote:
On Thu, Feb 20, 2014 at 6:44 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
On 02/19/2014 08:11 PM, Mark Rutland wrote:
On Wed, Feb 19, 2014 at 01:40:10PM +, Ivan Khoronzhuk wrote:
Add bindings for TI Async External Memory Interface (AEMIF
() returns -1.
used request_irq() instead of setup_irq()
assigned irq for event_device in event_dev-irq
calculated timer.hz_period for CLOCK_EVT_MODE_PERIODIC at init
deleted spare call of keystone_timer_config() in keystone_timer_init()
Ivan Khoronzhuk (3
...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../bindings/timer/ti,keystone-timer.txt | 29 ++
1 file changed, 29 insertions(+)
create mode 100644
Documentation/devicetree/bindings/timer/ti,keystone-timer.txt
diff --git a/Documentation/devicetree
.
Reviewed-by: Stephen Boyd sb...@codeaurora.org
Acked-by: Santosh shilimkar santosh.shilim...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
drivers/clocksource/Makefile | 1 +
drivers/clocksource/timer-keystone.c | 244 +++
2 files changed
Add keystone timer entry to keystone device tree.
This 64-bit timer is used as backup clock event device.
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/boot/dts/keystone-clocks.dtsi | 10 ++
arch/arm/boot/dts/keystone.dtsi| 7 +++
2 files changed, 17
-davinci/aemif.c.
In case of Keystone the timings are going to be set by AEMIF driver.
AEMIF is going to be merged I hope. That's plan.
So you can leave it.
--
Regards,
Ivan Khoronzhuk
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
Add the property davinci-no-subpage-write to disable sub page write in the
nand driver.
Signed-off-by: Murali Karicheri m-kariche...@ti.com
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
arch/arm/boot/dts/k2hk-evm.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot
1 - 100 of 1224 matches
Mail list logo
