From: John Ogness <john.ogness@linutronix.de>
To: Esben Haabendal <esben@geanix.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/2] serial: imx: Switch to nbcon console
Date: Fri, 13 Sep 2024 10:05:50 +0206 [thread overview]
Message-ID: <84ed5o9e6h.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <87frq459iv.fsf@geanix.com>
On 2024-09-13, Esben Haabendal <esben@geanix.com> wrote:
> I have now gone through all usage of above mentioned registers in the
> driver. I found a single missing lock/unlock, but other than that the
> driver seems to be in good shape in this regards.
Great. Please send a separate patch for the missing lock/unlock to
mainline. It should be a mainline problem as well.
> In the _probe() function, the following registers are accessed
> unprotected: ucr1, ucr2, ucr3, uts. But I assume this should be safe,
> as the uart port is not registred yet, and interrupt handlers have not
> been registered.
Sure.
> I will send out a v3 short, hoping we can get this in a shape where we
> can get it merged shortly after the 8250 driver nbcon patches.
Great!
Note that I am currently pushing the 8250 nbcon to mainline. It is in
the review process and there have already been significant changes. It
is all 8250-specific changes, so it probably is not related to your
work. Just letting you know. I will CC you on the next series
submission.
John Ogness
next prev parent reply other threads:[~2024-09-13 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 7:56 [RFC PATCH v2 0/2] serial: imx: Switch to nbcon console Esben Haabendal
2024-04-05 7:56 ` [RFC PATCH v2 1/2] serial: imx: Introduce timeout when waiting on transmitter empty Esben Haabendal
2024-04-05 8:06 ` Marc Kleine-Budde
2024-04-05 8:32 ` Esben Haabendal
2024-04-05 7:56 ` [RFC PATCH v2 2/2] serial: imx: Switch to nbcon console Esben Haabendal
2024-04-15 10:28 ` John Ogness
2024-09-13 6:54 ` Esben Haabendal
2024-09-13 7:59 ` John Ogness [this message]
2024-09-13 8:29 ` Esben Haabendal
2024-04-05 8:43 ` [RFC PATCH v2 0/2] " Marc Kleine-Budde
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=84ed5o9e6h.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=esben@geanix.com \
--cc=linux-rt-users@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