From: Yakir Yang <ykk@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: rk3036: enable the CLK_IGNORE_UNUSED flag for hclk_vio_bus
Date: Mon, 18 Jan 2016 18:44:16 +0800 [thread overview]
Message-ID: <569CC200.1050504@rock-chips.com> (raw)
In-Reply-To: <1816378.OnNVlMiORS@phil>
On 01/18/2016 03:14 AM, Heiko Stuebner wrote:
> Am Freitag, 15. Januar 2016, 19:54:14 schrieb Yakir Yang:
>> HCLK_VIO_BUS is the noc bus controller clock for display module,
>> due to it shouldn't belong to any driver, but we need it enabled,
>> so just mark it as the CLK_IGNORE_UNUSED flag.
>>
>> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
> applied to my clk-branch for 4.6
Thanks ;)
- Yakir
> Thanks
> Heiko
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: ykk@rock-chips.com (Yakir Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: rockchip: rk3036: enable the CLK_IGNORE_UNUSED flag for hclk_vio_bus
Date: Mon, 18 Jan 2016 18:44:16 +0800 [thread overview]
Message-ID: <569CC200.1050504@rock-chips.com> (raw)
In-Reply-To: <1816378.OnNVlMiORS@phil>
On 01/18/2016 03:14 AM, Heiko Stuebner wrote:
> Am Freitag, 15. Januar 2016, 19:54:14 schrieb Yakir Yang:
>> HCLK_VIO_BUS is the noc bus controller clock for display module,
>> due to it shouldn't belong to any driver, but we need it enabled,
>> so just mark it as the CLK_IGNORE_UNUSED flag.
>>
>> Signed-off-by: Yakir Yang <ykk@rock-chips.com>
> applied to my clk-branch for 4.6
Thanks ;)
- Yakir
> Thanks
> Heiko
>
>
>
next prev parent reply other threads:[~2016-01-18 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 11:54 [PATCH] clk: rockchip: rk3036: enable the CLK_IGNORE_UNUSED flag for hclk_vio_bus Yakir Yang
2016-01-15 11:54 ` Yakir Yang
2016-01-17 19:14 ` Heiko Stuebner
2016-01-17 19:14 ` Heiko Stuebner
2016-01-17 19:14 ` Heiko Stuebner
2016-01-18 10:44 ` Yakir Yang [this message]
2016-01-18 10:44 ` Yakir Yang
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=569CC200.1050504@rock-chips.com \
--to=ykk@rock-chips.com \
--cc=heiko@sntech.de \
--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@codeaurora.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.