From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] spi: s3c64xx: add dma maxburst size initialization
Date: Sat, 02 Mar 2013 22:27:10 +0000 [thread overview]
Message-ID: <20130302222710.AE2143E2E65@localhost> (raw)
In-Reply-To: <001b01ce10d3$e9f78620$bde69260$%kim@samsung.com>
On Fri, 22 Feb 2013 17:09:18 +0900, Boojin Kim <boojin.kim@samsung.com> wrote:
> This patch adds dma maxburst size initialization.
> The maxburst should be set by MODE_CFGn.DMA_TYPE,
> because the pl330 dma driver supports burst mode.
>
> Signed-off-by: Hyeonkook Kim <hk619.kim@samsung.com>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
This series probably needs to be merged together through the arm-soc
tree.
g.
> ---
> drivers/spi/spi-s3c64xx.c | 18 ++++++++++++++++++
> 1 files changed, 18 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/spi/spi-s3c64xx.c b/drivers/spi/spi-s3c64xx.c
> index e862ab8..5e6cafe 100644
> --- a/drivers/spi/spi-s3c64xx.c
> +++ b/drivers/spi/spi-s3c64xx.c
> @@ -287,10 +287,20 @@ static void prepare_dma(struct s3c64xx_spi_dma_data *dma,
> struct s3c64xx_spi_driver_data *sdd;
> struct samsung_dma_prep info;
> struct samsung_dma_config config;
> + void __iomem *regs;
> + unsigned int mode_cfg;
>
> if (dma->direction == DMA_DEV_TO_MEM) {
> sdd = container_of((void *)dma,
> struct s3c64xx_spi_driver_data, rx_dma);
> +
> + regs = sdd->regs;
> + mode_cfg = readl(regs + S3C64XX_SPI_MODE_CFG);
> + if (mode_cfg & S3C64XX_SPI_MODE_4BURST)
> + config.maxburst = 4;
> + else
> + config.maxburst = 1;
> +
> config.direction = sdd->rx_dma.direction;
> config.fifo = sdd->sfr_start + S3C64XX_SPI_RX_DATA;
> config.width = sdd->cur_bpw / 8;
> @@ -298,6 +308,14 @@ static void prepare_dma(struct s3c64xx_spi_dma_data *dma,
> } else {
> sdd = container_of((void *)dma,
> struct s3c64xx_spi_driver_data, tx_dma);
> +
> + regs = sdd->regs;
> + mode_cfg = readl(regs + S3C64XX_SPI_MODE_CFG);
> + if (mode_cfg & S3C64XX_SPI_MODE_4BURST)
> + config.maxburst = 4;
> + else
> + config.maxburst = 1;
> +
> config.direction = sdd->tx_dma.direction;
> config.fifo = sdd->sfr_start + S3C64XX_SPI_TX_DATA;
> config.width = sdd->cur_bpw / 8;
> --
> 1.7.5.4
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.
prev parent reply other threads:[~2013-03-02 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 8:09 [PATCH v2 3/4] spi: s3c64xx: add dma maxburst size initialization Boojin Kim
2013-03-02 22:23 ` Grant Likely
2013-03-02 22:26 ` Grant Likely
2013-03-02 22:27 ` Grant Likely [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=20130302222710.AE2143E2E65@localhost \
--to=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).