linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-clk <linux-clk@vger.kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] clk: renesas: rcar-gen3: remove stp_ck handling for SDHI
Date: Wed, 23 Sep 2020 10:33:13 +0200	[thread overview]
Message-ID: <CAMuHMdUw99vAgBevAHmthEUgGQepTof9skjAeBNwxiHHbMk-5w@mail.gmail.com> (raw)
In-Reply-To: <20200922120036.10298-1-wsa+renesas@sang-engineering.com>

Hi Wolfram,

On Tue, Sep 22, 2020 at 2:00 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> There is no case (and none foreseen) where we would need to disable the
> SDn clock. So, for simplicity, remove its handling.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> Geert seems to favor simplicity, too. So, now this patch leaves RFC
> status.
>
> Change since RFC: * fixed typo in commit message

Thanks for the update!

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in clk-renesas-for-v5.11.

Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>
(on Salvator-X(S) with R-Car H3 ES1.0 and ES2.0, M3-W ES1.0, M3-N ES1.0,
 and on Ebisu-4D with R-Car E3 ES1.0).

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:[~2020-09-23  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 12:00 [PATCH] clk: renesas: rcar-gen3: remove stp_ck handling for SDHI Wolfram Sang
2020-09-23  8:33 ` Geert Uytterhoeven [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=CAMuHMdUw99vAgBevAHmthEUgGQepTof9skjAeBNwxiHHbMk-5w@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=linux-clk@vger.kernel.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 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).