ext Pierre Ossman wrote:
Anderson Briglia wrote:
Actually they represent the bits regarding the modes and it is used
when we
have to send the LOCK/UNLOCK mode on the command data block, according
to the MMC Spec.
If you take a look at mmc_lock_unlock function, we use those modes to
set the right bit
when composing the command data block.
This definition makes the code more legible and simple.
In that case you need to change the code to make sure it is clear that
it is bits and not values.
Yes. As I sent another version after read your comment, I'll fix the V8 code just for this patch, ok? I don't see that
we have to send another version.
Also, your definition for
MMC_LOCK_MODE_UNLOCK is wrong.
This definition:
#define MMC_LOCK_MODE_UNLOCK (0<<2)
also tries to make the code more clear and legible. It is indicating that this bit is on the position 3 into the bits
array, according to MMC Spec.
But, why zero? Well, the bit must be 1 for locking and 0 for unlocking. We are using the unlocking action, so we used zero.
Is there any issue using this piece of code?
If you prefer another approach we can adjust our patch.
Regards,
Anderson Briglia
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
