On Thu, Apr 09, 2015 at 10:54:26PM +0300, Dan Carpenter wrote:
> On Thu, Apr 09, 2015 at 09:25:57PM +0200, Simon Guinot wrote:
> > On Thu, Apr 09, 2015 at 12:07:12PM +0300, Dan Carpenter wrote:
> > > This driver is pretty hardware specific so it's unlikely that we're
> > > going to be using it on 64 big endian systems. Still, the current code
> > > causes a static checker warning so we may as well change the type from
> > > "unsigned long" to "u32" and remove the casting.
> >
> > Hi Dan,
> >
> > Thanks for the patch.
> >
> > Why do you think it would be an issue to use the u32 type for this
> > variables on a 64-bit big-endian machine ? Note that this LED mechanism
> > is actually used on ARM 32-bits and x86-64 NAS platforms. The latter are
> > not mainlined yet. But indeed, for now, there is no plan to use it on a
> > 64-bit big-endian machine.
> >
> > Since the whole LED code uses the unsigned long type to hold the delay
> > values, if possible, I would prefer to keep the delay_{on,off} variables
> > consistent with that.
> >
> > Is there an another way to make the "static checker" happy ?
>
> We're writing over 32 bits of a long. It's a dangerous habbit.
>
> If long is u32 then of_property_read_u32_index() works, obviously. If
> it is a little endian and the last 32 bits have been zeroed out (as they
> have been here) then that also works.
>
> If it's big endian and 64 bit then it doesn't work because we're writing
> to the wrong 32 bits.
Sorry, I misunderstood your commit message.
But still, rather than changing the type from unsigned long to u32 for
the delay_{on,off} variables, I think we should use a temporary u32
variable for the of_property_read_u32_index calls. This way we can keep
the type of the delay_{on,off} variables consistent with the LED core
code.
Regards,
Simon
Attachment:
signature.asc
Description: Digital signature
