Pipe_ConfigurePipe() now automatically defaults IN pipes to accepting infinite IN requests, this can still be changed by calling the existing \ref Pipe_SetFiniteINRequests() function.
This commit is contained in:
@@ -96,7 +96,6 @@ void Bluetooth_ProcessHCICommands(void)
|
||||
{
|
||||
case Bluetooth_Init:
|
||||
Pipe_SelectPipe(BLUETOOTH_EVENTS_PIPE);
|
||||
Pipe_SetInfiniteINRequests();
|
||||
|
||||
memset(&Bluetooth_Connection, 0x00, sizeof(Bluetooth_Connection));
|
||||
|
||||
|
||||
@@ -86,7 +86,6 @@ uint8_t ProcessConfigurationDescriptor(void)
|
||||
EndpointData->EndpointAddress, EndpointData->EndpointSize,
|
||||
PIPE_BANK_SINGLE);
|
||||
|
||||
Pipe_SetInfiniteINRequests();
|
||||
Pipe_SetInterruptPeriod(EndpointData->PollingIntervalMS);
|
||||
|
||||
/* Set the flag indicating that the events notification pipe has been found */
|
||||
@@ -102,8 +101,6 @@ uint8_t ProcessConfigurationDescriptor(void)
|
||||
EndpointData->EndpointAddress, EndpointData->EndpointSize,
|
||||
PIPE_BANK_SINGLE);
|
||||
|
||||
Pipe_SetInfiniteINRequests();
|
||||
|
||||
/* Set the flag indicating that the data IN pipe has been found */
|
||||
FoundEndpoints |= (1 << BLUETOOTH_DATA_IN_PIPE);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user