From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>,
<wsa@the-dreams.de>, <geert@linux-m68k.org>,
<linux-renesas-soc@vger.kernel.org>
Cc: <linux-serial@vger.kernel.org>,
Dirk Behme <dirk.behme@de.bosch.com>,
Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>,
"George G. Davis" <george_davis@mentor.com>,
Andy Lowe <andy_lowe@mentor.com>,
Joshua Frkuska <joshua_frkuska@mentor.com>,
Tobias Franzen <tfranzen@de.adit-jv.com>, <magnus.damm@gmail.com>,
<greg@kroah.com>
Subject: Re: [PATCH v2] serial: sh-sci: Support for HSCIF RX sampling point adjustment
Date: Wed, 27 Mar 2019 19:35:55 +0100 [thread overview]
Message-ID: <20190327183555.GA23991@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <1522856931-6225-1-git-send-email-ulrich.hecht+renesas@gmail.com>
Dear Renesas Open Source team,
We've recently switched from rcar-3.7.x to rcar-3.9.x [1] kernel and the
latter contains this patch [2] by virtue of rcar-3.9.0 commit [3], which
mirrors v4.18-rc1 commit [4] in mainline.
JFYI, quite far away in the delivery chain, we've received below report:
> With this patch [2-4] there are reports about broken data
> communication with 115200 baud with SXM module. Reverting
> this patch results in successful communication, again.
While this scarce information barely helps anybody, I thought that
sharing it with you might be beneficial in case you collect several
reports linked to this specific commit in future, meaning it potentially
adds a regression.
Also, if you are aware of any userland changes that might be
required/assumed by this patch or in case you have any alternative
ideas how to avoid reverting this patch, your feedback would be very
appreciated.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tag/?h=rcar-3.9.3
[2] https://patchwork.kernel.org/patch/10322809/
[3] https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/commit/?id=e395fc813539
[4] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63ba1e00f178
Best regards,
Eugeniu.
next prev parent reply other threads:[~2019-03-27 18:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 15:48 [PATCH v2] serial: sh-sci: Support for HSCIF RX sampling point adjustment Ulrich Hecht
2018-04-24 15:15 ` Geert Uytterhoeven
2019-03-27 18:35 ` Eugeniu Rosca [this message]
2019-03-28 8:33 ` Wolfram Sang
2019-03-28 9:24 ` Geert Uytterhoeven
2019-03-28 10:16 ` Dirk Behme
2019-03-28 11:30 ` Dirk Behme
2019-03-29 7:05 ` Dirk Behme
2019-03-29 9:46 ` Ulrich Hecht
2019-03-29 9:56 ` Geert Uytterhoeven
2019-03-29 10:35 ` Ulrich Hecht
2019-03-29 11:01 ` Ulrich Hecht
2019-03-29 11:17 ` Dirk Behme
2019-03-29 9:46 ` Geert Uytterhoeven
2019-03-29 12:13 ` Dirk Behme
2019-03-29 13:00 ` Geert Uytterhoeven
2019-03-29 14:11 ` Ulrich Hecht
2019-04-01 6:05 ` Dirk Behme
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=20190327183555.GA23991@vmlxhi-102.adit-jv.com \
--to=erosca@de.adit-jv.com \
--cc=andy_lowe@mentor.com \
--cc=dirk.behme@de.bosch.com \
--cc=geert@linux-m68k.org \
--cc=george_davis@mentor.com \
--cc=greg@kroah.com \
--cc=joshua_frkuska@mentor.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=roscaeugeniu@gmail.com \
--cc=tfranzen@de.adit-jv.com \
--cc=ulrich.hecht+renesas@gmail.com \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).