linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/7] clk: rockchip: add clock flag parameter when register pll
Date: Fri, 05 Aug 2016 10:55:44 +0200	[thread overview]
Message-ID: <1618511.YfjKKMY3nc@diego> (raw)
In-Reply-To: <57A45369.7020804@gmail.com>

Hi Lin,

Am Freitag, 5. August 2016, 16:50:49 schrieb hl:
> On 2016?08?05? 06:37, Heiko Stuebner wrote:
> > Am Freitag, 29. Juli 2016, 15:56:55 schrieb Lin Huang:
> >> From: Heiko St?bner <heiko@sntech.de>
> >> 
> >> add clock flag parameter so we can pass specific clock flag
> >> (like CLK_GET_RATE_NOCACHE etc..)to pll driver.
> >> 
> >> Signed-off-by: Heiko St?bner <heiko@sntech.de>
> >> Signed-off-by: Lin Huang <hl@rock-chips.com>
> > 
> > applied to my clock branch for 4.9 after some minor edits on the commit
> > message.
> 
>   I can not found your clock branch for 4.9, can you share me the patch
> ID, i want
> cherry-pick it to my downstream branch.

sorry forgot to push yesterday evening. The patch is at [0].

Please keep in mind, that I'll rebase that branch onto 4.8-rc1 once it 
gets released on sunday. So the commit id is volatile till then.
[Same is true for all my 4.9 branch of course, I just pick patches already
to reduce the number of patches in my inbox :-) ]


Heiko

[0] https://git.kernel.org/cgit/linux/kernel/git/mmind/linux-rockchip.git/commit/?h=v4.9-clk/next&id=24bdd1a5a2cc706b8c4820a1976dd4eed56716e4

  reply	other threads:[~2016-08-05  8:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160729075805epcas1p2fa2fab53fc8cdfdf42f53e99a0a72e6a@epcas1p2.samsung.com>
2016-07-29  7:56 ` [PATCH v4 0/7] rk3399 support ddr frequency scaling Lin Huang
2016-07-29  7:56   ` [PATCH v4 1/7] clk: rockchip: add clock flag parameter when register pll Lin Huang
2016-08-04 22:37     ` Heiko Stuebner
2016-08-05  8:50       ` hl
2016-08-05  8:55         ` Heiko Stübner [this message]
2016-07-29  7:56   ` [PATCH v4 2/7] clk: rockchip: add new clock-type for the ddrclk Lin Huang
2016-08-04 20:23     ` Heiko Stübner
2016-08-04 22:42       ` Heiko Stuebner
2016-07-29  7:56   ` [PATCH v4 3/7] clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc Lin Huang
2016-08-04 22:40     ` Heiko Stuebner
2016-07-29  7:56   ` [PATCH v4 4/7] clk: rockchip: rk3399: add ddrc clock support Lin Huang
2016-07-29  7:56   ` [PATCH v4 5/7] PM / devfreq: event: support rockchip dfi controller Lin Huang
2016-08-01  7:41     ` Chanwoo Choi
2016-08-01  8:08       ` Chanwoo Choi
2016-08-01  8:27         ` hl
2016-08-01 10:31           ` Chanwoo Choi
2016-07-29  7:57   ` [PATCH v4 6/7] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc Lin Huang
2016-08-01 10:28     ` Chanwoo Choi
2016-08-02  1:03       ` hl
2016-08-02  4:21         ` Chanwoo Choi
2016-08-03  7:38           ` hl
2016-08-04  0:33             ` Chanwoo Choi
2016-07-29  7:57   ` [PATCH v4 7/7] drm/rockchip: Add dmc notifier in vop driver Lin Huang
2016-08-01  7:39   ` [PATCH v4 0/7] rk3399 support ddr frequency scaling Chanwoo Choi
2016-08-01  7:46     ` hl
2016-08-01  7:50       ` Chanwoo Choi
2016-08-05 13:48   ` Tomeu Vizoso

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=1618511.YfjKKMY3nc@diego \
    --to=heiko@sntech.de \
    --cc=linux-arm-kernel@lists.infradead.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 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).