[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150609095628.GP2982@x1>
Date:	Tue, 9 Jun 2015 10:56:28 +0100
From:	Lee Jones <lee@...nel.org>
To:	Eric Anholt <eric@...olt.net>
Cc:	linux-arm-kernel@...ts.infradead.org,
	linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Stephen Warren <swarren@...dotorg.org>,
	linux-clk@...r.kernel.org, Stephen Boyd <sboyd@...eaurora.org>,
	Mike Turquette <mturquette@...aro.org>
Subject: Re: [PATCH v3 2/7] ARM: bcm2835: Add a Raspberry Pi-specific clock
 driver.
On Mon, 08 Jun 2015, Eric Anholt wrote:
> Unfortunately, the clock manager's registers are not accessible by the
> ARM, so we have to request that the firmware modify our clocks for us.
> 
> This driver only registers the clocks at the point they are requested
> by a client driver.  This is partially to support returning
> -EPROBE_DEFER when the firmware driver isn't supported yet, but it
> also avoids issues with disabling "unused" clocks due to them not yet
> being connected to their consumers in the DT.
> 
> v2: Declare the mutex static (from review by Baruch Siach), merge
>     description and copyright comments.
> 
> v3: Update for new rpi firmware API.  Update the compatible string.
>     Make the firmware handle be under a vendor-namespaced property.
>     Make the DT indices match the firmware clock IDs.  Move the driver
>     under the firmware driver's Kconfig, since it requires it.  Move a
>     container_of() from 2 callers into the callee.
> 
> Signed-off-by: Eric Anholt <eric@...olt.net>
> ---
>  drivers/clk/Makefile          |   1 +
>  drivers/clk/clk-raspberrypi.c | 242 ++++++++++++++++++++++++++++++++++++++++++
This is not an "ARM" patch.
The subject line needs to reflect the subsystem you are submitting to.
`git log --oneline -- <subsystem>`
--
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