Without this patch the adv7343 encoder was being set to default
configuration which caused display not to work on this board.
This patch passes the necessary platform data required for adv7343
encoder to work on da850 evm.
Signed-off-by: Lad, Prabhakar prabhakar@ti.com
---
This patch is
Hi Mauro,
Please pull the following patches, which use devm_kzalloc() instead of
kzalloc().
Regards,
--Prabhakar Lad
The following changes since commit 3151d14aa6e983aa36d51a80d0477859f9ba12af:
[media] media: remove __dev* annotations (2013-01-11 13:03:24 -0200)
are available in the git
On 1/12/2013 7:56 AM, Tivy, Robert wrote:
From: Ohad Ben-Cohen [mailto:o...@wizery.com]
Sent: Friday, January 11, 2013 4:26 AM
On Fri, Jan 11, 2013 at 2:23 AM, Robert Tivy rt...@ti.com wrote:
+static int davinci_rproc_probe(struct platform_device *pdev)
+{
+ struct da8xx_rproc_pdata
Hi Mauro,
Please pull the following patches for DaVinci media, fixing trivial issues.
Regards,
--Prabhakar Lad
The following changes since commit 3151d14aa6e983aa36d51a80d0477859f9ba12af:
[media] media: remove __dev* annotations (2013-01-11 13:03:24 -0200)
are available in the git
Hi Rob,
On Sat, Jan 12, 2013 at 4:26 AM, Tivy, Robert rt...@ti.com wrote:
Is FW_CONFIG above supposed to be FW_LOADER?
That FW_CONFIG is completely bogus of course. care to fix it in your series?
We're currently handling the CHIPINT lines as levels, since they're
completely controlled by
On Tue, Jan 15, 2013 at 11:15 AM, Sekhar Nori nsek...@ti.com wrote:
Right, and platform data is not the way to achieve this.
How do you suggest to handle platforms with multiple different remote
processors (driven by the same driver) ?
Requiring the user to indicate the fw name for each
On Thu, Jan 10, 2013 at 17:49:13, Nori, Sekhar wrote:
On 1/10/2013 1:07 PM, Kumar, Anil wrote:
On Wed, Jan 09, 2013 at 18:17:46, Nori, Sekhar wrote:
I do not think that it is good idea to move NAND pin mux information
into da850.dtsi because this information is evm specific.
if we will
On 1/15/2013 4:06 PM, Kumar, Anil wrote:
On Thu, Jan 10, 2013 at 17:49:13, Nori, Sekhar wrote:
On 1/10/2013 1:07 PM, Kumar, Anil wrote:
On Wed, Jan 09, 2013 at 18:17:46, Nori, Sekhar wrote:
I do not think that it is good idea to move NAND pin mux information
into da850.dtsi because this
On 1/15/2013 3:33 PM, Ohad Ben-Cohen wrote:
On Tue, Jan 15, 2013 at 11:15 AM, Sekhar Nori nsek...@ti.com wrote:
Right, and platform data is not the way to achieve this.
How do you suggest to handle platforms with multiple different remote
processors (driven by the same driver) ?
Requiring
On Tue, Jan 15, 2013 at 2:29 PM, Sekhar Nori nsek...@ti.com wrote:
May be rproc_alloc() could auto-assign the firmware name to something
like 'rproc%d-fw' if firmware name passed to it is NULL?
I prefer we use name-based filenames instead to make it easier for
users (and us developers).
We can
On Wed, 2013-01-02 at 23:22 +0300, Sergei Shtylyov wrote:
Commit cdeadd712f52b16a9285386d61ee26fd14eb4085 (mtd: nand: davinci: add OF
support for davinci nand controller) obviously has never been really build
tested with CONFIG_OF=y. Now it prevents DaVinci family kernels from
building:
all
Fix build on OMAP, the irqs are undefined on AM33xx.
These error interrupt handlers were hardcoded as disabled
so since they are unused code, simply remove them.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/common/edma.c | 37 -
1 file changed, 37
Move mach-davinci/dma.c to common/edma.c so it can be used
by OMAP (specifically AM33xx) as well. This just moves the
private EDMA API and enables it to build on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/Kconfig |1 +
Adds support for parsing the TI EDMA DT data into the required
EDMA private API platform data. Enables runtime PM support to
initialize the EDMA hwmod. Adds AM33XX EMDA crossbar event mux
support.
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/common/edma.c | 314
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter mpor...@ti.com
---
drivers/dma/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
index d4c1218..20ef955 100644
--- a/drivers/dma/Kconfig
+++ b/drivers/dma/Kconfig
@@
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the
Changes since v4:
- Fixed debug section mismatch in private edma api [01/14]
- Respun format-patch to catch the platform_data/edma.h rename [01/14]
- Removed address/size-cells from the EDMA binding [05/14]
Changes since v3:
- Rebased on 3.8-rc3
- No longer
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 49 +
1 file changed, 49 insertions(+)
create mode 100644
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter mpor...@ti.com
---
arch/arm/boot/dts/am33xx.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
Adds a dma_request_slave_channel_compat() wrapper which accepts
both the arguments from dma_request_channel() and
dma_request_slave_channel(). Based on whether the driver is
instantiated via DT, the appropriate channel request call will be
made.
This allows for a much cleaner migration of drivers
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter mpor...@ti.com
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 25 +++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git
The EDMA DMAC has a hardware limitation that prevents supporting
scatter gather lists with any number of segments. The DMA Engine
API reports the maximum number of segments a channel can support
via the optional dma_get_channel_caps() API. If the nr_segs
capability is present, the value is used to
Adds AM33XX MMC support for am335x-bone, am335x-evm, and
am335x-evmsk.
Signed-off-by: Matt Porter mpor...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
arch/arm/boot/dts/am335x-evmsk.dts |
Convert dmaengine channel requests to use
dma_request_slave_channel_compat(). This supports the DT case of
platforms requiring channel selection from either the OMAP DMA or
the EDMA engine. AM33xx only boots from DT and is the only user
implementing EDMA so in the !DT case we can default to the
-Original Message-
From: Ohad Ben-Cohen [mailto:o...@wizery.com]
Sent: Tuesday, January 15, 2013 4:49 AM
To: Nori, Sekhar
Cc: Tivy, Robert; davinci-linux-open-source; linux-arm; Ring, Chris;
Grosen, Mark; r...@landley.net; linux-...@vger.kernel.org; Chemparathy,
Cyril
Subject: Re:
On Wed, Jan 16, 2013 at 1:06 AM, Tivy, Robert rt...@ti.com wrote:
This sounds good, although it will introduce the need to handle dynamic
storage for the generated name. I think I can jam that storage on the end of
the already-dynamically-sized 'struct rproc + sizeof(pdata)' allocation in
This set of patches adds:
* Add pinctrl-single for handling Padconf registers.
* Add NAND node to export NAND functionality on da850 EVM.
* Add NAND pinctrl node to do pin mux according to pinctrl-single driver.
This series applies on top of tag next-20130107 git tree
Enable pinctrl related config option in da8xx_omapl_defconfig
Signed-off-by: Kumar, Anil anilkuma...@ti.com
---
:100644 100644 f292239... 0892db4... M arch/arm/configs/da8xx_omapl_defconfig
arch/arm/configs/da8xx_omapl_defconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff
Add NAND driver DT node and related pinctrl DT data to export NAND
functionality on da850 evm.
Signed-off-by: Kumar, Anil anilkuma...@ti.com
---
:100644 100644 c7609d0... 433027f... M arch/arm/boot/dts/da850-evm.dts
:100644 100644 e9c6e82... 59e6ea4... M arch/arm/boot/dts/da850.dtsi
For DT, DaVinci platform can use pinctrl-single driver for handling
padconf registers.
Enable PINCTRL Kconfig for MACH_DA8XX_DT platform. Add required
pinctrl DT entries in da850 dts file.
Test procedure
1)Populate DT file with NAND node information.
2)Populate board DT file with pinmux
On 1/15/2013 6:19 PM, Ohad Ben-Cohen wrote:
On Tue, Jan 15, 2013 at 2:29 PM, Sekhar Nori nsek...@ti.com wrote:
May be rproc_alloc() could auto-assign the firmware name to something
like 'rproc%d-fw' if firmware name passed to it is NULL?
I prefer we use name-based filenames instead to make
32 matches
Mail list logo
