From: Michal Simek <michal.simek@amd.com>
To: Harshit Shah <hshah@axiado.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] serial: xilinx_uartps: read reg size from DTS
Date: Wed, 20 Aug 2025 08:58:13 +0200 [thread overview]
Message-ID: <59692110-eca9-4f0f-b6f9-e23bf835733c@amd.com> (raw)
In-Reply-To: <20250819-xilinx-uartps-reg-size-v1-1-0fb7341023fb@axiado.com>
On 8/19/25 22:53, Harshit Shah wrote:
> Current implementation uses `CDNS_UART_REGISTER_SPACE(0x1000)`
> for request_mem_region() and ioremap() in cdns_uart_request_port() API.
>
> The cadence/xilinx IP has register space defined from offset 0x0 to 0x48.
> It also mentions that the register map is defined as [6:0]. So, the upper
> region may/maynot be used based on the IP integration.
>
> In Axiado AX3000 SoC two UART instances are defined
> 0x100 apart. That is creating issue in some other instance due to overlap
> with addresses.
>
> Since, this address space is already being defined in the
> devicetree, use the same when requesting the register space.
>
> Signed-off-by: Harshit Shah <hshah@axiado.com>
> ---
> drivers/tty/serial/xilinx_uartps.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
> index fe457bf1e15bb4fc77a5c7de2aea8bfbdbaa643a..a66b44d21fba2558d0b2a62864d86d3b73152e26 100644
> --- a/drivers/tty/serial/xilinx_uartps.c
> +++ b/drivers/tty/serial/xilinx_uartps.c
> @@ -33,7 +33,6 @@
> #define CDNS_UART_MINOR 0 /* works best with devtmpfs */
> #define CDNS_UART_NR_PORTS 16
> #define CDNS_UART_FIFO_SIZE 64 /* FIFO size */
> -#define CDNS_UART_REGISTER_SPACE 0x1000
> #define TX_TIMEOUT 500000
>
> /* Rx Trigger level */
> @@ -1098,15 +1097,15 @@ static int cdns_uart_verify_port(struct uart_port *port,
> */
> static int cdns_uart_request_port(struct uart_port *port)
> {
> - if (!request_mem_region(port->mapbase, CDNS_UART_REGISTER_SPACE,
> + if (!request_mem_region(port->mapbase, port->mapsize,
> CDNS_UART_NAME)) {
> return -ENOMEM;
> }
>
> - port->membase = ioremap(port->mapbase, CDNS_UART_REGISTER_SPACE);
> + port->membase = ioremap(port->mapbase, port->mapsize);
> if (!port->membase) {
> dev_err(port->dev, "Unable to map registers\n");
> - release_mem_region(port->mapbase, CDNS_UART_REGISTER_SPACE);
> + release_mem_region(port->mapbase, port->mapsize);
> return -ENOMEM;
> }
> return 0;
> @@ -1121,7 +1120,7 @@ static int cdns_uart_request_port(struct uart_port *port)
> */
> static void cdns_uart_release_port(struct uart_port *port)
> {
> - release_mem_region(port->mapbase, CDNS_UART_REGISTER_SPACE);
> + release_mem_region(port->mapbase, port->mapsize);
> iounmap(port->membase);
> port->membase = NULL;
> }
> @@ -1780,6 +1779,7 @@ static int cdns_uart_probe(struct platform_device *pdev)
> * and triggers invocation of the config_port() entry point.
> */
> port->mapbase = res->start;
> + port->mapsize = resource_size(res);
> port->irq = irq;
> port->dev = &pdev->dev;
> port->uartclk = clk_get_rate(cdns_uart_data->uartclk);
>
> ---
> base-commit: 8742b2d8935f476449ef37e263bc4da3295c7b58
> change-id: 20250813-xilinx-uartps-reg-size-c3be67d88b7c
>
> Best regards,
yes. There is no reason to hardcode it to 0x1000. Only 0x48 is used on our
silicon. Information about size can be taken from DT.
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2025-08-20 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 20:53 Harshit Shah
2025-08-20 6:58 ` Michal Simek [this message]
2025-08-22 18:58 Harshit Shah
2025-08-23 6:36 ` Greg Kroah-Hartman
2025-08-26 17:23 ` Harshit Shah
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=59692110-eca9-4f0f-b6f9-e23bf835733c@amd.com \
--to=michal.simek@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=hshah@axiado.com \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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
all inboxes | Powered by JetHome®