All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Katsuhiro Suzuki <katsuhiro@katsuster.net>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: fix I2S1 clock gate register for rk3328
Date: Mon, 19 Nov 2018 14:40:06 +0100	[thread overview]
Message-ID: <22369238.AtuRxmQGGH@phil> (raw)
In-Reply-To: <20181118041612.2773-1-katsuhiro@katsuster.net>

Am Sonntag, 18. November 2018, 05:16:12 CET schrieb Katsuhiro Suzuki:
> This patch fixes definition of I2S1 clock gate register for rk3328.
> Current setting is not related I2S clocks.
>   - bit6 of CRU_CLKGATE_CON0 means clk_ddrmon_en
>   - bit6 of CRU_CLKGATE_CON1 means clk_i2s1_en
> 
> Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>

applied for 4.21


Thanks
Heiko



WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: fix I2S1 clock gate register for rk3328
Date: Mon, 19 Nov 2018 14:40:06 +0100	[thread overview]
Message-ID: <22369238.AtuRxmQGGH@phil> (raw)
In-Reply-To: <20181118041612.2773-1-katsuhiro@katsuster.net>

Am Sonntag, 18. November 2018, 05:16:12 CET schrieb Katsuhiro Suzuki:
> This patch fixes definition of I2S1 clock gate register for rk3328.
> Current setting is not related I2S clocks.
>   - bit6 of CRU_CLKGATE_CON0 means clk_ddrmon_en
>   - bit6 of CRU_CLKGATE_CON1 means clk_i2s1_en
> 
> Signed-off-by: Katsuhiro Suzuki <katsuhiro@katsuster.net>

applied for 4.21


Thanks
Heiko

  reply	other threads:[~2018-11-19 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18  4:16 [PATCH] clk: rockchip: fix I2S1 clock gate register for rk3328 Katsuhiro Suzuki
2018-11-18  4:16 ` Katsuhiro Suzuki
2018-11-18  4:16 ` Katsuhiro Suzuki
2018-11-19 13:40 ` Heiko Stuebner [this message]
2018-11-19 13:40   ` Heiko Stuebner

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=22369238.AtuRxmQGGH@phil \
    --to=heiko@sntech.de \
    --cc=katsuhiro@katsuster.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 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.