From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Maximilian Luz <luzmaximilian@gmail.com>
Cc: "open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wang Hongcheng <annie.wang@amd.com>, Ken Xue <Ken.Xue@amd.com>
Subject: Re: Support for AMDI0022 UART
Date: Sat, 24 Apr 2021 13:25:54 +0300 [thread overview]
Message-ID: <CAHp75VcLoTsjyQyVAo6cd+HMd+z_irM8ofcenRm0P6CzYGOQNw@mail.gmail.com> (raw)
In-Reply-To: <295686a0-240d-71d1-a6a0-f3752cf24477@gmail.com>
On Fri, Apr 23, 2021 at 10:58 PM Maximilian Luz <luzmaximilian@gmail.com> wrote:
>
> Hi all,
>
> I received a report from a Surface Laptop 4 which has a UART that is
> identified as AMDI0022 in ACPI [1] and that does not seem to be
> supported by the kernel yet.
>
> From what I can tell via ACPI, this is similar to the AMDI0020 [2] UART
> that's already supported by the kernel (well, both are devices with two
> MMIO regions and an interrupt as far as I can tell...). So it's possible
> that all that's needed is adding it to the respective device ID lists
> [3, 4]. Unfortunately, I a) don't have a device to test this myself, b)
> haven't found any more details on that online, and c) don't want to tell
> others to test this without knowing a bit more about that (potentially
> writing random stuff to some unknown MMIO region that I don't know
> anything about doesn't sound as safe to me as I'd like).
To me they look completely the same. Depending on the device which is
connected to the UART, I would suggest just to add an ID and see if it
makes it work.
> Does anyone here have some pointers on what it'd take to support this,
> or any contacts at AMD that could provide more insight?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-24 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 19:57 Support for AMDI0022 UART Maximilian Luz
2021-04-24 10:25 ` Andy Shevchenko [this message]
2021-04-30 12:37 ` Maximilian Luz
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=CAHp75VcLoTsjyQyVAo6cd+HMd+z_irM8ofcenRm0P6CzYGOQNw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Ken.Xue@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=annie.wang@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luzmaximilian@gmail.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).