Thread (26 messages) 26 messages, 6 authors, 2016-09-17

Re: [PATCH V5] clk: bcm: Add driver for BCM53573 ILP clock

From: Rob Herring <robh@kernel.org>
Date: 2016-08-31 16:17:05
Also in: linux-clk, lkml

On Thu, Aug 25, 2016 at 02:42:52PM +0200, Rafał Miłecki wrote:
On 23 August 2016 at 21:55, Rob Herring [off-list ref] wrote:
quoted
On Tue, Aug 23, 2016 at 08:25:59AM +0200, Rafał Miłecki wrote:
quoted
From: Rafał Miłecki <rafal@milecki.pl>

This clock is present on BCM53573 devices (including BCM47189) that use
Cortex-A7. ILP is a part of PMU (Power Management Unit) and so it should
be defined as one of its subnodes (subdevices). For more details see
Documentation entry.

Unfortunately there isn't a set of registers related to ILP clock only.
We use registers 0x66c, 0x674 and 0x6dc and between them there are e.g.
"retention*" and "control_ext" regs. This is why this driver maps all
0x1000 B of space.
Then describe the block as a syscon which has several functions of
which clocks are one.
This isn't clear to me, sorry, could you describe it? Would you like
me to update commit message or documentation? Is code fine as is?
Let me put it another way, when you need to use the other registers, how 
do you plan to describe them in DT? We don't really want a node per 
register, nor do I want to get binding docs one by one as you add each 
function. Instead describe the block with all the misc functions as a 
whole. What would you call that block? Still ILP or something else? 

Also, you if you do have multiple drivers all needing to access this 
single block, then that is when you need syscon and regmap.

Rob
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help