docs,ports: Fix some comments and error messages with doubled-up words.
Signed-off-by: chuangjinglu <chuangjinglu@outlook.com>
This commit is contained in:
committed by
Damien George
parent
3de3821abf
commit
2e796d6c3e
@@ -665,7 +665,7 @@ L2CAP connection-oriented-channels
|
||||
|
||||
Connect to a listening peer on the specified *psm* with local MTU set to *mtu*.
|
||||
|
||||
On successful connection, the the ``_IRQ_L2CAP_CONNECT`` event will be
|
||||
On successful connection, the ``_IRQ_L2CAP_CONNECT`` event will be
|
||||
raised, allowing the client to obtain the CID and the local and remote (peer) MTU.
|
||||
|
||||
An unsuccessful connection will raise the ``_IRQ_L2CAP_DISCONNECT`` event
|
||||
|
||||
@@ -71,7 +71,7 @@ Methods
|
||||
|
||||
Otherwise, a TimerChannel object is initialized and returned.
|
||||
|
||||
The operating mode is is the one configured to the Timer object that was used to
|
||||
The operating mode is the one configured to the Timer object that was used to
|
||||
create the channel.
|
||||
|
||||
- ``channel`` if the width of the timer is 16-bit, then must be either ``TIMER.A``, ``TIMER.B``.
|
||||
|
||||
@@ -163,7 +163,7 @@ Methods
|
||||
- ``callback`` - as per TimerChannel.callback()
|
||||
|
||||
- ``pin`` None (the default) or a Pin object. If specified (and not None)
|
||||
this will cause the alternate function of the the indicated pin
|
||||
this will cause the alternate function of the indicated pin
|
||||
to be configured for this timer channel. An error will be raised if
|
||||
the pin doesn't support any alternate functions for this timer channel.
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ re-flashing the entire firmware. However, it can still be useful to
|
||||
selectively freeze some rarely-changing dependencies (such as third-party
|
||||
libraries).
|
||||
|
||||
The way to list the Python files to be be frozen into the firmware is via
|
||||
The way to list the Python files to be frozen into the firmware is via
|
||||
a "manifest", which is a Python file that will be interpreted by the build
|
||||
process. Typically you would write a manifest file as part of a board
|
||||
definition, but you can also write a stand-alone manifest file and use it with
|
||||
|
||||
@@ -1671,7 +1671,7 @@ static void prvAddNewTaskToReadyList( TCB_t *pxNewTCB )
|
||||
if( listIS_CONTAINED_WITHIN( &xPendingReadyList, &( pxTCB->xEventListItem ) ) == pdFALSE )
|
||||
{
|
||||
/* Is it in the suspended list because it is in the Suspended
|
||||
state, or because is is blocked with no timeout? */
|
||||
state, or because it is blocked with no timeout? */
|
||||
if( listIS_CONTAINED_WITHIN( NULL, &( pxTCB->xEventListItem ) ) != pdFALSE )
|
||||
{
|
||||
xReturn = pdTRUE;
|
||||
|
||||
@@ -1089,7 +1089,7 @@ static MP_DEFINE_CONST_FUN_OBJ_1(pyb_timer_deinit_obj, pyb_timer_deinit);
|
||||
/// - `callback` - as per TimerChannel.callback()
|
||||
///
|
||||
/// - `pin` None (the default) or a Pin object. If specified (and not None)
|
||||
/// this will cause the alternate function of the the indicated pin
|
||||
/// this will cause the alternate function of the indicated pin
|
||||
/// to be configured for this timer channel. An error will be raised if
|
||||
/// the pin doesn't support any alternate functions for this timer channel.
|
||||
///
|
||||
@@ -1197,7 +1197,7 @@ static mp_obj_t pyb_timer_channel(size_t n_args, const mp_obj_t *pos_args, mp_ma
|
||||
mp_obj_t pin_obj = args[2].u_obj;
|
||||
if (pin_obj != mp_const_none) {
|
||||
if (!mp_obj_is_type(pin_obj, &pin_type)) {
|
||||
mp_raise_ValueError(MP_ERROR_TEXT("pin argument needs to be be a Pin type"));
|
||||
mp_raise_ValueError(MP_ERROR_TEXT("pin argument needs to be a Pin type"));
|
||||
}
|
||||
const machine_pin_obj_t *pin = MP_OBJ_TO_PTR(pin_obj);
|
||||
const pin_af_obj_t *af = pin_find_af(pin, AF_FN_TIM, self->tim_id);
|
||||
|
||||
Reference in New Issue
Block a user