Re: [PATCH] clk: Fix debugfs_create_*() usage

[Stephen Boyd]

On 01/02, Geert Uytterhoeven wrote:
> On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd  wrote:
> > On 01/02, Geert Uytterhoeven wrote:

> >> --- a/drivers/clk/clk.c
> >> +++ b/drivers/clk/clk.c
> >> @@ -58,7 +58,7 @@ struct clk_core {
> >>   unsigned long   new_rate;
> >>   struct clk_core *new_parent;
> >>   struct clk_core *new_child;
> >> - unsigned long   flags;
> >> + unsigned intflags;
> >
> > This doesn't look good.
> 
> Why not?
> It's not like flags is used with bitops, which would  mandate unsigned long.
> And you can't start using bits 32-63 without changing flags to u64, else
> the extra bits are not available on 32-bit platforms.

Fair enough. We don't need to change it if we print better
information in debugfs though. That's all I'm saying.

> 
> >> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
> >> *core, struct dentry *pdentry)
> >>
> >>   core->dentry = d;
> >>
> >> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
> >> - (u32 *)>rate);
> >> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
> >> +  >rate);
> >
> > As you're changing these lines, can you also change S_IRUGO to
> > the octal values. That's the preferred style now.
> 
> Yes, I can. That would be a separate patch, though.

Uhhh ok. I will fold them together if you don't :)

> 
> >>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
> >> - (u32 *)>flags);
> >> +>flags);
> >
> > Maybe we need a new debugfs API like debugfs_create_ulong_hex()
> > or something that prints out an unsigned long as a hex value?
> 
> That's possible.  I already have that locally (for another user which uses
> u32 or u64 depending on platform).
> My main worry was the change from 0x to 0x
> on 64-bit platforms, which you don't seem to see as a blocker, as
> debugfs isn't ABI?

That's right. Debugfs isn't an ABI.

> 
> > clk_flags file would have something like
> >
> > CLK_SET_RATE_PARENT
> > CLK_SET_RATE_GATE
> >
> > if those flags are set.
> 
> But some flags are internal to platform-specific drivers, right?

Nope. Platform specific drivers shouldn't be passing internal
flags in this field. It's for the clk core to use. Perhaps we
should enforce that by failing non-core flags on registration.
I've been catching this in review so far.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH] clk: Fix debugfs_create_*() usage

[Stephen Boyd]

On 01/02, Geert Uytterhoeven wrote:
> On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd  wrote:
> > On 01/02, Geert Uytterhoeven wrote:

> >> --- a/drivers/clk/clk.c
> >> +++ b/drivers/clk/clk.c
> >> @@ -58,7 +58,7 @@ struct clk_core {
> >>   unsigned long   new_rate;
> >>   struct clk_core *new_parent;
> >>   struct clk_core *new_child;
> >> - unsigned long   flags;
> >> + unsigned intflags;
> >
> > This doesn't look good.
> 
> Why not?
> It's not like flags is used with bitops, which would  mandate unsigned long.
> And you can't start using bits 32-63 without changing flags to u64, else
> the extra bits are not available on 32-bit platforms.

Fair enough. We don't need to change it if we print better
information in debugfs though. That's all I'm saying.

> 
> >> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
> >> *core, struct dentry *pdentry)
> >>
> >>   core->dentry = d;
> >>
> >> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
> >> - (u32 *)>rate);
> >> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
> >> +  >rate);
> >
> > As you're changing these lines, can you also change S_IRUGO to
> > the octal values. That's the preferred style now.
> 
> Yes, I can. That would be a separate patch, though.

Uhhh ok. I will fold them together if you don't :)

> 
> >>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
> >> - (u32 *)>flags);
> >> +>flags);
> >
> > Maybe we need a new debugfs API like debugfs_create_ulong_hex()
> > or something that prints out an unsigned long as a hex value?
> 
> That's possible.  I already have that locally (for another user which uses
> u32 or u64 depending on platform).
> My main worry was the change from 0x to 0x
> on 64-bit platforms, which you don't seem to see as a blocker, as
> debugfs isn't ABI?

That's right. Debugfs isn't an ABI.

> 
> > clk_flags file would have something like
> >
> > CLK_SET_RATE_PARENT
> > CLK_SET_RATE_GATE
> >
> > if those flags are set.
> 
> But some flags are internal to platform-specific drivers, right?

Nope. Platform specific drivers shouldn't be passing internal
flags in this field. It's for the clk core to use. Perhaps we
should enforce that by failing non-core flags on registration.
I've been catching this in review so far.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH] clk: Fix debugfs_create_*() usage

[Geert Uytterhoeven]

Hi Stephen,

On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd  wrote:
> On 01/02, Geert Uytterhoeven wrote:
>> When exposing data access through debugfs, the correct
>> debugfs_create_*() functions must be used, depending on data type.
>>
>> Remove all casts from data pointers passed to debugfs_create_*()
>> functions, as such casts prevent the compiler from flagging bugs.
>>
>> clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
>> to "u32 *" exposed the wrong halves on big-endian 64-bit systems.
>>
>> Fix .rate and .accuracy, by using debugfs_create_ulong() instead.
>>
>> Fix .flags by changing the field to "unsigned int", as a change to
>> debugfs_create_x64() on 64-bit systems would change the user-visible
>> formatting in debugfs.
>> Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
>> and still return "unsigned long", to avoid having to change all their
>> users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
>> but the comment is updated as it is never passed a real pointer to
>> clk_core.flags.
>>
>> Signed-off-by: Geert Uytterhoeven 
>> ---
>> Looks like none of the 64-bit architectures support common clock yet?
>
> arm64 does.

Sorry, I meant "64-bit big endian".

>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -58,7 +58,7 @@ struct clk_core {
>>   unsigned long   new_rate;
>>   struct clk_core *new_parent;
>>   struct clk_core *new_child;
>> - unsigned long   flags;
>> + unsigned intflags;
>
> This doesn't look good.

Why not?
It's not like flags is used with bitops, which would  mandate unsigned long.
And you can't start using bits 32-63 without changing flags to u64, else
the extra bits are not available on 32-bit platforms.

>> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
>> *core, struct dentry *pdentry)
>>
>>   core->dentry = d;
>>
>> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
>> - (u32 *)>rate);
>> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
>> +  >rate);
>
> As you're changing these lines, can you also change S_IRUGO to
> the octal values. That's the preferred style now.

Yes, I can. That would be a separate patch, though.

>>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
>> - (u32 *)>flags);
>> +>flags);
>
> Maybe we need a new debugfs API like debugfs_create_ulong_hex()
> or something that prints out an unsigned long as a hex value?

That's possible.  I already have that locally (for another user which uses
u32 or u64 depending on platform).
My main worry was the change from 0x to 0x
on 64-bit platforms, which you don't seem to see as a blocker, as
debugfs isn't ABI?

> Probably we should change it to pretty print the values and what
> they correspond to, with words, because that's the least
> confusing thing to do with regards to endianness. So the

Endianness doesn't matter when printing u32. The hex values of
the flags are the same on big and little endian.

> clk_flags file would have something like
>
> CLK_SET_RATE_PARENT
> CLK_SET_RATE_GATE
>
> if those flags are set.

But some flags are internal to platform-specific drivers, right?

> We don't care about ABI here either. This is debugfs.

OK.

>> @@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
>>   * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
>>   * @np: Device node pointer associated with clock provider
>>   * @index: clock index
>> - * @flags: pointer to clk_core->flags
>> + * @flags: pointer to core clock flags
>
> Please split this off into another patch.

OK.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

Re: [PATCH] clk: Fix debugfs_create_*() usage

[Geert Uytterhoeven]

Hi Stephen,

On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd  wrote:
> On 01/02, Geert Uytterhoeven wrote:
>> When exposing data access through debugfs, the correct
>> debugfs_create_*() functions must be used, depending on data type.
>>
>> Remove all casts from data pointers passed to debugfs_create_*()
>> functions, as such casts prevent the compiler from flagging bugs.
>>
>> clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
>> to "u32 *" exposed the wrong halves on big-endian 64-bit systems.
>>
>> Fix .rate and .accuracy, by using debugfs_create_ulong() instead.
>>
>> Fix .flags by changing the field to "unsigned int", as a change to
>> debugfs_create_x64() on 64-bit systems would change the user-visible
>> formatting in debugfs.
>> Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
>> and still return "unsigned long", to avoid having to change all their
>> users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
>> but the comment is updated as it is never passed a real pointer to
>> clk_core.flags.
>>
>> Signed-off-by: Geert Uytterhoeven 
>> ---
>> Looks like none of the 64-bit architectures support common clock yet?
>
> arm64 does.

Sorry, I meant "64-bit big endian".

>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -58,7 +58,7 @@ struct clk_core {
>>   unsigned long   new_rate;
>>   struct clk_core *new_parent;
>>   struct clk_core *new_child;
>> - unsigned long   flags;
>> + unsigned intflags;
>
> This doesn't look good.

Why not?
It's not like flags is used with bitops, which would  mandate unsigned long.
And you can't start using bits 32-63 without changing flags to u64, else
the extra bits are not available on 32-bit platforms.

>> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
>> *core, struct dentry *pdentry)
>>
>>   core->dentry = d;
>>
>> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
>> - (u32 *)>rate);
>> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
>> +  >rate);
>
> As you're changing these lines, can you also change S_IRUGO to
> the octal values. That's the preferred style now.

Yes, I can. That would be a separate patch, though.

>>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
>> - (u32 *)>flags);
>> +>flags);
>
> Maybe we need a new debugfs API like debugfs_create_ulong_hex()
> or something that prints out an unsigned long as a hex value?

That's possible.  I already have that locally (for another user which uses
u32 or u64 depending on platform).
My main worry was the change from 0x to 0x
on 64-bit platforms, which you don't seem to see as a blocker, as
debugfs isn't ABI?

> Probably we should change it to pretty print the values and what
> they correspond to, with words, because that's the least
> confusing thing to do with regards to endianness. So the

Endianness doesn't matter when printing u32. The hex values of
the flags are the same on big and little endian.

> clk_flags file would have something like
>
> CLK_SET_RATE_PARENT
> CLK_SET_RATE_GATE
>
> if those flags are set.

But some flags are internal to platform-specific drivers, right?

> We don't care about ABI here either. This is debugfs.

OK.

>> @@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
>>   * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
>>   * @np: Device node pointer associated with clock provider
>>   * @index: clock index
>> - * @flags: pointer to clk_core->flags
>> + * @flags: pointer to core clock flags
>
> Please split this off into another patch.

OK.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

Re: [PATCH] clk: Fix debugfs_create_*() usage

[Stephen Boyd]

On 01/02, Geert Uytterhoeven wrote:
> When exposing data access through debugfs, the correct
> debugfs_create_*() functions must be used, depending on data type.
> 
> Remove all casts from data pointers passed to debugfs_create_*()
> functions, as such casts prevent the compiler from flagging bugs.
> 
> clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
> to "u32 *" exposed the wrong halves on big-endian 64-bit systems.
> 
> Fix .rate and .accuracy, by using debugfs_create_ulong() instead.
> 
> Fix .flags by changing the field to "unsigned int", as a change to
> debugfs_create_x64() on 64-bit systems would change the user-visible
> formatting in debugfs.
> Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
> and still return "unsigned long", to avoid having to change all their
> users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
> but the comment is updated as it is never passed a real pointer to
> clk_core.flags.
> 
> Signed-off-by: Geert Uytterhoeven 
> ---
> Looks like none of the 64-bit architectures support common clock yet?

arm64 does.

> ---
>  drivers/clk/clk.c | 24 
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 5ec580914089510a..b23e0249f0e3c634 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -58,7 +58,7 @@ struct clk_core {
>   unsigned long   new_rate;
>   struct clk_core *new_parent;
>   struct clk_core *new_child;
> - unsigned long   flags;
> + unsigned intflags;

This doesn't look good.

>   boolorphan;
>   unsigned intenable_count;
>   unsigned intprepare_count;
> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
> *core, struct dentry *pdentry)
>  
>   core->dentry = d;
>  
> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
> - (u32 *)>rate);
> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
> +  >rate);

As you're changing these lines, can you also change S_IRUGO to
the octal values. That's the preferred style now.

>   if (!d)
>   goto err_out;
>  
> - d = debugfs_create_u32("clk_accuracy", S_IRUGO, core->dentry,
> - (u32 *)>accuracy);
> + d = debugfs_create_ulong("clk_accuracy", S_IRUGO, core->dentry,
> +  >accuracy);
>   if (!d)
>   goto err_out;
>  
>   d = debugfs_create_u32("clk_phase", S_IRUGO, core->dentry,
> - (u32 *)>phase);
> +>phase);
>   if (!d)
>   goto err_out;
>  
>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
> - (u32 *)>flags);
> +>flags);

Maybe we need a new debugfs API like debugfs_create_ulong_hex()
or something that prints out an unsigned long as a hex value?
Probably we should change it to pretty print the values and what
they correspond to, with words, because that's the least
confusing thing to do with regards to endianness. So the
clk_flags file would have something like

CLK_SET_RATE_PARENT
CLK_SET_RATE_GATE

if those flags are set.

We don't care about ABI here either. This is debugfs.

> @@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
>   * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
>   * @np: Device node pointer associated with clock provider
>   * @index: clock index
> - * @flags: pointer to clk_core->flags
> + * @flags: pointer to core clock flags

Please split this off into another patch.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

Re: [PATCH] clk: Fix debugfs_create_*() usage

[Stephen Boyd]

On 01/02, Geert Uytterhoeven wrote:
> When exposing data access through debugfs, the correct
> debugfs_create_*() functions must be used, depending on data type.
> 
> Remove all casts from data pointers passed to debugfs_create_*()
> functions, as such casts prevent the compiler from flagging bugs.
> 
> clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
> to "u32 *" exposed the wrong halves on big-endian 64-bit systems.
> 
> Fix .rate and .accuracy, by using debugfs_create_ulong() instead.
> 
> Fix .flags by changing the field to "unsigned int", as a change to
> debugfs_create_x64() on 64-bit systems would change the user-visible
> formatting in debugfs.
> Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
> and still return "unsigned long", to avoid having to change all their
> users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
> but the comment is updated as it is never passed a real pointer to
> clk_core.flags.
> 
> Signed-off-by: Geert Uytterhoeven 
> ---
> Looks like none of the 64-bit architectures support common clock yet?

arm64 does.

> ---
>  drivers/clk/clk.c | 24 
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
> index 5ec580914089510a..b23e0249f0e3c634 100644
> --- a/drivers/clk/clk.c
> +++ b/drivers/clk/clk.c
> @@ -58,7 +58,7 @@ struct clk_core {
>   unsigned long   new_rate;
>   struct clk_core *new_parent;
>   struct clk_core *new_child;
> - unsigned long   flags;
> + unsigned intflags;

This doesn't look good.

>   boolorphan;
>   unsigned intenable_count;
>   unsigned intprepare_count;
> @@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core 
> *core, struct dentry *pdentry)
>  
>   core->dentry = d;
>  
> - d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
> - (u32 *)>rate);
> + d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
> +  >rate);

As you're changing these lines, can you also change S_IRUGO to
the octal values. That's the preferred style now.

>   if (!d)
>   goto err_out;
>  
> - d = debugfs_create_u32("clk_accuracy", S_IRUGO, core->dentry,
> - (u32 *)>accuracy);
> + d = debugfs_create_ulong("clk_accuracy", S_IRUGO, core->dentry,
> +  >accuracy);
>   if (!d)
>   goto err_out;
>  
>   d = debugfs_create_u32("clk_phase", S_IRUGO, core->dentry,
> - (u32 *)>phase);
> +>phase);
>   if (!d)
>   goto err_out;
>  
>   d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
> - (u32 *)>flags);
> +>flags);

Maybe we need a new debugfs API like debugfs_create_ulong_hex()
or something that prints out an unsigned long as a hex value?
Probably we should change it to pretty print the values and what
they correspond to, with words, because that's the least
confusing thing to do with regards to endianness. So the
clk_flags file would have something like

CLK_SET_RATE_PARENT
CLK_SET_RATE_GATE

if those flags are set.

We don't care about ABI here either. This is debugfs.

> @@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
>   * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
>   * @np: Device node pointer associated with clock provider
>   * @index: clock index
> - * @flags: pointer to clk_core->flags
> + * @flags: pointer to core clock flags

Please split this off into another patch.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

[PATCH] clk: Fix debugfs_create_*() usage

[Geert Uytterhoeven]

When exposing data access through debugfs, the correct
debugfs_create_*() functions must be used, depending on data type.

Remove all casts from data pointers passed to debugfs_create_*()
functions, as such casts prevent the compiler from flagging bugs.

clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
to "u32 *" exposed the wrong halves on big-endian 64-bit systems.

Fix .rate and .accuracy, by using debugfs_create_ulong() instead.

Fix .flags by changing the field to "unsigned int", as a change to
debugfs_create_x64() on 64-bit systems would change the user-visible
formatting in debugfs.
Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
and still return "unsigned long", to avoid having to change all their
users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
but the comment is updated as it is never passed a real pointer to
clk_core.flags.

Signed-off-by: Geert Uytterhoeven 
---
Looks like none of the 64-bit architectures support common clock yet?
---
 drivers/clk/clk.c | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 5ec580914089510a..b23e0249f0e3c634 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -58,7 +58,7 @@ struct clk_core {
unsigned long   new_rate;
struct clk_core *new_parent;
struct clk_core *new_child;
-   unsigned long   flags;
+   unsigned intflags;
boolorphan;
unsigned intenable_count;
unsigned intprepare_count;
@@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core *core, 
struct dentry *pdentry)
 
core->dentry = d;
 
-   d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
-   (u32 *)>rate);
+   d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
+>rate);
if (!d)
goto err_out;
 
-   d = debugfs_create_u32("clk_accuracy", S_IRUGO, core->dentry,
-   (u32 *)>accuracy);
+   d = debugfs_create_ulong("clk_accuracy", S_IRUGO, core->dentry,
+>accuracy);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_phase", S_IRUGO, core->dentry,
-   (u32 *)>phase);
+  >phase);
if (!d)
goto err_out;
 
d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
-   (u32 *)>flags);
+  >flags);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_prepare_count", S_IRUGO, core->dentry,
-   (u32 *)>prepare_count);
+  >prepare_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_enable_count", S_IRUGO, core->dentry,
-   (u32 *)>enable_count);
+  >enable_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_protect_count", S_IRUGO, core->dentry,
-   (u32 *)>protect_count);
+  >protect_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_notifier_count", S_IRUGO, core->dentry,
-   (u32 *)>notifier_count);
+  >notifier_count);
if (!d)
goto err_out;
 
@@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
  * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
  * @np: Device node pointer associated with clock provider
  * @index: clock index
- * @flags: pointer to clk_core->flags
+ * @flags: pointer to core clock flags
  *
  * Detects if the clock-critical property exists and, if so, sets the
  * corresponding CLK_IS_CRITICAL flag.
-- 
2.7.4

[PATCH] clk: Fix debugfs_create_*() usage

[Geert Uytterhoeven]

When exposing data access through debugfs, the correct
debugfs_create_*() functions must be used, depending on data type.

Remove all casts from data pointers passed to debugfs_create_*()
functions, as such casts prevent the compiler from flagging bugs.

clk_core.rate, .accuracy, and .flags are "unsigned long", hence casting
to "u32 *" exposed the wrong halves on big-endian 64-bit systems.

Fix .rate and .accuracy, by using debugfs_create_ulong() instead.

Fix .flags by changing the field to "unsigned int", as a change to
debugfs_create_x64() on 64-bit systems would change the user-visible
formatting in debugfs.
Note that __clk_get_flags() and clk_hw_get_flags() are left unchanged
and still return "unsigned long", to avoid having to change all their
users.  Likewise, of_clk_detect_critical() still takes "unsigned long",
but the comment is updated as it is never passed a real pointer to
clk_core.flags.

Signed-off-by: Geert Uytterhoeven 
---
Looks like none of the 64-bit architectures support common clock yet?
---
 drivers/clk/clk.c | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 5ec580914089510a..b23e0249f0e3c634 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -58,7 +58,7 @@ struct clk_core {
unsigned long   new_rate;
struct clk_core *new_parent;
struct clk_core *new_child;
-   unsigned long   flags;
+   unsigned intflags;
boolorphan;
unsigned intenable_count;
unsigned intprepare_count;
@@ -2600,43 +2600,43 @@ static int clk_debug_create_one(struct clk_core *core, 
struct dentry *pdentry)
 
core->dentry = d;
 
-   d = debugfs_create_u32("clk_rate", S_IRUGO, core->dentry,
-   (u32 *)>rate);
+   d = debugfs_create_ulong("clk_rate", S_IRUGO, core->dentry,
+>rate);
if (!d)
goto err_out;
 
-   d = debugfs_create_u32("clk_accuracy", S_IRUGO, core->dentry,
-   (u32 *)>accuracy);
+   d = debugfs_create_ulong("clk_accuracy", S_IRUGO, core->dentry,
+>accuracy);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_phase", S_IRUGO, core->dentry,
-   (u32 *)>phase);
+  >phase);
if (!d)
goto err_out;
 
d = debugfs_create_x32("clk_flags", S_IRUGO, core->dentry,
-   (u32 *)>flags);
+  >flags);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_prepare_count", S_IRUGO, core->dentry,
-   (u32 *)>prepare_count);
+  >prepare_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_enable_count", S_IRUGO, core->dentry,
-   (u32 *)>enable_count);
+  >enable_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_protect_count", S_IRUGO, core->dentry,
-   (u32 *)>protect_count);
+  >protect_count);
if (!d)
goto err_out;
 
d = debugfs_create_u32("clk_notifier_count", S_IRUGO, core->dentry,
-   (u32 *)>notifier_count);
+  >notifier_count);
if (!d)
goto err_out;
 
@@ -3927,7 +3927,7 @@ static int parent_ready(struct device_node *np)
  * of_clk_detect_critical() - set CLK_IS_CRITICAL flag from Device Tree
  * @np: Device node pointer associated with clock provider
  * @index: clock index
- * @flags: pointer to clk_core->flags
+ * @flags: pointer to core clock flags
  *
  * Detects if the clock-critical property exists and, if so, sets the
  * corresponding CLK_IS_CRITICAL flag.
-- 
2.7.4