All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: renesas: ulcb-kf: remove flow control for SCIF1
Date: Tue, 30 May 2023 11:11:43 +0200	[thread overview]
Message-ID: <CAMuHMdVMOG-PtZtstOLZU9LWJ8v3Rh9QSdKWZVa7iFs54Lha8A@mail.gmail.com> (raw)
In-Reply-To: <20230525084823.4195-2-wsa+renesas@sang-engineering.com>

On Thu, May 25, 2023 at 10:48 AM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> The schematics are misleading, the flow control is for HSCIF1. We need
> SCIF1 for GNSS/GPS which does not use flow control.
>
> Fixes: c6c816e22bc8 ("arm64: dts: ulcb-kf: enable SCIF1")
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks, will queue in renesas-devel for v6.5.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2023-05-30  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25  8:48 [PATCH v2 0/2] KingFisher: fix SCIF1, add HSCIF1 Wolfram Sang
2023-05-25  8:48 ` [PATCH v2 1/2] arm64: dts: renesas: ulcb-kf: remove flow control for SCIF1 Wolfram Sang
2023-05-30  9:11   ` Geert Uytterhoeven [this message]
2023-05-25  8:48 ` [PATCH v2 2/2] arm64: dts: renesas: ulcb-kf: add HSCIF1 node Wolfram Sang
2023-05-30  9:12   ` Geert Uytterhoeven

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=CAMuHMdVMOG-PtZtstOLZU9LWJ8v3Rh9QSdKWZVa7iFs54Lha8A@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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.