From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: max310x: add comments for membase address workaround
Date: Fri, 4 Aug 2023 15:07:50 +0200 [thread overview]
Message-ID: <2023080417-surname-sizzling-591e@gregkh> (raw)
In-Reply-To: <20230803140551.970141-1-hugo@hugovil.com>
On Thu, Aug 03, 2023 at 10:05:51AM -0400, Hugo Villeneuve wrote:
> From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
>
> Add comments about workaround used to configure membase address. This
> follows suggestions made during review of a sc16is7xx driver patch to
> add the same workaround.
>
> Link: https://lore.kernel.org/lkml/2936e18f-44ea-faed-9fa0-2ddefe7c3194@linux.intel.com
> Link: https://lore.kernel.org/lkml/20230801131655.80bd8f97f018dda6155d65f6@hugovil.com/
> Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> ---
> drivers/tty/serial/max310x.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/tty/serial/max310x.c b/drivers/tty/serial/max310x.c
> index 416d553b73a7..5903dd033fd0 100644
> --- a/drivers/tty/serial/max310x.c
> +++ b/drivers/tty/serial/max310x.c
> @@ -1369,6 +1369,11 @@ static int max310x_probe(struct device *dev, const struct max310x_devtype *devty
> s->p[i].port.flags = UPF_FIXED_TYPE | UPF_LOW_LATENCY;
> s->p[i].port.iotype = UPIO_PORT;
> s->p[i].port.iobase = i;
> + /*
> + * Use all ones as membase to make sure uart_configure_port() in
> + * serial_core.c does not abort for SPI/I2C devices where the
> + * membase address is not applicable.
> + */
> s->p[i].port.membase = (void __iomem *)~0;
> s->p[i].port.uartclk = uartclk;
> s->p[i].port.rs485_config = max310x_rs485_config;
>
> base-commit: 426263d5fb400ccde5444748693dc75bda18f01e
> --
> 2.30.2
>
Meta-comment, your email system is not correct and is not able to be
verified as I get the following when attempting to apply your patch:
---
✗ [PATCH] serial: max310x: add comments for membase address workaround
---
✗ BADSIG: DKIM/hugovil.com
Please fix up for future submissions.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-04 13:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:05 [PATCH] serial: max310x: add comments for membase address workaround Hugo Villeneuve
2023-08-04 13:07 ` Greg Kroah-Hartman [this message]
2023-08-04 14:17 ` Hugo Villeneuve
2023-08-07 15:24 ` Hugo Villeneuve
2023-08-07 15:27 ` Greg Kroah-Hartman
2023-08-07 20:23 ` Hugo Villeneuve
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=2023080417-surname-sizzling-591e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hugo@hugovil.com \
--cc=hvilleneuve@dimonoff.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox