From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/8] serial: sh-sci: Use offset_in_page() helper instead of open coding
Date: Sat, 23 May 2015 19:13:46 +0000 [thread overview]
Message-ID: <1521242.0sxhMsOBq0@avalon> (raw)
In-Reply-To: <1432145174-11534-6-git-send-email-geert+renesas@glider.be>
Hi Geert,
Thank you for the patch.
On Wednesday 20 May 2015 20:06:11 Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/tty/serial/sh-sci.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/serial/sh-sci.c b/drivers/tty/serial/sh-sci.c
> index 73f4115159a7fbbc..d2734e13b17bf720 100644
> --- a/drivers/tty/serial/sh-sci.c
> +++ b/drivers/tty/serial/sh-sci.c
> @@ -1715,10 +1715,10 @@ static void sci_request_dma(struct uart_port *port)
> s->chan_tx = chan;
> sg_init_table(&s->sg_tx, 1);
> /* UART circular tx buffer is an aligned page. */
> - BUG_ON((uintptr_t)port->state->xmit.buf & ~PAGE_MASK);
> + BUG_ON(offset_in_page(port->state->xmit.buf));
> sg_set_page(&s->sg_tx, virt_to_page(port->state->xmit.buf),
> UART_XMIT_SIZE,
> - (uintptr_t)port->state->xmit.buf & ~PAGE_MASK);
> + offset_in_page(port->state->xmit.buf));
If a non-zero offset is a bug, do we really need to pass it to sg_set_page()
here and below ? I also expect this code to be simplified if we switch to
dma_map_single().
> nent = dma_map_sg(chan->device->dev, &s->sg_tx, 1,
> DMA_TO_DEVICE);
> if (!nent)
> @@ -1768,7 +1768,7 @@ static void sci_request_dma(struct uart_port *port)
>
> sg_init_table(sg, 1);
> sg_set_page(sg, virt_to_page(buf[i]), s->buf_len_rx,
> - (uintptr_t)buf[i] & ~PAGE_MASK);
> + offset_in_page(buf[i]));
> sg_dma_address(sg) = dma[i];
> }
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2015-05-23 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:06 [PATCH 5/8] serial: sh-sci: Use offset_in_page() helper instead of open coding Geert Uytterhoeven
2015-05-23 19:13 ` Laurent Pinchart [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=1521242.0sxhMsOBq0@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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 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.