Thread (152 messages) 152 messages, 12 authors, 2013-06-18

[PATCH 01/11] pinctrl: mvebu: pinctrl driver core

From: Linus Walleij <hidden>
Date: 2012-08-20 14:18:18
Also in: linux-devicetree, lkml

On Mon, Aug 20, 2012 at 11:46 AM, Sebastian Hesselbarth
[off-list ref] wrote:
On 8/20/12, Linus Walleij [off-list ref] wrote:
quoted
Are you taking this patch series through some Marvell tree or do you want
me to carry it in the pinctrl tree?
I think it would be better to take it through the Marvell tree of Jason
Cooper. It is only for Marvell SoCs anyway.
OK.
quoted
There is some other "variant" field elsewhere that is
a u8, is this correct? In this and the other case, should
this "variant" rather be an enum?
I'll review the variant types but inside pinctrl-mvebu variant
is used as a bit mask to distinguish different variants. Anyway,
they should always be the same size.
Aha bitmask, seems you can only have 8 different variants of
the Marvell's then?
quoted
Is it possible to use devm_* managed devm_kzalloc() for this map
so you don't need to free it explicitly?

(Maybe not, just checking.)
Hmm, I guess not as I thought I've read not to use devm_kfree when
you allocate _and_ free stuff on runtime without removing the device
itself, right?
You're right.
quoted
So, there will never be > 256 pins on a Marvell platform?
Well, with all current platforms we are well below 100. I guess
256 max (muxable) pins will be enough.
OK.
quoted
quoted
+ * struct mvebu_mpp_ctrl_setting - describe a mpp ctrl setting
+ * @val: ctrl setting value
It is not obvious to me what this means, it it possible to elaborate
on how this member is defined and used?
Well, I see if I can clarify the description but wrt the datasheet it
_should_ be quite obvious.
I mainly worry about being able to read the code and figure out
what's going on, if the datasheet is vital then pls include some
link to it or so in the header of the file (but preferrably the code
should speak for itself).
quoted
quoted
+ * @variant: (optional) variant identifier mask
This thing again, there are lots of "variants" around here.
Is it a candidate for an enum?
As it is a mask, I don't think enum fits here.
OK. No big deal anyway.
In some internal review with Andrew I also added a spinlock to
mvebu_pinconf_get/_set that will protect all calls to generic and specific
_get/_set register accesses. Moreover, I replaced clk_get_sys in pinctrl-dove
with the devm_ counterpart and removed the explicit clk_put.
I had some separate comments on that clk thing...
Anyway, looking forward to v2, this is progressing quickly
I think.

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