public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sbabic@denx.de
To: Johannes Schneider <johannes.schneider@leica-geosystems.com>,
	u-boot@lists.denx.de
Subject: [PATCH v5 1/2] serial: mxc: enable the RX pipeline
Date: Sun, 18 Sep 2022 22:40:31 +0200 (CEST)	[thread overview]
Message-ID: <20220918204033.CD1C584A8A@phobos.denx.de> (raw)
In-Reply-To: <20220906121504.2200171-2-johannes.schneider@leica-geosystems.com>

> on imx8(mm) the RXDMUXSEL needs to be set for data going over the wire
> (as observable on a connected 'scope) to actually make it into the
> RXFIFO
> the reference manual is not overly clear about this, and only
> mentiones that "UCR3_RXDMUXSEL should always be set." - and since the
> CR3 register reverts to its reset values after setting the baudrate,
> setting this bit is done during '_mxc_serial_setbgr'
> Signed-off-by: Johannes Schneider <johannes.schneider@leica-geosystems.com>
> Reviewed-by: Peng Fan <peng.fan@nxp.com>
> Reviewed-by: Fabio Estevam <festevam@denx.de>
Applied to u-boot-imx, master, thanks !

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

  reply	other threads:[~2022-09-18 20:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 12:15 [PATCH v5 0/2] serial_mxc: fixing reception Johannes Schneider
2022-09-06 12:15 ` [PATCH v5 1/2] serial: mxc: enable the RX pipeline Johannes Schneider
2022-09-18 20:40   ` sbabic [this message]
2022-09-06 12:15 ` [PATCH v5 2/2] serial: mxc: have putc use the TXFIFO Johannes Schneider
2022-09-18 20:41   ` sbabic
2022-10-25 19:18   ` Tim Harvey
2022-10-25 20:23     ` Pali Rohár
2022-10-25 20:37       ` Fabio Estevam
2022-10-25 21:37         ` Tim Harvey
2022-10-25 21:48           ` Fabio Estevam
2022-10-25 22:19           ` Fabio Estevam
2022-10-26 10:10             ` Peng Fan
2022-10-26 10:15               ` Fabio Estevam
2022-10-26 17:45             ` Pali Rohár
2022-10-26 22:22               ` SCHNEIDER Johannes
2022-10-26 22:26                 ` Pali Rohár
2022-11-01 20:39                 ` Fabio Estevam
2022-11-02  5:16                   ` SCHNEIDER Johannes
2022-11-02 12:15                     ` Fabio Estevam
2022-11-02 12:38                       ` SCHNEIDER Johannes
2022-11-02 14:20                         ` Fabio Estevam
2022-11-02 17:24                           ` Pali Rohár
2022-11-02 18:37                             ` Fabio Estevam
2022-11-03  6:17                               ` SCHNEIDER Johannes
2022-11-03  8:35                                 ` TERTYCHNYI Grygorii
2022-11-03  8:47                                   ` Pali Rohár
2022-11-03 11:14                                 ` Fabio Estevam
2022-11-07 21:17                                   ` Fabio Estevam
2022-11-08  9:37                                     ` SCHNEIDER Johannes
2022-11-08 11:55                                       ` Fabio Estevam
2022-10-25 21:41         ` Pali Rohár

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=20220918204033.CD1C584A8A@phobos.denx.de \
    --to=sbabic@denx.de \
    --cc=johannes.schneider@leica-geosystems.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox