From: Thierry Reding <treding@nvidia.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: Add Tegra Combined UART driver
Date: Thu, 7 Feb 2019 17:08:02 +0100 [thread overview]
Message-ID: <20190207160801.GA6991@ulmo> (raw)
In-Reply-To: <20190207143916.GA11121@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Thu, Feb 07, 2019 at 06:39:16AM -0800, Guenter Roeck wrote:
> On Wed, Jan 23, 2019 at 11:28:19AM +0100, Thierry Reding wrote:
> > The Tegra Combined UART (TCU) is a mailbox-based mechanism that allows
> > multiplexing multiple "virtual UARTs" into a single hardware serial
> > port. The TCU is the primary serial port on Tegra194 devices.
> >
> > Add a TCU driver utilizing the mailbox framework, as the used mailboxes
> > are part of Tegra HSP blocks that are already controlled by the Tegra
> > HSP mailbox driver.
> >
> > Based on work by Mikko Perttunen <mperttunen@nvidia.com>.
> >
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> In case 0day hasn't reported it:
>
> arm64:allmodconfig:
>
> ERROR: "mbox_flush" [drivers/tty/serial/tegra-tcu.ko] undefined!
>
> mbox_flush() isn't exported.
We only ever test TCU as built-in because it's used for the system
console, so I never actually tested this as a module. I sent a fix
for this earlier this week:
https://lore.kernel.org/patchwork/patch/1038464/
Thanks,
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-07 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 14:39 [PATCH] serial: Add Tegra Combined UART driver Guenter Roeck
2019-02-07 16:08 ` Thierry Reding [this message]
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=20190207160801.GA6991@ulmo \
--to=treding@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.