ProcessorInterface: Remove prefixed underscores from parameters
These are reserved by the implementation for any use.
This commit is contained in:
parent
419ed1b46a
commit
a8088b7365
|
@ -135,9 +135,9 @@ void UpdateException()
|
||||||
PowerPC::ppcState.Exceptions &= ~EXCEPTION_EXTERNAL_INT;
|
PowerPC::ppcState.Exceptions &= ~EXCEPTION_EXTERNAL_INT;
|
||||||
}
|
}
|
||||||
|
|
||||||
static const char* Debug_GetInterruptName(u32 _causemask)
|
static const char* Debug_GetInterruptName(u32 cause_mask)
|
||||||
{
|
{
|
||||||
switch (_causemask)
|
switch (cause_mask)
|
||||||
{
|
{
|
||||||
case INT_CAUSE_PI:
|
case INT_CAUSE_PI:
|
||||||
return "INT_CAUSE_PI";
|
return "INT_CAUSE_PI";
|
||||||
|
@ -176,33 +176,33 @@ static const char* Debug_GetInterruptName(u32 _causemask)
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
void SetInterrupt(u32 _causemask, bool _bSet)
|
void SetInterrupt(u32 cause_mask, bool set)
|
||||||
{
|
{
|
||||||
DEBUG_ASSERT_MSG(POWERPC, Core::IsCPUThread(), "SetInterrupt from wrong thread");
|
DEBUG_ASSERT_MSG(POWERPC, Core::IsCPUThread(), "SetInterrupt from wrong thread");
|
||||||
|
|
||||||
if (_bSet && !(m_InterruptCause & _causemask))
|
if (set && !(m_InterruptCause & cause_mask))
|
||||||
{
|
{
|
||||||
DEBUG_LOG(PROCESSORINTERFACE, "Setting Interrupt %s (set)", Debug_GetInterruptName(_causemask));
|
DEBUG_LOG(PROCESSORINTERFACE, "Setting Interrupt %s (set)", Debug_GetInterruptName(cause_mask));
|
||||||
}
|
}
|
||||||
|
|
||||||
if (!_bSet && (m_InterruptCause & _causemask))
|
if (!set && (m_InterruptCause & cause_mask))
|
||||||
{
|
{
|
||||||
DEBUG_LOG(PROCESSORINTERFACE, "Setting Interrupt %s (clear)",
|
DEBUG_LOG(PROCESSORINTERFACE, "Setting Interrupt %s (clear)",
|
||||||
Debug_GetInterruptName(_causemask));
|
Debug_GetInterruptName(cause_mask));
|
||||||
}
|
}
|
||||||
|
|
||||||
if (_bSet)
|
if (set)
|
||||||
m_InterruptCause |= _causemask;
|
m_InterruptCause |= cause_mask;
|
||||||
else
|
else
|
||||||
m_InterruptCause &= ~_causemask; // is there any reason to have this possibility?
|
m_InterruptCause &= ~cause_mask; // is there any reason to have this possibility?
|
||||||
// F|RES: i think the hw devices reset the interrupt in the PI to 0
|
// F|RES: i think the hw devices reset the interrupt in the PI to 0
|
||||||
// if the interrupt cause is eliminated. that isn't done by software (afaik)
|
// if the interrupt cause is eliminated. that isn't done by software (afaik)
|
||||||
UpdateException();
|
UpdateException();
|
||||||
}
|
}
|
||||||
|
|
||||||
static void SetResetButton(bool _bSet)
|
static void SetResetButton(bool set)
|
||||||
{
|
{
|
||||||
SetInterrupt(INT_CAUSE_RST_BUTTON, !_bSet);
|
SetInterrupt(INT_CAUSE_RST_BUTTON, !set);
|
||||||
}
|
}
|
||||||
|
|
||||||
static void ToggleResetButtonCallback(u64 userdata, s64 cyclesLate)
|
static void ToggleResetButtonCallback(u64 userdata, s64 cyclesLate)
|
||||||
|
|
|
@ -73,7 +73,7 @@ inline u32 GetCause()
|
||||||
return m_InterruptCause;
|
return m_InterruptCause;
|
||||||
}
|
}
|
||||||
|
|
||||||
void SetInterrupt(u32 _causemask, bool _bSet = true);
|
void SetInterrupt(u32 cause_mask, bool set = true);
|
||||||
|
|
||||||
// Thread-safe func which sets and clears reset button state automagically
|
// Thread-safe func which sets and clears reset button state automagically
|
||||||
void ResetButton_Tap();
|
void ResetButton_Tap();
|
||||||
|
|
Loading…
Reference in New Issue