From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Tushar Behera' <tushar.behera@linaro.org>,
'Alim Akhtar' <alim.akhtar@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org, jhbird.choi@samsung.com
Subject: RE: [PATCH] ARM: dts: Remove mau_pd node for Exynos5420
Date: Wed, 23 Apr 2014 19:13:32 +0900 [thread overview]
Message-ID: <03b001cf5edc$ae42e770$0ac8b650$@samsung.com> (raw)
In-Reply-To: <CAHbNUh2T8gOdGxDGm995vbj0oiJkyDwW9C9J7VV_o7mudfKjEw@mail.gmail.com>
Tushar Behera wrote:
>
> On 22 April 2014 13:08, Alim Akhtar <alim.akhtar@gmail.com> wrote:
> > Hi Tushar
> >
> > On Tue, Apr 22, 2014 at 11:09 AM, Tushar Behera
> > <tushar.behera@linaro.org> wrote:
> >> MAU powerdomain provides clocks for Audio sub-system block. This block
> >> comprises of the I2S audio controller, audio DMA blocks and Audio
> >> sub-system clock registers.
> >>
> >> Right now, there is no way to hook up power-domains with clock
> providers.
> >> During late boot when this power-domain gets disabled, we get following
> >> external abort.
+ Jonghwan Choi
Well, this is not a perfect solution to support MAU power domain, it's true it is a problem right now though.
In other words, this is just temporal fix for the problem.
How about accessing clock stuff for audio sub-system with handling MAU power domain via generic IO power domain?
> > ?? which abort?? Can you please mention it here?
> >>
>
> Thanks Alim for spotting this ... I somehow missed adding this.
>
> <<<<
> Unhandled fault: imprecise external abort (0x1406) at 0x00000000
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
> >>>>
>
> Kukjin,
>
> Let me know if I need to resend the patch.
- Kukjin
next prev parent reply other threads:[~2014-04-23 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 5:39 [PATCH] ARM: dts: Remove mau_pd node for Exynos5420 Tushar Behera
2014-04-22 7:38 ` Alim Akhtar
2014-04-22 8:21 ` Tushar Behera
2014-04-23 10:13 ` Kukjin Kim [this message]
2014-04-24 9:07 ` Tushar Behera
2014-04-24 10:06 ` Tomasz Figa
2014-04-24 11:03 ` Tushar Behera
2014-04-25 23:30 ` Tomasz Figa
2014-04-26 11:57 ` Vikas Sajjan
2014-04-26 15:18 ` Tomasz Figa
2014-04-26 15:42 ` Vikas Sajjan
2014-04-26 15:46 ` Tomasz Figa
2014-04-28 3:41 ` Tushar Behera
2014-05-13 4:11 ` Kukjin Kim
2014-04-22 16:34 ` 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='03b001cf5edc$ae42e770$0ac8b650$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=alim.akhtar@gmail.com \
--cc=jhbird.choi@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tushar.behera@linaro.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