On Wed, Nov 26, 2014 at 10:14 PM, Dave Gerlach d-gerl...@ti.com wrote:
--- a/lib/devres.c
+++ b/lib/devres.c
@@ -72,6 +72,64 @@ void __iomem *devm_ioremap_nocache(struct device *dev,
resource_size_t offset,
EXPORT_SYMBOL(devm_ioremap_nocache);
/**
+ * devm_ioremap_exec - Managed
Hi,
The linux/platform_data/edma.h file was used for API definition as well, which
is not correct since the header should only contain platform data related
structures, defines, etc.
Mark: I think this series can go via arm since it is just changing include stuff
under ASoC.
Regards,
Peter
---
Rename the include/linux/edma.h to include/linux/edma-dmaengine.h
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/common/edma.c | 2 +-
drivers/mmc/host/davinci_mmc.c | 3 +--
drivers/spi/spi-davinci.c | 2 +-
include/linux/edma-dmaengine.h | 29
include/linux/platform_data/ is not a correct place to keep the API
definitions for edma, it is meant to be only for the pdata for the device.
Clean up this by moving the API to include/linux/edma.h
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/common/edma.c
The machine driver has no business with the underlying dma.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
sound/soc/davinci/davinci-evm.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/sound/soc/davinci/davinci-evm.c b/sound/soc/davinci/davinci-evm.c
index
On Thu, Nov 27, 2014 at 12:41:29PM +0200, Peter Ujfalusi wrote:
The machine driver has no business with the underlying dma.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
Acked-by: Mark Brown broo...@kernel.org
signature.asc
Description: Digital signature
On Thursday 27 November 2014 12:41:30 Peter Ujfalusi wrote:
diff --git a/include/linux/edma-dmaengine.h b/include/linux/edma-dmaengine.h
new file mode 100644
index ..8a2602809a77
--- /dev/null
+++ b/include/linux/edma-dmaengine.h
@@ -0,0 +1,29 @@
+struct dma_chan;
+
+#if
8
From: Tony Lindgren t...@atomide.com
Date: Wed, 26 Nov 2014 11:55:29 -0800
Subject: [PATCH] ARM: OMAP2+: Fix n900 board name for legacy user space
N900 legacy user space apps need the board name in
/proc/cpuinfo to work properly for the Hardware entry.
For other boards
On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
* Pali Rohár pali.ro...@gmail.com [141126 15:40]:
With enabled CONFIG_ARM_APPENDED_DTB=y file /proc/atags is
missing.
OK I guess it should not be needed for DT based booting.
If I do not enable CONFIG_ARM_APPENDED_DTB=y then
On Fri, Nov 14, 2014 at 4:40 PM, Roger Quadros rog...@ti.com wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the CAN_RX line.
To work around this issue we select
On Fri, Nov 14, 2014 at 2:43 PM, Roger Quadros rog...@ti.com wrote:
On 11/13/2014 06:03 PM, Marc Kleine-Budde wrote:
On 11/13/2014 04:23 PM, Roger Quadros wrote:
I just stumbled over pinctrl_pm_select_sleep_state(), is it possible to
integrate this into runtime pm?
Hello,
in commit ARM: dts: OMAP3-N900: Add isp1704 support
e17337a26962943c27124a14b0794eabe76af437 was added support for
isp1704 chip with configured gpio 3. Now I looked into legacy
board rx51 data and there is gpio 67 for isp1704.
I would like to ask, why we have different gpio in board
On 11/27/2014 01:14 PM, Arnd Bergmann wrote:
On Thursday 27 November 2014 12:41:30 Peter Ujfalusi wrote:
diff --git a/include/linux/edma-dmaengine.h b/include/linux/edma-dmaengine.h
new file mode 100644
index ..8a2602809a77
--- /dev/null
+++ b/include/linux/edma-dmaengine.h
@@
On Thursday 27 November 2014 16:23:31 Peter Ujfalusi wrote:
This will only work in case of legacy boot. When booting with DT we do not
have pdata and after this patch in dt boot we are not going to be able to get
the DMA resources either.
No, when booting with DT, the filter_fn and data are
Hi,
On Thu, Nov 27, 2014 at 03:13:43PM +0100, Pali Rohár wrote:
Hello,
in commit ARM: dts: OMAP3-N900: Add isp1704 support
e17337a26962943c27124a14b0794eabe76af437 was added support for
isp1704 chip with configured gpio 3. Now I looked into legacy
board rx51 data and there is gpio 67
OMAP2/3 now use generic API for the prm_clear_mod_irqs, the SoC specific
implementation details are provided through prm_ll_data.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm24xx.c | 24 +++-
arch/arm/mach-omap2/pm34xx.c | 18
This makes the API the same as used with OMAP2, and makes it possible
to implement a generic driver API for the functionality.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/pm34xx.c | 18 +-
arch/arm/mach-omap2/prm3xxx.c |8
There is no implementation for this anywhere, so remove it from the header
files also.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prm3xxx.h |1 -
arch/arm/mach-omap2/prm44xx_54xx.h |1 -
2 files changed, 2 deletions(-)
diff --git
omap2xxx_cm_get_pll_config and omap2xxx_cm_get_pll_status are not used
for anything, so remove these.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/cm2xxx.c | 10 --
arch/arm/mach-omap2/cm2xxx.h |2 --
2 files changed, 12 deletions(-)
diff --git
This gets rid of need for some exported driver APIs, and simplifies the
initialization of the CM driver. Done in preparation to make CM a
separate driver. The init data is now also passed to the SoC specific
implementations, allowing future expansion to add feature flags etc.
Signed-off-by: Tero
All clock provider related drivers will now register their iomaps
individually, and provide index number to the provider init. The
clock related drivers also add support for providing init data
through the DT match functionality; this is initially used only
to provide the index variable, but can
There is no need to provide the PRM base address through a low-level API
from the low-level IO init, as this information is available through DT.
Re-routed the parsing function to be called from the PRM drivers also to
simplify the implementation under io.c.
Signed-off-by: Tero Kristo
Hi,
Yet another PRCM cleanup set, towards making PRCM a separate driver.
This set is most likely too late for 3.19, but hopefully it can make
it to 3.20. Couple of related clock patches are also within this set,
as some of the clock support code is now obsolete. Most important
things this set
There is no need to provide the CM base address through a low-level API
from the low-level IO init, as this information is available through DT.
Re-routed the parsing function to be called from the CM drivers also to
simplify the implementation under io.c.
Signed-off-by: Tero Kristo
PRM device instance offset is now provided through the prm_init_data.
This gets rid of some cpu_is_X / soc_is_X calls from PRM core code,
preparing for PRM to be its own separate driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prcm-common.h |2 ++
Splits the clock related provider module inits under their own driver files.
Previously this was done for all modules under the common PRM driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/cm.h |1 +
arch/arm/mach-omap2/cm_common.c | 24
PRM driver now only exports a generic API for clearing / checking
VP txdone status.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prm.h | 14 ++
arch/arm/mach-omap2/prm3xxx.c |6 --
arch/arm/mach-omap2/prm3xxx.h |4
There is no need to provide the control module base address through a
low-level API from the low-level IO init, as this information is
available through DT. This patch adds a new API to initialize the
control module though, but mostly makes the old API obsolete. The
old API can be completely
There is no need to call this separately from io.c, rather this can be
done commonly under the PRM driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |4
arch/arm/mach-omap2/prm44xx.c |2 ++
2 files changed, 2 insertions(+), 4 deletions(-)
diff
APLL clock type is no longer needed as the legacy clock support is removed.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/Makefile|1 -
arch/arm/mach-omap2/clkt2xxx_apll.c | 142 ---
arch/arm/mach-omap2/clock2xxx.h | 11 ---
OMAP4 is DT only now, so the legacy mux support is not needed anymore.
Padconf is used instead from the driver / DT. This removes the need
for having the mux APIs exported from the control module driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
Cc: Tomi Valkeinen tomi.valkei...@ti.com
---
This gets rid of need for some exported driver APIs, and simplifies the
initialization of the PRM driver. Done in preparation to make PRM a
separate driver. The init data is now also passed to the SoC specific
implementations, allowing future expansion to add feature flags etc.
Signed-off-by:
These are no longer needed for anything with the introduction of
pinctrl DT support, thus removed.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/control.c | 23 +--
arch/arm/mach-omap2/control.h |5 +
arch/arm/mach-omap2/io.c | 27
Splits the clock provider init out of the PRM driver and moves it to
clock driver. This is needed so that once the PRCM drivers are separated,
they can logically just access the clock driver not needing to go through
common PRM code. This would be wrong in the case of control module for
example.
This avoids conflicts in the global namespace, and is more descriptive
of the purpose anyway.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |2 +-
arch/arm/mach-omap2/prm.h|2 +-
arch/arm/mach-omap2/prm_common.c |8 +++-
3 files changed,
OMAP4 has different ordering of PRM and CM init calls in the early init.
Re-oder these accordingly for OMAP4 also. This is needed so that we
can do some optimizations in the following patches for the PRCM init.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |2 +-
1
Currently some cpu_is_X checks are used to setup prm_features, however
the same can be accomplished by just passing these flags from the PRM
init data. This is done in preparation to make PRM a separate driver.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/prm44xx.c|
There is no need to call this separately from io.c, rather this can be
done commonly under the CM driver. Also, this patch makes the API static,
as it is no longer used outside the driver file.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/cm44xx.h |1 -
The compatible DT node is now passed with the prm init, so there is no
need to do node matching here again. Added a new flag to the init data
also, to detect default IRQ support for OMAP4. Also, any booting omap4
DT setup always has a PRM node, so there is no need to check against
the special case
On 27/11/14 17:51, Tero Kristo wrote:
OMAP4 is DT only now, so the legacy mux support is not needed anymore.
Padconf is used instead from the driver / DT. This removes the need
for having the mux APIs exported from the control module driver.
We still use those mux functions for DT. The mux
On 11/27/2014 04:50 PM, Arnd Bergmann wrote:
On Thursday 27 November 2014 16:23:31 Peter Ujfalusi wrote:
This will only work in case of legacy boot. When booting with DT we do not
have pdata and after this patch in dt boot we are not going to be able to get
the DMA resources either.
No,
On Thu, 27 Nov 2014, Tero Kristo wrote:
Yet another PRCM cleanup set, towards making PRCM a separate driver.
This set is most likely too late for 3.19, but hopefully it can make
it to 3.20.
Yep too late for 3.19.
...
Testing done:
...
omap3-beagle: boot, suspend (ret), suspend (off)
On 11/27/2014 02:26 PM, Linus Walleij wrote:
On Fri, Nov 14, 2014 at 4:40 PM, Roger Quadros rog...@ti.com wrote:
DRA7 CAN IP suffers from a problem which causes it to be prevented
from fully turning OFF (i.e. stuck in transition) if the module was
disabled while there was traffic on the
On Thursday 27 November 2014 20:46:12 Peter Ujfalusi wrote:
I see. With this series I did not planed to fix all edma related issues, just
as a start clean up the related header files. I would rather not add fixes to
mmc, spi, etc drivers since while you have valid point it is not in the scope
On Mon, Nov 17, 2014 at 12:48:22PM +0100, Marek Szyprowski wrote:
This is an updated patchset, which intends to add support for L2 cache
on Exynos4 SoCs on boards running under secure firmware, which requires
certain initialization steps to be done with help of firmware, as
selected registers
ES1.2 is a minor variant of ES1.1. Major changes since ES1.1 are
updating ROM for fixing the following boot modes:
- NAND boot
- UART boot
- Ethernet boot
- USB HOST/Client boot
This patch adds ID support for AM437x ES1.2 silicon.
There are no additional kernel fixes required for ES1.2 silicon.
On 11/27/2014 11:52 PM, Arnd Bergmann wrote:
On Thursday 27 November 2014 20:46:12 Peter Ujfalusi wrote:
I see. With this series I did not planed to fix all edma related issues, just
as a start clean up the related header files. I would rather not add fixes to
mmc, spi, etc drivers since
On 11/27/2014 06:09 PM, Tomi Valkeinen wrote:
On 27/11/14 17:51, Tero Kristo wrote:
OMAP4 is DT only now, so the legacy mux support is not needed anymore.
Padconf is used instead from the driver / DT. This removes the need
for having the mux APIs exported from the control module driver.
We
48 matches
Mail list logo
