[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7hiodg98z7.fsf@deeprootsystems.com>
Date: Tue, 31 Mar 2015 14:02:04 -0700
From: Kevin Hilman <khilman@...nel.org>
To: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
Cc: Tomasz Figa <tomasz.figa@...il.com>,
Stephen Boyd <sboyd@...eaurora.org>,
Mike Turquette <mturquette@...aro.org>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Kukjin Kim <kgene@...nel.org>, Olof Johansson <olof@...om.net>,
Doug Anderson <dianders@...omium.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Tyler Baker <tyler.baker@...aro.org>,
Abhilash Kesavan <kesavan.abhilash@...il.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
"linux-samsung-soc\@vger.kernel.org"
<linux-samsung-soc@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v3 2/2] clk: exynos5420: Make sure MDMA0 clock is enabled during suspend
Javier Martinez Canillas <javier.martinez@...labora.co.uk> writes:
[...]
> Unfortunately I don't fully understand why this clock needs to be
> enabled. It would be good if someone at Samsung can explain in more
> detail what the real problem really is.
+1
Maybe Abhilash can shed some light here?
We really should know *why* this is needed because having the fix in the
clock driver just doesn't seem right. It seems like the DMA driver
should be managing this clock.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists