Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Boojin Kim' <boojin.kim@samsung.com>,
	alsa-devel@alsa-project.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org,
	spi-devel-general@lists.sourceforge.net
Cc: 'Vinod Koul' <vinod.koul@intel.com>,
	'Grant Likely' <grant.likely@secretlab.ca>,
	'Russell King - ARM Linux' <linux@arm.linux.org.uk>,
	'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
	'Dan Williams' <dan.j.williams@intel.com>
Subject: RE: [PATCH 2/3] spi: Add the use of DMA config operation
Date: Tue, 19 Jun 2012 17:47:56 +0900	[thread overview]
Message-ID: <019301cd4df8$3a5883c0$af098b40$%kim@samsung.com> (raw)
In-Reply-To: <011601cd42eb$8314ab10$893e0130$%kim@samsung.com>

Boojin Kim wrote:
> 
> Config operation is separated from request operation in DMA common
> operation.
> Because spi driver can change the DMA config for every transfer.
> So this patch is using the separated DMA config operation.
> 
> Signed-off-by: Boojin Kim <boojin.kim@samsung.com>
> Signed-off-by: Kyoungil Kim <ki0351.kim@samsung.com>
> ---
>  drivers/spi/spi-s3c64xx.c |   33 +++++++++++++++++++--------------
>  1 files changed, 19 insertions(+), 14 deletions(-)
> 
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index 15f864d..f4e2341 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -262,14 +262,24 @@ static void prepare_dma(struct s3c64xx_spi_dma_data
> *dma,
>  					unsigned len, dma_addr_t buf)
>  {
>  	struct s3c64xx_spi_driver_data *sdd;
> -	struct samsung_dma_prep_info info;
> +	struct samsung_dma_prep info;
> +	struct samsung_dma_config config;
> 
> -	if (dma->direction == DMA_DEV_TO_MEM)
> +	if (dma->direction == DMA_DEV_TO_MEM) {
>  		sdd = container_of((void *)dma,
>  			struct s3c64xx_spi_driver_data, rx_dma);
> -	else
> +		config.direction = sdd->rx_dma.direction;
> +		config.fifo = sdd->sfr_start + S3C64XX_SPI_RX_DATA;
> +		config.width = sdd->cur_bpw / 8;
> +		sdd->ops->config(sdd->rx_dma.ch, &config);
> +	} else {
>  		sdd = container_of((void *)dma,
>  			struct s3c64xx_spi_driver_data, tx_dma);
> +		config.direction =  sdd->tx_dma.direction;
> +		config.fifo = sdd->sfr_start + S3C64XX_SPI_TX_DATA;
> +		config.width = sdd->cur_bpw / 8;
> +		sdd->ops->config(sdd->tx_dma.ch, &config);
> +	}
> 
>  	info.cap = DMA_SLAVE;
>  	info.len = len;
> @@ -284,20 +294,15 @@ static void prepare_dma(struct s3c64xx_spi_dma_data
> *dma,
> 
>  static int acquire_dma(struct s3c64xx_spi_driver_data *sdd)
>  {
> -	struct samsung_dma_info info;
> +	struct samsung_dma_req req;
> 
>  	sdd->ops = samsung_dma_get_ops();
> 
> -	info.cap = DMA_SLAVE;
> -	info.client = &s3c64xx_spi_dma_client;
> -	info.width = sdd->cur_bpw / 8;
> -
> -	info.direction = sdd->rx_dma.direction;
> -	info.fifo = sdd->sfr_start + S3C64XX_SPI_RX_DATA;
> -	sdd->rx_dma.ch = sdd->ops->request(sdd->rx_dma.dmach, &info);
> -	info.direction =  sdd->tx_dma.direction;
> -	info.fifo = sdd->sfr_start + S3C64XX_SPI_TX_DATA;
> -	sdd->tx_dma.ch = sdd->ops->request(sdd->tx_dma.dmach, &info);
> +	req.cap = DMA_SLAVE;
> +	req.client = &s3c64xx_spi_dma_client;
> +
> +	sdd->rx_dma.ch = sdd->ops->request(sdd->rx_dma.dmach, &req);
> +	sdd->tx_dma.ch = sdd->ops->request(sdd->tx_dma.dmach, &req);
> 
>  	return 1;
>  }
> --
> 1.7.1

Hi Grant,

I think, this is needed to support Samsung SPI with DMA and this has
dependency with other patches in this series.

If you're ok on this, please reply with your ack :) so that I can take this
series together.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

      reply	other threads:[~2012-06-19  8:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05  7:19 [PATCH 2/3] spi: Add the use of DMA config operation Boojin Kim
2012-06-19  8:47 ` Kukjin Kim [this message]

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='019301cd4df8$3a5883c0$af098b40$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=boojin.kim@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dan.j.williams@intel.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=spi-devel-general@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox