[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C79B248886DD134989C8FF6B096A91AB91CF1615C6@BGMAIL01.nvidia.com>
Date: Wed, 12 Jun 2013 12:41:38 +0530
From: Jay Agarwal <jagarwal@...dia.com>
To: 'Mike Turquette' <mturquette@...aro.org>,
Stephen Warren <swarren@...dotorg.org>
CC: "linux@....linux.org.uk" <linux@....linux.org.uk>,
"thierry.reding@...onic-design.de" <thierry.reding@...onic-design.de>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
Laxman Dewangan <ldewangan@...dia.com>,
"olof@...om.net" <olof@...om.net>, Hiroshi Doyu <hdoyu@...dia.com>,
Prashant Gaikwad <pgaikwad@...dia.com>,
Peter De Schrijver <pdeschrijver@...dia.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Juha Tukkinen <jtukkinen@...dia.com>,
Krishna Thota <kthota@...dia.com>
Subject: RE: [PATCH V3 1/4] ARM: tegra30: clocks: Fix pciex clock
registration
> Quoting Stephen Warren (2013-06-04 12:08:08)
> > On 06/04/2013 12:57 PM, Jay Agarwal wrote:
> > > Registering pciex as peripheral clock instead of fixed clock as
> > > tegra_perih_reset_assert(deassert) api of this clock api gives
> > > warning and ultimately does not succeed to assert(deassert).
> > >
> > > Signed-off-by: Jay Agarwal <jagarwal@...dia.com>
> > > ---
> > > Patch is based on remotes/gitorious_thierryreding_linux/tegra/next and
> should be applied on top of this.
> >
> > For this change, Mike may as well apply it directly to the clock tree.
> > Thierry can then pick it up when he rebases his tegra/next tree.
> >
> > That said, I don't think you should need any of the
> > TEGRA_CLK_DUPLICATE() entries; the PCIe driver should get its clocks
> > from device tree now, and hence the driver name in the clock
> > registration shouldn't be necessary. All of these
> > TEGRA_CLK_DUPLICATE() entries should be removed en mass sometime
> soon
> > with luck. So, can you simply leave the two TEGRA_CLK_DUPLICATE()
> > entries untouched, rather than changing them?
>
> Ping on this patch. I can take it through my tree, but is there going to be
> rework based on Stephen's comments?
Hi Mike,
I have uploaded next version V4 of this patch after taking care of this comment.
Powered by blists - more mailing lists