From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] clk: si5351: Some fixes
Date: Sat, 2 May 2015 10:53:44 +0200 [thread overview]
Message-ID: <20150502105344.5b78bd20@armhf> (raw)
In-Reply-To: <554347AA.3070502@gmail.com>
On Fri, 01 May 2015 11:30:18 +0200
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> > I applied the patches 2 and 3, and the audio and video in the Cubox
> > work fine again. Thanks.
>
> Ok, good. You mentioned that on v3.19-rc1 it still "works" i.e. despite
> the broken/missing clk_get/clk_prepare_enable?
>
> Can you check the stable (v3.19, v4.0) versions and see how far we
> should backport the fix?
v3.19 works, v4.0 does not.
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2015-05-02 8:53 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 17:45 [PATCH 0/4] clk: si5351: Some fixes Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 17:45 ` [PATCH 1/4] clk: si5351: Mention clock-names in the binding documentation Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 17:45 ` [PATCH 2/4] ARM: dove: Add clock-names to CuBox Si5351 clk generator Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 17:45 ` [PATCH 3/4] clk: si5351: Do not pass struct clk in platform_data Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 18:20 ` Fabio Estevam
2015-04-30 18:20 ` Fabio Estevam
2015-04-30 18:30 ` Michael Welling
2015-04-30 18:30 ` Michael Welling
2015-04-30 18:44 ` Sebastian Hesselbarth
2015-04-30 18:44 ` Sebastian Hesselbarth
2015-04-30 19:16 ` Fabio Estevam
2015-04-30 19:16 ` Fabio Estevam
2015-04-30 20:46 ` Sebastian Hesselbarth
2015-04-30 20:46 ` Sebastian Hesselbarth
2015-04-30 17:45 ` [PATCH 4/4] clk: si5351: Reset PLL after rate change Sebastian Hesselbarth
2015-04-30 17:45 ` Sebastian Hesselbarth
2015-04-30 18:49 ` Michael Welling
2015-04-30 18:49 ` Michael Welling
2015-04-30 18:58 ` Sebastian Hesselbarth
2015-04-30 18:58 ` Sebastian Hesselbarth
2015-04-30 18:47 ` [PATCH 0/4] clk: si5351: Some fixes Michael Welling
2015-04-30 18:47 ` Michael Welling
2015-04-30 19:33 ` Michael Welling
2015-04-30 19:33 ` Michael Welling
2015-04-30 19:33 ` Michael Welling
2015-04-30 20:44 ` Sebastian Hesselbarth
2015-04-30 20:44 ` Sebastian Hesselbarth
2015-04-30 20:44 ` Sebastian Hesselbarth
2015-04-30 21:20 ` Michael Welling
2015-04-30 21:20 ` Michael Welling
2015-04-30 21:20 ` Michael Welling
2015-04-30 22:21 ` Sebastian Hesselbarth
2015-04-30 22:21 ` Sebastian Hesselbarth
2015-04-30 22:21 ` Sebastian Hesselbarth
2015-04-30 22:36 ` Michael Welling
2015-04-30 22:36 ` Michael Welling
2015-04-30 22:36 ` Michael Welling
2015-05-01 8:17 ` Sebastian Hesselbarth
2015-05-01 8:17 ` Sebastian Hesselbarth
2015-05-01 8:17 ` Sebastian Hesselbarth
2015-05-08 0:52 ` Michael Welling
2015-05-08 0:52 ` Michael Welling
2015-05-01 9:14 ` Jean-Francois Moine
2015-05-01 9:14 ` Jean-Francois Moine
2015-05-01 9:14 ` Jean-Francois Moine
2015-05-01 9:14 ` Jean-Francois Moine
2015-05-01 9:30 ` Sebastian Hesselbarth
2015-05-01 9:30 ` Sebastian Hesselbarth
2015-05-02 8:53 ` Jean-Francois Moine [this message]
2015-05-02 8:55 ` Jean-Francois Moine
2015-05-02 8:55 ` Jean-Francois Moine
2015-05-02 8:55 ` Jean-Francois Moine
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=20150502105344.5b78bd20@armhf \
--to=moinejf@free.fr \
--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 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.