All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	alsa-devel@alsa-project.org, "Kukjin Kim" <kgene.kim@samsung.com>,
	"Vinod Koul" <vinod.koul@intel.com>, "Dan Williams" <djbw@fb.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Alessandro Rubini" <rubini@gnudd.com>,
	"Giancarlo Asnaghi" <giancarlo.asnaghi@st.com>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Sangbeom Kim" <sbkim73@samsung.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.de>,
	"Padmavathi Venna" <padma.v@samsung.com>,
	"Thomas Abraham" <thomas.abraham@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Sylwester Nawrocki" <sylvester.nawrocki@gmail.com>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>
Subject: Re: [RFC PATCH 00/11] ARM: s3c64xx: Let amba-pl08x driver handle DMA
Date: Wed, 19 Jun 2013 20:26:12 +0200	[thread overview]
Message-ID: <3697657.tZFV7pR81Q@flatron> (raw)
In-Reply-To: <20130619174047.GB1403@sirena.org.uk>

On Wednesday 19 of June 2013 18:40:47 Mark Brown wrote:
> On Sun, Jun 16, 2013 at 10:54:07PM +0200, Tomasz Figa wrote:
> > One of the biggest roadblocks on the way of S3C64xx to DeviceTree
> > support is its DMA driver, which is completely platform-specific and
> > provides private API (s3c-dma), not even saying that its design is
> > completely against multiplatform-awareness.
> 
> I tried to test this on my s3c64xx based system but it gave me a kernel
> that didn't boot far enough to give console output (there's some early
> init stuff that uses SPI...).  That said, I needed:
> 
> diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
> index 210a893..0f49707 100644
> --- a/drivers/dma/amba-pl08x.c
> +++ b/drivers/dma/amba-pl08x.c
> @@ -313,7 +313,7 @@ static int pl08x_request_mux(struct pl08x_dma_chan
> *plchan) int ret;
> 
>  	if (plchan->mux_use++ == 0 && pd->get_signal) {
> -		ret = pd->get_signal(plchan->cd);
> +		ret = (pd->get_signal)(plchan->cd);

Hmm, that's strange. The former is a completely valid piece of code...

>  		if (ret < 0) {
>  			plchan->mux_use = 0;
>  			return ret;
> 
> to get it to build which makes me suspect the compiler a bit as well...
> the system has audio, SPI and MMC enabled.
> 
> I was applying this to -next, are there any other dependencies I need or
> anything?

Hmm, I've been testing this on top of my common clock framework and device 
tree patches, but I don't think this had any effect. Did you add necessary 
clkdev lookups to the clock driver?

In Samsung CCF alias notation it looks like this:

+       ALIAS(HCLK_DMA1, "dma-pl080s.1", "apb_pclk"),
+       ALIAS(HCLK_DMA0, "dma-pl080s.0", "apb_pclk"),

Not sure how hard it will be to add such lookups to the old clock driver, 
though.

I will test this applied directly on top of current linux-next when I find 
some time, but for now you might check out my v3.11-devel branch on my 
github:

https://github.com/tom3q/linux.git

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 00/11] ARM: s3c64xx: Let amba-pl08x driver handle DMA
Date: Wed, 19 Jun 2013 20:26:12 +0200	[thread overview]
Message-ID: <3697657.tZFV7pR81Q@flatron> (raw)
In-Reply-To: <20130619174047.GB1403@sirena.org.uk>

On Wednesday 19 of June 2013 18:40:47 Mark Brown wrote:
> On Sun, Jun 16, 2013 at 10:54:07PM +0200, Tomasz Figa wrote:
> > One of the biggest roadblocks on the way of S3C64xx to DeviceTree
> > support is its DMA driver, which is completely platform-specific and
> > provides private API (s3c-dma), not even saying that its design is
> > completely against multiplatform-awareness.
> 
> I tried to test this on my s3c64xx based system but it gave me a kernel
> that didn't boot far enough to give console output (there's some early
> init stuff that uses SPI...).  That said, I needed:
> 
> diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
> index 210a893..0f49707 100644
> --- a/drivers/dma/amba-pl08x.c
> +++ b/drivers/dma/amba-pl08x.c
> @@ -313,7 +313,7 @@ static int pl08x_request_mux(struct pl08x_dma_chan
> *plchan) int ret;
> 
>  	if (plchan->mux_use++ == 0 && pd->get_signal) {
> -		ret = pd->get_signal(plchan->cd);
> +		ret = (pd->get_signal)(plchan->cd);

Hmm, that's strange. The former is a completely valid piece of code...

>  		if (ret < 0) {
>  			plchan->mux_use = 0;
>  			return ret;
> 
> to get it to build which makes me suspect the compiler a bit as well...
> the system has audio, SPI and MMC enabled.
> 
> I was applying this to -next, are there any other dependencies I need or
> anything?

Hmm, I've been testing this on top of my common clock framework and device 
tree patches, but I don't think this had any effect. Did you add necessary 
clkdev lookups to the clock driver?

In Samsung CCF alias notation it looks like this:

+       ALIAS(HCLK_DMA1, "dma-pl080s.1", "apb_pclk"),
+       ALIAS(HCLK_DMA0, "dma-pl080s.0", "apb_pclk"),

Not sure how hard it will be to add such lookups to the old clock driver, 
though.

I will test this applied directly on top of current linux-next when I find 
some time, but for now you might check out my v3.11-devel branch on my 
github:

https://github.com/tom3q/linux.git

Best regards,
Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
	alsa-devel@alsa-project.org, "Kukjin Kim" <kgene.kim@samsung.com>,
	"Vinod Koul" <vinod.koul@intel.com>, "Dan Williams" <djbw@fb.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Alessandro Rubini" <rubini@gnudd.com>,
	"Giancarlo Asnaghi" <giancarlo.asnaghi@st.com>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Sangbeom Kim" <sbkim73@samsung.com>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.de>,
	"Padmavathi Venna" <padma.v@samsung.com>,
	"Thomas Abraham" <thomas.abraham@linaro.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Olof Johansson" <olof@lixom.net>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Sylwester Nawrocki" <sylvester.nawrocki@gmail.com>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Alban Bedel" <alban.bedel@avionic-design.de>
Subject: Re: [RFC PATCH 00/11] ARM: s3c64xx: Let amba-pl08x driver handle DMA
Date: Wed, 19 Jun 2013 20:26:12 +0200	[thread overview]
Message-ID: <3697657.tZFV7pR81Q@flatron> (raw)
In-Reply-To: <20130619174047.GB1403@sirena.org.uk>

On Wednesday 19 of June 2013 18:40:47 Mark Brown wrote:
> On Sun, Jun 16, 2013 at 10:54:07PM +0200, Tomasz Figa wrote:
> > One of the biggest roadblocks on the way of S3C64xx to DeviceTree
> > support is its DMA driver, which is completely platform-specific and
> > provides private API (s3c-dma), not even saying that its design is
> > completely against multiplatform-awareness.
> 
> I tried to test this on my s3c64xx based system but it gave me a kernel
> that didn't boot far enough to give console output (there's some early
> init stuff that uses SPI...).  That said, I needed:
> 
> diff --git a/drivers/dma/amba-pl08x.c b/drivers/dma/amba-pl08x.c
> index 210a893..0f49707 100644
> --- a/drivers/dma/amba-pl08x.c
> +++ b/drivers/dma/amba-pl08x.c
> @@ -313,7 +313,7 @@ static int pl08x_request_mux(struct pl08x_dma_chan
> *plchan) int ret;
> 
>  	if (plchan->mux_use++ == 0 && pd->get_signal) {
> -		ret = pd->get_signal(plchan->cd);
> +		ret = (pd->get_signal)(plchan->cd);

Hmm, that's strange. The former is a completely valid piece of code...

>  		if (ret < 0) {
>  			plchan->mux_use = 0;
>  			return ret;
> 
> to get it to build which makes me suspect the compiler a bit as well...
> the system has audio, SPI and MMC enabled.
> 
> I was applying this to -next, are there any other dependencies I need or
> anything?

Hmm, I've been testing this on top of my common clock framework and device 
tree patches, but I don't think this had any effect. Did you add necessary 
clkdev lookups to the clock driver?

In Samsung CCF alias notation it looks like this:

+       ALIAS(HCLK_DMA1, "dma-pl080s.1", "apb_pclk"),
+       ALIAS(HCLK_DMA0, "dma-pl080s.0", "apb_pclk"),

Not sure how hard it will be to add such lookups to the old clock driver, 
though.

I will test this applied directly on top of current linux-next when I find 
some time, but for now you might check out my v3.11-devel branch on my 
github:

https://github.com/tom3q/linux.git

Best regards,
Tomasz


  reply	other threads:[~2013-06-19 18:26 UTC|newest]

Thread overview: 133+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 20:54 [RFC PATCH 00/11] ARM: s3c64xx: Let amba-pl08x driver handle DMA Tomasz Figa
2013-06-16 20:54 ` Tomasz Figa
2013-06-16 20:54 ` Tomasz Figa
2013-06-16 20:54 ` [RFC PATCH 01/11] dma: amba-pl08x: Use bitmap to pass variant specific quirks Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:25   ` Linus Walleij
2013-06-17 13:25     ` Linus Walleij
2013-06-17 18:48   ` Russell King - ARM Linux
2013-06-17 18:48     ` Russell King - ARM Linux
2013-06-17 18:48     ` Russell King - ARM Linux
2013-06-17 18:56     ` Tomasz Figa
2013-06-17 18:56       ` Tomasz Figa
2013-06-17 18:56       ` Tomasz Figa
2013-06-18  7:47       ` Linus Walleij
2013-06-18  7:47         ` Linus Walleij
2013-06-18 13:33         ` Arnd Bergmann
2013-06-18 13:33           ` Arnd Bergmann
2013-06-16 20:54 ` [RFC PATCH 02/11] dma: amba-pl08x: Refactor pl08x_getbytes_chan() to lower indentation Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:29   ` Linus Walleij
2013-06-17 13:29     ` Linus Walleij
2013-06-16 20:54 ` [RFC PATCH 03/11] dma: amba-pl08x: Add support for different offset of CONFIG register Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:31   ` Linus Walleij
2013-06-17 13:31     ` Linus Walleij
2013-06-17 18:52   ` Russell King - ARM Linux
2013-06-17 18:52     ` Russell King - ARM Linux
2013-06-17 18:52     ` Russell King - ARM Linux
2013-06-17 19:02     ` Tomasz Figa
2013-06-17 19:02       ` Tomasz Figa
2013-06-17 19:02       ` Tomasz Figa
2013-06-16 20:54 ` [RFC PATCH 04/11] dma: amba-pl08x: Add support for PL080S variant Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:39   ` Linus Walleij
2013-06-17 13:39     ` Linus Walleij
2013-06-17 18:22     ` Tomasz Figa
2013-06-17 18:22       ` Tomasz Figa
2013-06-16 20:54 ` [RFC PATCH 05/11] dma: amba-pl08x: Add support for different maximum transfer size Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:42   ` Linus Walleij
2013-06-17 13:42     ` Linus Walleij
2013-06-17 18:27     ` Tomasz Figa
2013-06-17 18:27       ` Tomasz Figa
2013-06-16 20:54 ` [RFC PATCH 06/11] dma: amba-pl08x: Keep LLIs aligned to 4-word boundary Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:51   ` Linus Walleij
2013-06-17 13:51     ` Linus Walleij
2013-06-17 18:28     ` Tomasz Figa
2013-06-17 18:28       ` Tomasz Figa
2013-06-17 19:01     ` Russell King - ARM Linux
2013-06-17 19:01       ` Russell King - ARM Linux
2013-06-16 20:54 ` [RFC PATCH 07/11] dmaengine: PL08x: Fix reading the byte count in cctl Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:53   ` Linus Walleij
2013-06-17 13:53     ` Linus Walleij
2013-06-17 18:32     ` Tomasz Figa
2013-06-17 18:32       ` Tomasz Figa
2013-06-17 19:03     ` Russell King - ARM Linux
2013-06-17 19:03       ` Russell King - ARM Linux
2013-06-16 20:54 ` [RFC PATCH 08/11] dmaengine: PL08x: Add cyclic transfer support Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:57   ` Linus Walleij
2013-06-17 13:57     ` Linus Walleij
2013-06-17 18:52     ` Tomasz Figa
2013-06-17 18:52       ` Tomasz Figa
2013-06-17 18:56   ` Russell King - ARM Linux
2013-06-17 18:56     ` Russell King - ARM Linux
2013-06-17 18:56     ` Russell King - ARM Linux
2013-06-16 20:54 ` [RFC PATCH 09/11] spi: s3c64xx: Do not require legacy DMA API in case of S3C64XX Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 13:59   ` Linus Walleij
2013-06-17 13:59     ` Linus Walleij
2013-06-17 16:06     ` Mark Brown
2013-06-17 16:06       ` Mark Brown
2013-06-17 19:36       ` Tomasz Figa
2013-06-17 19:36         ` Tomasz Figa
2013-06-16 20:54 ` [RFC PATCH 10/11] ASoC: samsung: " Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 14:01   ` Linus Walleij
2013-06-17 14:01     ` Linus Walleij
2013-06-16 20:54 ` [RFC PATCH 11/11] ARM: s3c64xx: Add support for DMA using generic amba-pl08x driver Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-16 20:54   ` Tomasz Figa
2013-06-17 14:04   ` Linus Walleij
2013-06-17 14:04     ` Linus Walleij
2013-06-19 18:23     ` Tomasz Figa
2013-06-19 18:23       ` Tomasz Figa
2013-06-19 19:50       ` Linus Walleij
2013-06-19 19:50         ` Linus Walleij
2013-06-17 14:06 ` [RFC PATCH 00/11] ARM: s3c64xx: Let amba-pl08x driver handle DMA Linus Walleij
2013-06-17 14:06   ` Linus Walleij
2013-06-17 19:38   ` Tomasz Figa
2013-06-17 19:38     ` Tomasz Figa
2013-06-19 17:40 ` Mark Brown
2013-06-19 17:40   ` Mark Brown
2013-06-19 17:40   ` Mark Brown
2013-06-19 18:26   ` Tomasz Figa [this message]
2013-06-19 18:26     ` Tomasz Figa
2013-06-19 18:26     ` Tomasz Figa
2013-06-19 19:01     ` Arnd Bergmann
2013-06-19 19:01       ` Arnd Bergmann
2013-06-19 19:01       ` Arnd Bergmann
2013-06-19 19:24       ` Mark Brown
2013-06-19 19:24         ` Mark Brown
2013-06-19 19:24         ` Mark Brown
2013-06-19 19:22     ` Mark Brown
2013-06-19 19:22       ` Mark Brown
2013-06-19 19:22       ` Mark Brown
2013-06-19 19:32       ` Tomasz Figa
2013-06-19 19:32         ` Tomasz Figa
2013-06-19 19:32         ` Tomasz Figa
2013-06-19 22:48         ` Mark Brown
2013-06-19 22:48           ` Mark Brown
2013-06-19 22:48           ` Mark Brown
2013-06-20  9:24       ` Phil Carmody
2013-06-20  9:24         ` Phil Carmody
2013-06-20 10:35         ` Mark Brown
2013-06-20 10:35           ` Mark Brown
2013-06-20 11:14           ` Phil Carmody
2013-06-20 11:14             ` Phil Carmody
2013-06-21  9:47             ` Mark Brown
2013-06-21  9:47               ` Mark Brown
2013-06-21  9:47               ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3697657.tZFV7pR81Q@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=djbw@fb.com \
    --cc=giancarlo.asnaghi@st.com \
    --cc=grant.likely@linaro.org \
    --cc=heiko@sntech.de \
    --cc=kgene.kim@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=padma.v@samsung.com \
    --cc=perex@perex.cz \
    --cc=rubini@gnudd.com \
    --cc=sbkim73@samsung.com \
    --cc=sylvester.nawrocki@gmail.com \
    --cc=thomas.abraham@linaro.org \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.