Skip to content
  1. Oct 19, 2017
    • Jussi Kivilinna's avatar
      drivrs/mtd/filemtd.c: add block device MTD interface. Block MTD interface... · 5ef54867
      Jussi Kivilinna authored
      drivrs/mtd/filemtd.c: add block device MTD interface.  Block MTD interface allows using block device directly as MTD instead of having to use file-system in between.  NOTE that this provides the opposite capability of FTL which will let you use an MTD interface directly as a block device.
      5ef54867
    • Alan Carvalho de Assis's avatar
    • Sebastien Lorquet's avatar
      drivers/ioexpander: The IRQ subsystem now supports passing a void * parameter... · 1182702b
      Sebastien Lorquet authored
      drivers/ioexpander:  The IRQ subsystem now supports passing a void * parameter to IRQ handlers.  Use that method to support multiple pc9555 devices, by passing a pointer to the device to the board defined irq handler.  Now the CONFIG_ for multiple PCA devices just allocates device structures dynamically instead of statically when not enabled.
      
      The same interrupt handler is entered with the device structure parameter in all situations,
      multiple or single PCA. One should still be careful if multiple PCA devices share the same IRQ.
      1182702b
    • Mattias Edlund's avatar
      The timer frequencies (BOARD_TIMx_FREQUENCY) are incorrectly defined... · ee1330ed
      Mattias Edlund authored
      The timer frequencies (BOARD_TIMx_FREQUENCY) are incorrectly defined in configs/stm3240g-eval/include/board.h.  Since the APB prescalers are set to divide by 4 and 2 respectively, the frequencies should be "2xAPBx" as said in the comment.  The correct frequencies are already defined but as STM32_APBx_TIMx_CLKIN.
      ee1330ed
    • Gregory Nutt's avatar
      Alexey T, Bitbuck Issue 73: · ffca71b9
      Gregory Nutt authored
      Lower part of STM32 CAN driver arch/arm/src/stm32/stm32_can.c uses all three hw tx mailboxes and clears TXFP bit in the CAN_MCR register (it means transmission order is defined by identifier and mailbox number).
      
      This creates situation when order frames are put in upper part of CAN driver (via can_write) and order frames are sent on bus can be different (and I experience this in wild).
      
      Since CAN driver API pretends to be "file like" I expect data to be read from fd the same order it is written. So I consider described behaviour to be a bug.
      
      I propose either to set TXFP bit in the CAN_MCR register (FIFO transmit order) or to use only one mailbox.
      ffca71b9
  2. Oct 18, 2017
  3. Oct 17, 2017
  4. Oct 16, 2017
  5. Oct 15, 2017