Re: [PATCH] MUSB: fix DM644xEVM DRVVBUS GPIO number

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello, I wrote:

Commit 30899ca7f20571c4bd64544dec261171f6ec255b (USB: musb: davinci dm6446evm GPIO renumbering) has updated GPIO_nVBUS_DRV to a wrong value which causes a
kernel oops.

The DaVinci chips have 104 GPIOs max, not 128, hence the correct value is 120
(that is 104 + 8 + 8), not 144.

Signed-off-by: Sergei Shtylyov <sshtylyov@xxxxxxxxxxxxx>

---
Please, apply it before 2.6.31 is out as it fixes a kernel oops...

   Ping.

David, Greg is waiting for your ACKs (or NAKs) on my several outstanding MUSB patches... we've already missed 2.6.31. :-/

   David, PING again...
Greg, can the patch that hasn't been merged to Linus' tree (this one hasn't been merged in its due time) be merged into -stable. If not, then this patch can now be dropped from the cosideration and superseded by Saminathan's patch -- this patch is only valid in the context of 2.6.31. Or perhaps Swaminathan's patch could be applied to -stable in the form different from 2.6.32, i.e. with 120, not 160 for the GPIO #...

WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux