[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51B8956B.8020704@wwwdotorg.org>
Date: Wed, 12 Jun 2013 09:36:11 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: Jay Agarwal <jagarwal@...dia.com>, mturquette@...aro.org
CC: linux@....linux.org.uk, thierry.reding@...onic-design.de,
bhelgaas@...gle.com, ldewangan@...dia.com, olof@...om.net,
hdoyu@...dia.com, pgaikwad@...dia.com, pdeschrijver@...dia.com,
linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
jtukkinen@...dia.com, kthota@...dia.com
Subject: Re: [PATCH V4 1/4] ARM: tegra30: clocks: Fix pciex clock registration
On 06/12/2013 01:13 AM, 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.
In this case, it would make more sense to apply this to the clock tree,
since it's a standalone bug-fix.
Acked-by: Stephen Warren <swarren@...dia.com>
--
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