From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Lukasz Czerwinski
<l.czerwinski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Mark Brown <broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] spi: Make core DMA mapping functions generate scatterlists
Date: Wed, 5 Feb 2014 07:30:57 +0100 [thread overview]
Message-ID: <201402050730.57398.marex@denx.de> (raw)
In-Reply-To: <1391349172-27668-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Sunday, February 02, 2014 at 02:52:52 PM, Mark Brown wrote:
Hi, thanks for preparing this patch!
I have just a few very minor nitpicks, ignore if you please.
[...]
> +static int spi_map_buf(struct spi_master *master, struct device *dev,
> + struct sg_table *sgt, void *buf, size_t len,
> + enum dma_data_direction dir)
> +{
> + const bool vmalloced_buf = is_vmalloc_addr(buf);
> + const int desc_len = vmalloced_buf ? PAGE_SIZE : master->max_dma_len;
You might want to rename this to "sg_chunk_max_size" or something, "desc_len"
doesn't make much sense here. The variable describes the maximum size of one
single scatterlist element.
> + const int sgs = DIV_ROUND_UP(len, desc_len);
Looking at this, the variables could generally use a more meaningful name. I
think it'd be clearer to call this "num_sg_chunks" or so ?
> + struct page *vm_page;
> + void *sg_buf;
> + size_t min;
> + int i, ret;
> +
> + ret = sg_alloc_table(sgt, sgs, GFP_KERNEL);
> + if (ret != 0)
> + return ret;
> +
> + for (i = 0; i < sgs; i++) {
> + min = min_t(size_t, len, desc_len);
> +
> + if (vmalloced_buf) {
> + vm_page = vmalloc_to_page(buf);
Just curious, but shouldn't we check if buf != NULL right at the begining of
this function?
[...]
> +static void spi_unmap_buf(struct spi_master *master, struct device *dev,
> + struct sg_table *sgt, enum dma_data_direction dir)
> +{
> + if (sgt->orig_nents) {
I don't want to nag, but why not use if (!sgt->...) return; ? This would cut
down one level of indent.
> + dma_unmap_sg(dev, sgt->sgl, sgt->orig_nents, dir);
> + sg_free_table(sgt);
> + }
> +}
> +
[...]
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-05 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 13:52 [PATCH] spi: Make core DMA mapping functions generate scatterlists Mark Brown
[not found] ` <1391349172-27668-1-git-send-email-broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2014-02-05 6:30 ` Marek Vasut [this message]
2014-02-05 12:00 ` Mark Brown
[not found] ` <20140205120002.GH22609-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-02-05 18:13 ` Marek Vasut
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=201402050730.57398.marex@denx.de \
--to=marex-ynqeqjnshbs@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=broonie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=l.czerwinski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).