[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1306110944130.22645@utopia.booyaka.com>
Date: Tue, 11 Jun 2013 09:47:13 +0000 (UTC)
From: Paul Walmsley <pwalmsley@...dia.com>
To: Prashant Gaikwad <pgaikwad@...dia.com>
cc: Stephen Warren <swarren@...dotorg.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"mturquette@...aro.org" <mturquette@...aro.org>,
Peter De Schrijver <pdeschrijver@...dia.com>,
Aleksandr Frid <afrid@...dia.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 3/3] clk: tegra: T114: add DFLL DVCO reset control
On Tue, 11 Jun 2013, Prashant Gaikwad wrote:
> Why not implement these APIs in DFLL clock driver itself and pass RST address
> register to driver?
The DFLL DVCO reset registers are CAR registers, not DFLL registers.
Functions that operate on registers in one IP block shouldn't be located
in another IP block's driver.
- Paul
--
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