Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sn32 develop June 2023 update #54

Merged
merged 54 commits into from
Jun 16, 2023
Merged

Conversation

minh7a6 and others added 30 commits September 11, 2022 16:45
The USBHSv1 LLD for KINETIS was checking `epc->in_cb` and `epc->out_cb`
to be non-NULL before calling `_usb_isr_invoke_in_cb()` and
`_usb_isr_invoke_out_cb()`.  This is not correct, because if the
`USB_USE_WAIT` option is enabled, those ChibiOS macros do more than just
invoking the callback - they also resume the thread that may be waiting
for the transfer completion, and omitting the call results in that
thread never getting resumed.  The macros also perform the same pointer
check internally before invoking the callback.

Remove the unneeded checks to make the driver work properly with any
APIs enabled by `USB_USE_WAIT`.
The USBHSv1 LLD for MIMXRT1062 was checking `epc->in_cb` and
`epc->out_cb` to be non-NULL before calling `_usb_isr_invoke_in_cb()`
and `_usb_isr_invoke_out_cb()`.  This is not correct, because if the
`USB_USE_WAIT` option is enabled, those ChibiOS macros do more than just
invoking the callback - they also resume the thread that may be waiting
for the transfer completion, and omitting the call results in that
thread never getting resumed.  The macros also perform the same pointer
check internally before invoking the callback.

Remove the unneeded checks to make the driver work properly with any
APIs enabled by `USB_USE_WAIT`.  Also remove the manipulation of
`(usbp)->receiving` and `(usbp)->transmitting`, because the
`_usb_isr_invoke_in_cb()` and `_usb_isr_invoke_out_cb()` macros handle
that part too.
Fixes issue where GPTD_BFTM0 would point to BFTM1 when
HT32_GPT_USE_BFTM0 and HT32_GPT_USE_BFTM1 are defined True (and leaving
GPTD_BFTM1 unused).

Additionally, this fixes undeclared variable warning when only
HT32_GPT_USE_BFTM1 is defined True.
scsi_transport_transmit returns the length instead of the status message.
RP2040 i2c peripherals are numbered starting from zero, therefore the drivers
shall follow the same numbering e.g. I2C0 uses the driver I2CD0. This commit
fixes the current missmatch.
SAMD21: Adding Initial Support for SAMD21A
HT32: hal: Fix misleading indentation errors
fpoussin and others added 24 commits December 9, 2022 23:26
[RP2040] update i2c drivers to reflect peripheral number
For context, the page size of HT32F523xx is 512 bytes (see page 42 of
HT32F52342/HT3252352 User Manual v1.30) and certain bootloaders jump to
addresses that are not aligned to 1024 bytes (specified by common
rules_code.ld). This commit updates the example ld scripts so that these
bootloaders can correctly map the vector table and boot a ChibiOS
application firmware.
This change introduces basic WDT HAL driver functionality (start, stop,
reload) for HT32F165x and HT32F523xx.
HT32: Add low level driver for WDT
…or-align

HT32: ld: Fix vector table alignment for HT32F523xx
The RP2040 ADC driver was initializing adcp->current_buffer_position and
friends only in adc_lld_start(), therefore a simple adcConvert() call
did not work when called a second time (only the circular mode worked,
because the interrupt handler was resetting the position in that case
after the whole buffer was filled).  Reset the buffer position variables
in adc_lld_start_conversion() to make the one-time conversion work.
RP2040: Init buffer position in adc_lld_start_conversion()
Fixup compilation with gcc12, warnings due to indenting.
Fixed some issues with usb_msd for stm32l496
We need to set the logical HIGH/LOW state here
NOT mess with DATA
add missing hooks for GPTD2
fixup the prescaler assert check
update the interrupt handler
@dexter93 dexter93 merged commit db448c5 into SonixQMK:sn32_develop Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants