From: Henrik Grimler <henrik@grimler.se>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] serial: s5p: add compatible for exynos8895
Date: Fri, 24 Oct 2025 07:47:58 +0200 [thread overview]
Message-ID: <20251024054758.GA10245@localhost> (raw)
In-Reply-To: <20251017-serial-s5p-exynos8895-v1-1-b412dd112cfd@disroot.org>
Hi Kaustabh,
On Fri, Oct 17, 2025 at 08:59:22PM +0530, Kaustabh Chakraborty wrote:
> Add the compatible for Exynos8895 UART as described in upstream
> devicetree bindings. This enables support for Exynos8895 and other
> similar UART devices, such as Exynos7870. Other than that, the driver
> works as-is.
>
> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
Reviewed-by: Henrik Grimler <henrik@grimler.se>
Thanks!
> ---
> drivers/serial/serial_s5p.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/serial/serial_s5p.c b/drivers/serial/serial_s5p.c
> index 734780a124ad47ed97811784edfdb45a75d37bf7..d46a88610ab88a227aa07b10c62576a13168bfbc 100644
> --- a/drivers/serial/serial_s5p.c
> +++ b/drivers/serial/serial_s5p.c
> @@ -258,6 +258,7 @@ static const struct dm_serial_ops s5p_serial_ops = {
> static const struct udevice_id s5p_serial_ids[] = {
> { .compatible = "samsung,exynos4210-uart", .data = PORT_S5P },
> { .compatible = "samsung,exynos850-uart", .data = PORT_S5P },
> + { .compatible = "samsung,exynos8895-uart", .data = PORT_S5P },
> { .compatible = "apple,s5l-uart", .data = PORT_S5L },
> { }
> };
>
> ---
> base-commit: 582a04763aa80738c1c8ac60c47d1a5159a42833
> change-id: 20251014-serial-s5p-exynos8895-3303dfe3a99b
>
> Best regards,
> --
> Kaustabh Chakraborty <kauschluss@disroot.org>
>
next prev parent reply other threads:[~2025-10-24 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 15:29 [PATCH] serial: s5p: add compatible for exynos8895 Kaustabh Chakraborty
2025-10-24 5:47 ` Henrik Grimler [this message]
2025-11-26 8:48 ` Minkyu Kang
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=20251024054758.GA10245@localhost \
--to=henrik@grimler.se \
--cc=kauschluss@disroot.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.