SAM3/4 Interrupt initialization. Default interrupt priority not being set correctly
This commit is contained in:
parent
b83702dd8a
commit
9485fbf66e
@ -7198,3 +7198,6 @@
|
|||||||
compilation. From Leo (2014-4-17).
|
compilation. From Leo (2014-4-17).
|
||||||
* drivers/usbhost/usbhost_hidmouse.c: Don't include NAKs from the device
|
* drivers/usbhost/usbhost_hidmouse.c: Don't include NAKs from the device
|
||||||
in the error count. From Leo (2014-4-17).
|
in the error count. From Leo (2014-4-17).
|
||||||
|
* arch/arm/src/sam34/sam_irq.c: Fix initialization of the default
|
||||||
|
priorities (2014-4-17).
|
||||||
|
|
||||||
|
@ -372,7 +372,7 @@ void up_irqinitialize(void)
|
|||||||
i > 0;
|
i > 0;
|
||||||
i--, regaddr += 4)
|
i--, regaddr += 4)
|
||||||
{
|
{
|
||||||
putreg32(0, regaddr);
|
putreg32(DEFPRIORITY32, regaddr);
|
||||||
}
|
}
|
||||||
|
|
||||||
/* currents_regs is non-NULL only while processing an interrupt */
|
/* currents_regs is non-NULL only while processing an interrupt */
|
||||||
|
@ -1085,16 +1085,14 @@ static int usbhost_mouse_poll(int argc, char *argv[])
|
|||||||
{
|
{
|
||||||
/* If DRVR_TRANSFER() returns EAGAIN, that simply means that
|
/* If DRVR_TRANSFER() returns EAGAIN, that simply means that
|
||||||
* the devices was not ready and has NAK'ed the transfer. That
|
* the devices was not ready and has NAK'ed the transfer. That
|
||||||
* no be treated as an error (unless it persists for a long
|
* should not be treated as an error (unless it persists for a
|
||||||
* time).
|
* long time).
|
||||||
*/
|
*/
|
||||||
|
|
||||||
udbg("ERROR: DRVR_TRANSFER returned: %d/%d\n", ret, nerrors);
|
udbg("ERROR: DRVR_TRANSFER returned: %d/%d\n", ret, nerrors);
|
||||||
if (ret != -EAGAIN)
|
if (ret != -EAGAIN)
|
||||||
{
|
{
|
||||||
nerrors++;
|
if (++nerrors > 200)
|
||||||
|
|
||||||
if (nerrors > 200)
|
|
||||||
{
|
{
|
||||||
udbg("Too many errors... aborting: %d\n", nerrors);
|
udbg("Too many errors... aborting: %d\n", nerrors);
|
||||||
break;
|
break;
|
||||||
|
Loading…
Reference in New Issue
Block a user