From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Harshit Shah <hshah@axiado.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Michal Simek <michal.simek@amd.com>,
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: Sat, 23 Aug 2025 08:36:30 +0200 [thread overview]
Message-ID: <2025082322-speech-blaming-b075@gregkh> (raw)
In-Reply-To: <20250822-xilinx-uartps-reg-size-v1-1-78a5c63cb6df@axiado.com>
On Fri, Aug 22, 2025 at 11:58:14AM -0700, 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.
>
> Fixes: 1f7055779001 ("arm64: dts: axiado: Add initial support for AX3000 SoC and eval board")
> 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.
>
> Acked-by: Michal Simek <michal.simek@amd.com>
> Signed-off-by: Harshit Shah <hshah@axiado.com>
> ---
> - Add fixes tag in commit msg
That fixes tag needs to go where the signed-off-by area is. See the
many examples on the lists and in the tree itself for specifics.
> - Link to v1: https://lore.kernel.org/r/20250819-xilinx-uartps-reg-size-v1-1-0fb7341023fb@axiado.com
Then why is this one not marked "v2"?
Can you fix this all up and send a v3?
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-23 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 18:58 [PATCH] serial: xilinx_uartps: read reg size from DTS Harshit Shah
2025-08-23 6:36 ` Greg Kroah-Hartman [this message]
2025-08-26 17:23 ` Harshit Shah
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 20:53 Harshit Shah
2025-08-20 6:58 ` Michal Simek
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=2025082322-speech-blaming-b075@gregkh \
--to=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 \
--cc=michal.simek@amd.com \
/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).