linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: trblinux@gmail.com (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] clk: exynos-audss: Keep the parent of mout_audss always enabled
Date: Wed, 25 Jun 2014 08:39:37 +0530	[thread overview]
Message-ID: <53AA3D71.5010000@gmail.com> (raw)
In-Reply-To: <CAD=FV=VP4-+B6oV8Skb3rxxPRbOWmzu=6PJbWbxCU=86ZvRuYQ@mail.gmail.com>

On 06/25/2014 04:29 AM, Doug Anderson wrote:
> Tushar,
> 
> On Thu, Jun 12, 2014 at 12:40 AM, Tushar Behera <tushar.b@samsung.com> wrote:
>> On Wed, Jun 11, 2014 at 10:20 PM, Kevin Hilman <khilman@linaro.org> wrote:
>>> Tushar Behera <tushar.b@samsung.com> writes:
>>>
>>>> When the output clock of AUDSS mux is disabled, we are getting kernel
>>>> oops while doing a clk_get() on other clocks provided by AUDSS.
>>>>
>>>> Though user manual doesn't specify this dependency, we came across
>>>> this issue while disabling the parent of AUDSS mux clocks.
>>>>
>>>> Keeping the parents of AUDSS mux always enabled fixes this issue.
>>>
>>> While this patch works (and fixes the boot problem for me), it seems
>>> like it's papering over the real problem.
>>>
>>
>> Thanks for testing.
>>
>>> Seems like the right fix is actually modelling the clocks properly so
>>> that enabling a child clock ensures that the parent is also enabled.
>>>
>>
>> Patch 2/3 was to ensure we have proper clock tree defined for
>> Exynos5420. While testing with audio disabled, that patch alone fixed
>> the issue. But when audio was enabled (and hence I2S0 was trying to
>> access the clocks), we got some kernel oops during late booting, hence
>> I came up this solution.
>>
>> The solution might be a little half-baked because of the urgency to
>> push the fix, but will try to dig more into the issue on Monday when I
>> resume office.
> 
> Which Monday were you referring to?  ;)
> 

Sorry that I couldn't get deeper into this issue. Thanks for reminding
though.

> ...but in all seriousness do you have an official status update on
> this patch?  It seems as if it's not needed and all you need is
> <https://patchwork.kernel.org/patch/4333581/>, but it would be nice to
> get an official confirmation.

I have tested various scenarios with only patch 2/3, which seems to be
sufficient for the time being. I have not encountered the older issue
till now. I was thinking of testing a bit further, but given that you
have already asked for, we can go ahead with only patch 2/3 right now.

In case any further issue comes up, I will post patch 1/3 as per the
review comments that I have got.

> 
> Thanks!
> 
> -Doug
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Tushar Behera

  reply	other threads:[~2014-06-25  3:09 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  5:32 [PATCH 0/3] Fix boot-hang on Peach-pit and Enable audio Tushar Behera
2014-06-11  5:32 ` [PATCH 1/3] clk: exynos-audss: Keep the parent of mout_audss always enabled Tushar Behera
2014-06-11 15:58   ` Javier Martinez Canillas
2014-06-11 16:50   ` Mike Turquette
2014-06-12  7:29     ` Tushar Behera
2014-06-12 21:09       ` Mike Turquette
2014-07-11  6:18         ` Tushar Behera
2014-07-29  6:58           ` Mike Turquette
2014-06-11 16:50   ` Kevin Hilman
2014-06-12  7:40     ` Tushar Behera
2014-06-24 22:59       ` Doug Anderson
2014-06-25  3:09         ` Tushar Behera [this message]
2014-06-25  4:02           ` Doug Anderson
2014-06-11 17:28   ` Tomasz Figa
2014-06-12  7:30     ` Tushar Behera
2014-06-11  5:32 ` [PATCH 2/3] ARM: dts: Update the parent for Audss clocks in Exynos5420 Tushar Behera
2014-06-11 15:58   ` Javier Martinez Canillas
2014-06-16 11:26     ` Tushar Behera
2014-06-22 15:53       ` Tushar Behera
2014-06-24 23:00   ` Doug Anderson
2014-06-25 23:21     ` Kevin Hilman
2014-06-26  3:20       ` Tushar Behera
2014-06-26 16:08         ` Kevin Hilman
2014-06-27  3:38           ` Tushar Behera
2014-06-27 14:18             ` Kevin Hilman
2014-06-27 14:48               ` Kevin Hilman
2014-07-01 11:59                 ` Tushar Behera
2014-07-07 23:34                   ` Kukjin Kim
2014-07-08  3:00                     ` Tushar Behera
2014-07-09 10:14                       ` Javier Martinez Canillas
2014-07-09 12:11                         ` Tushar Behera
2014-07-09 13:03                           ` Javier Martinez Canillas
2014-07-09 16:01                             ` Doug Anderson
2014-07-09 17:46                               ` Javier Martinez Canillas
2014-07-09 17:52                                 ` Doug Anderson
2014-06-11  5:32 ` [PATCH 3/3] ARM: dts: Enable audio support for Peach-pi board Tushar Behera
2014-06-13 17:03   ` Doug Anderson
2014-06-13 17:05     ` Mark Brown
2014-06-13 17:13       ` Doug Anderson
2014-06-13 21:58         ` Doug Anderson
2014-06-13 22:04           ` Mark Brown
2014-06-13 22:50             ` Doug Anderson
2014-06-16 11:19     ` Tushar Behera
2014-06-16 16:49       ` Doug Anderson
2014-06-16 16:51         ` Mark Brown
2014-06-16 17:02           ` Doug Anderson
2014-06-17  3:39             ` Tushar Behera
2014-06-17  3:36         ` Tushar Behera
2014-06-17  4:07           ` Doug Anderson

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=53AA3D71.5010000@gmail.com \
    --to=trblinux@gmail.com \
    --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).