On Fri, Jan 11, 2013 at 11:18:41, Porter, Matt wrote:
> The binding definition is based on the generic DMA controller
> binding.
>
> Signed-off-by: Matt Porter
> ---
> Documentation/devicetree/bindings/dma/ti-edma.txt | 51
> +
> 1 file changed, 51 insertions(+)
> create
On Fri, Jan 11, 2013 at 11:18:37, Porter, Matt wrote:
> 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
> ---
> arch/arm/Kconfig
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/spi/omap-spi.txt | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/spi/omap-spi.txt
b/D
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 OMA
Adds DMA resources to the AM33XX SPI nodes.
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 278b75d..8fd3648 100644
--- a/arch/arm/boot/dts/am33xx.dt
The binding definition is based on the generic DMA controller
binding.
Signed-off-by: Matt Porter
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 51 +
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/ti-edma.txt
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
---
arch/arm/boot/dts/am335x-bone.dts |7 +++
arch/arm/boot/dts/am335x-evm.dts |7 +++
arch/arm/boot/dts/am335x-evmsk.dts |7 +++
arch/arm/boot/dts/am33xx.dtsi | 2
The binding definition is based on the generic DMA request binding.
Signed-off-by: Matt Porter
---
.../devicetree/bindings/mmc/ti-omap-hsmmc.txt | 25 +++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
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
---
arch/arm/common/edma.c | 37 -
1 file changed, 37 deletions(-)
d
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 OMA
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
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
---
arch/arm/common/edma.c | 314 ++
Adds AM33XX EDMA support to the am33xx.dtsi as documented in
Documentation/devicetree/bindings/dma/ti-edma.txt
Signed-off-by: Matt Porter
---
arch/arm/boot/dts/am33xx.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dt
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
---
arch/arm/Kconfig |1 +
arch/arm/common/Kconfig
Enable TI EDMA option on OMAP.
Signed-off-by: Matt Porter
---
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
@@ -221,7 +221,7 @@
Changes since v3:
- Rebased on 3.8-rc3
- No longer an RFC
- Fixed bugs in DT/pdata parsing reported by Vaibhav Bedia
- Restored all the Davinci pdata to const
- Removed max_segs hack in favor of using dma_get_channel_caps()
- Fixed extra parens, __raw
Pour voir le message, veuillez utiliser un lecteur de mail compatible HTML
Lien miroir :
http://m10-fr.com/mc10_m/YT0xMyZiPTI5NjIyJmM9NDgzNjEyJmQ9MjAxMy0wMS0xMSAwNToxMDowMSZlPTEmaD0yOTYyMCZmPTI5NjIyJmc9Mjk2MjI=
Lien de désinscription :
http://m10-fr.com/mc10_unsub/YT0xMyZiPTI5NjIyJmM9NDgzNjEyJm
Remove deprecated cell-index property and use spi alias to
obtain the SPI PSC number used for SPI bus id.
Signed-off-by: Anatolij Gustschin
---
v2:
- use of_alias_get_id() to get spi bus number
drivers/spi/spi-mpc512x-psc.c | 16 +---
1 files changed, 5 insertions(+), 11 deletion
On Sun, Oct 28, 2012 at 01:47:09PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > 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 but does not support OMAP.
> >
> > Signed-off-
Remove deprecated cell-index property and use spi alias to
obtain the SPI PSC number used for SPI bus id.
Signed-off-by: Anatolij Gustschin
---
v2:
- use of_alias_get_id() to get spi bus number
drivers/spi/spi-mpc512x-psc.c | 16 +---
1 files changed, 5 insertions(+), 11 deletion
Hi Grant,
On Fri, 21 Dec 2012 19:29:14 +
Grant Likely wrote:
> On Fri, 21 Dec 2012 14:48:38 +, Grant Likely
> wrote:
> > On Fri, Dec 21, 2012 at 2:43 PM, Anatolij Gustschin wrote:
> > > Use unique PSCx register base offset to obtain the
> > > SPI PSC number used for SPI bus id.
> > >
On Sun, Oct 28, 2012 at 04:41:24PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds support for the per-EDMA channel event mux. This is required
> > for any peripherals using DMA crossbar mapped events.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/common/
On 15:49-20130110, Matt Porter wrote:
> On Thu, Jan 10, 2013 at 01:46:53PM -0600, Nishanth Menon wrote:
> > On 14:35-20130110, Matt Porter wrote:
> > > On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > > > On 10/18/2
On Thu, Jan 10, 2013 at 01:46:53PM -0600, Nishanth Menon wrote:
> On 14:35-20130110, Matt Porter wrote:
> > On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > > On 10/18/2012 6:56 PM, Matt Porter wrote:
> > > > Adds AM33XX SPI support
On Tue, Oct 30, 2012 at 05:33:40AM +, AnilKumar wrote:
> On Thu, Oct 18, 2012 at 18:56:52, Porter, Matt wrote:
> > Adds AM33XX MMC support for am335x-bone and am335x-evm.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am335x-bone.dts |6 ++
> > arch/arm/boot/dts/am3
On 14:35-20130110, Matt Porter wrote:
> On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> > On 10/18/2012 6:56 PM, Matt Porter wrote:
> > > Adds AM33XX SPI support for am335x-bone and am335x-evm.
> > >
> > > Signed-off-by: Matt Porter
>
On Sun, Oct 28, 2012 at 05:01:29PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds AM33XX SPI support for am335x-bone and am335x-evm.
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am335x-bone.dts | 17 +++
> > arch/arm/boot/dts/am33
On Mon, Oct 29, 2012 at 01:48:46PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > The EDMA DMAC has a hardware limitation that prevents supporting
> > scatter gather lists with any number of segments. Since the EDMA
> > DMA Engine driver sets the maximum segments to 16, w
On Sun, Oct 28, 2012 at 04:46:36PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds AM33XX EDMA support to the am33xx.dtsi as documented in
> > Documentation/devicetree/bindings/dma/ti-edma.txt
> >
> > Signed-off-by: Matt Porter
> > ---
> > arch/arm/boot/dts/am33xx.
On Sun, Oct 28, 2012 at 04:33:39PM +0530, Sekhar Nori wrote:
> On 10/18/2012 6:56 PM, Matt Porter wrote:
> > Adds support for parsing the TI EDMA DT data into the required
> > EDMA private API platform data.
> >
> > Calls runtime PM API only in the DT case in order to unidle the
> > associated hwm
On Thu, 10 Jan 2013, Linus Walleij wrote:
> On Wed, Jan 9, 2013 at 3:44 PM, Guennadi Liakhovetski
> wrote:
>
> > [ 79.968000] mmc0: new SD card on SPI
> > [ 79.976000] mmcblk0: mmc0: SU02G 1.84 GiB
> > [ 80.024000] mmcblk0: p1
> > [ 80.132000] mmcblk0: error -38 sending status comma
On Wed, Jan 9, 2013 at 3:44 PM, Guennadi Liakhovetski
wrote:
> [ 79.968000] mmc0: new SD card on SPI
> [ 79.976000] mmcblk0: mmc0: SU02G 1.84 GiB
> [ 80.024000] mmcblk0: p1
> [ 80.132000] mmcblk0: error -38 sending status command, retrying
> [ 80.136000] mmcblk0: error -38 sending
On Wed, Jan 9, 2013 at 3:08 PM, Guennadi Liakhovetski
wrote:
> Add a pointer variable to make spi_bitbang_start() look simpler.
>
> Signed-off-by: Guennadi Liakhovetski
Acked-by: Linus Walleij
I think Mark Brown is still backing up Grant sometimes, so include
him on CC.
Yours,
Linus Walleij
On Wed, Jan 9, 2013 at 5:25 AM, Vinod Koul wrote:
> Also I have some questions on this approach. Is this driver for SSP ip or SPI
> ip, looks like latter. In both the cases there are some existing drivers in
> kernel and adding one more IMHO doesnt make sense. What we really need a
> common core
Merci d'ajouter notre adresse à votre carnet d'adresses pour être sûr que nos
messages arrivent bien dans votre boîte de réception. Visualiser ce message en
ligne
http://news.dessouscheri.com/HM?a=ENX7Cqi8-r2A8SA9MKJJ7ennGHxKLCbYLvcStGb5lw8W0bBhOG5mpqVsje_Hhe-kulIY
4 euros l'ensemble, liquidat
On Thu, 10 Jan 2013, Lars-Peter Clausen wrote:
> On 01/10/2013 09:53 AM, Julia Lawall wrote:
> >> +@r1@
> >> +identifier fn;
> >> +identifier xfers;
> >> +@@
> >> +fn(...)
> >> +{
> >> + ...
> >> +(
> >> + struct spi_transfer xfers[...];
> >> +|
> >> + struct spi_transfer xfers[];
> >> +)
> >>
On 01/10/2013 09:53 AM, Julia Lawall wrote:
>> +@r1@
>> +identifier fn;
>> +identifier xfers;
>> +@@
>> +fn(...)
>> +{
>> +...
>> +(
>> +struct spi_transfer xfers[...];
>> +|
>> +struct spi_transfer xfers[];
>> +)
>> +...
>> +}
>
> Can it happen that there would be more than one sp
> +@r1@
> +identifier fn;
> +identifier xfers;
> +@@
> +fn(...)
> +{
> + ...
> +(
> + struct spi_transfer xfers[...];
> +|
> + struct spi_transfer xfers[];
> +)
> + ...
> +}
Can it happen that there would be more than one spi_transfer or spi_message
variable per function? This sem
39 matches
Mail list logo
