Move hw-locks to new mutex API in multiple steps to keep diffs readable.  The
users of hw-locks are **not** ported to the new-semantics; this needs to be
done as a follow up.  One patch is included, porting the MAX30001 driver in
commit 6da4644e ("chore(max30001): Port to new mutex and hw-lock APIs").

See merge request card10/firmware!356

Using a FreeRTOS mutex directly is deprecated.  Replace it with a
`struct mutex`.  Similarly, the deprecated `hwlock_acquire_timeout()`
is replaced with `hwlock_acquire()`.

Signed-off-by: Rahix <rahix@rahix.de>

Re-add a `hwlock_acquire()` method, but this time without a timeout
parameter.  From a functional point of view, this is just a wrapper
around `mutex_lock()`.

Additionally, add `hwlock_acquire_nonblock()` which behaves like
`mutex_trylock()`.

Signed-off-by: Rahix <rahix@rahix.de>

Rename hwlock_acquire() to hwlock_acquire_timeout() in preparation for
future changes to the hw-lock API.  Change all uses of the hw-lock API
to reflect this change.

This commit does not introduce any functional changes, except getting
rid of the timeout usage warnings.  This change is no-op, because the
hwlock_acquire() implementation already replaces any non-zero timeout
value with portMAX_DELAY.

Signed-off-by: Rahix <rahix@rahix.de>

With the switch to the new mutex API, hwlock_release() cannot fail under
any circumstances.  To emphasize this, make it return void instead of
int (Previously it just always returned 0).

Signed-off-by: Rahix <rahix@rahix.de>

Reimplement the hw-lock module to use the new mutex API.  This slightly
changes the semantics of locking a hw-lock as the new mutex API does not
allow timeouts.  When a hwlock_acquire() with a (non-infinite) timeout
is attempted, a warning is printed to the serial console.

Additionally, instead of returning -EINVAL on use of a non-existent
hardware lock, the new implementation triggers a firmware panic.

Signed-off-by: Rahix <rahix@rahix.de>

The poor-profiler scripts allow profiling card10 (to some degree).

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

See merge request card10/firmware!337

fuchsi* authored 5 years ago and rahix committed 5 years ago

fix performance problems with pulse logging (caching time string and approximating timestamp via samplecount)

See merge request card10/firmware!361

Signed-off-by: Rahix <rahix@rahix.de>

Closes #192

See merge request card10/firmware!360

Signed-off-by: Rahix <rahix@rahix.de>

With the increased warning-level, GCC warns about three unused fields in
`bleSmpCfg`:

    - maxAttemptTimeout: Maximum 'Repeated attempts' timeout in msec
    - attemptDecTimeout: Time msec before attemptExp decreases
    - attemptExp: Exponent to raise attemptTimeout on maxAttempts

These should probably be set to sensible values but to make !360
mergeable, explicitly set them to zero for now.

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

By passing `&resched` instead of just `resched`, the internal comparison
in FreeRTOS would always evaluate to rescheduling.  Curiously, only some
GCC versions emit the -Waddress warning for this while others do not ...

Signed-off-by: Rahix <rahix@rahix.de>

Fix sign-compare warnings for these constants.

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

It does not make sense for the filesize to be given as `int`; it cannot
ever be negative.  Instead, use `size_t` which is unsigned.

Signed-off-by: Rahix <rahix@rahix.de>

Fix all warnings in pycardium/modules.

Signed-off-by: Rahix <rahix@rahix.de>

Fix all warnings in epicardium/modules.

Signed-off-by: Rahix <rahix@rahix.de>

Make the length parameter a `size_t` instead of a `intptr_t`.  A signed
value does not make any sense here and just leads to weird behavior if a
negative value is given nonetheless.

See issue card10/firmware#192

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Disable the `unused-parameter` warning for the mpy-cross-wrapper to
silence an error about `argc` being unused (which is ok).

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

The crc_patch utility displays the following warning:

    bootloader/./crc_patch.py:31: DeprecationWarning: PY_SSIZE_T_CLEAN
        will be required for '#' formats

We cannot fix the offending library so disable the warnings to prevent
unnecessary build-log clutter.

Signed-off-by: Rahix <rahix@rahix.de>

Fix the following warning:

    lib/sdk/Libraries/Boards/card10/Source/board.c: In function 'Board_Init':
    lib/sdk/Libraries/Boards/card10/Source/board.c:102:19: warning:
             comparison of integer expressions of different signedness:
             'int' and 'unsigned int' [-Wsign-compare]
      102 |     for (i = 0; i < num_pins; i++) {
          |                   ^

Signed-off-by: Rahix <rahix@rahix.de>