* Mostly arch/arm/src/imxrt and include/imxrt: This commit gets imx1020 family support started. It is pretty similar, but subtly different, to 1050/60 (less PLLs, less GPIO banks, differently numbered ports etc. etc.). I think it's time to at least look at what needs to be done before we can get these into the mainline kernel even though they're not properly mature yet. Core memory functions, PLLs, serial and networking are all working, but there's no stress-testing or similar been done...I'm not aware of anything broken, but there again I haven't looked too hard.
I want to go through and start moving each of the imxrt family-specific files into its own subdirectory to tidy things up a bit, and remove the vast majority of ifdefs from the mainline code...but I think it's appropriate to separate the cleanup steps from the new-chip-suppport steps to keep things a bit more compartmentalized. Next week is a travel week so it's possible I'll get time on the cleanup side of the house.
I can't be 100% certain I didn't inflict casualties on the imxrt1050/60 code in the process of doing this, but nsh for 1050 and netnsh and nsh for the 1060 both compile correctly, so if I did break anything it's going to be properly evil and difficult to find.
* include/nuttx/usb/hid.h: The usbhid_descriptor_s struct defined in hid.h included some optional fields that should not be hard-defined as part of that structure. An arbitrray number of optional entries could be included in the descriptor, but that is not properly represneted. No code on NuttX currently depends on the structure definition with an optional descriptor so it is safe to remove.
* Directory re-arrangement and splitting of each imxrt family variant
* Prevent intermittent SDCard timeouts by increasing timer in line with spec.
* Support data dump on Hardfault
* Fix missing ccm definitions and wrong iomux offset
* Prevent hardfault when can't read from ENET PHY
* More consistent Ethernet pinmux
* Mostly arch/arm/src/imxrt and include/imxrt: This commit gets imx1020 family support started. It is pretty similar, but subtly different, to 1050/60 (less PLLs, less GPIO banks, differently numbered ports etc. etc.). I think it's time to at least look at what needs to be done before we can get these into the mainline kernel even though they're not properly mature yet. Core memory functions, PLLs, serial and networking are all working, but there's no stress-testing or similar been done...I'm not aware of anything broken, but there again I haven't looked too hard.
I want to go through and start moving each of the imxrt family-specific files into its own subdirectory to tidy things up a bit, and remove the vast majority of ifdefs from the mainline code...but I think it's appropriate to separate the cleanup steps from the new-chip-suppport steps to keep things a bit more compartmentalized. Next week is a travel week so it's possible I'll get time on the cleanup side of the house.
I can't be 100% certain I didn't inflict casualties on the imxrt1050/60 code in the process of doing this, but nsh for 1050 and netnsh and nsh for the 1060 both compile correctly, so if I did break anything it's going to be properly evil and difficult to find.
* Directory re-arrangement and splitting of each imxrt family variant
* Prevent intermittent SDCard timeouts by increasing timer in line with spec.
* Support data dump on Hardfault
* Fix missing ccm definitions and wrong iomux offset
* Prevent hardfault when can't read from ENET PHY
* More consistent Ethernet pinmux
* Various small commits starting i2c debug
libs/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
syscall/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
wireless/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
Documentation/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
include/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
drivers/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
sched/: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
configs: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
arch/xtensa: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
arch/z80: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
arch/x86: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
arch/renesas and arch/risc-v: Remove references to CONFIG_DISABLE_SIGNALS. Signals can no longer be disabled.
arch/or1k: Remove all references to CONFIG_DISABLE_SIGNALS. Signals are always enabled.
arch/misoc: Remove all references to CONFIG_DISABLE_SIGNALS. Signals are always enabled.
arch/mips: Remove all references to CONFIG_DISABLE_SIGNALS. Signals are always enabled.
arch/avr: Remove all references to CONFIG_DISABLE_SIGNALS. Signals are always enabled.
arch/arm: Remove all references to CONFIG_DISABLE_SIGNALS. Signals are always enabled.
Add some I2C devices to nucleo-h743zi and a few small fixes
configs/nucleo-h743zi: add support for ssd1306
configs/nucleo-h743zi: add support for pca9635
configs/nucleo-h743zi: add support for i2ctools
include/nuttx/sensors/lsm6dsl.h: remove whitespaces
configs/stm32f103-minimum/src/stm32_ssd1306.c: cosmetics
Documentation/NuttxPortingGuide.html: vsyslog return none
drivers/syslog/README.txt: vsyslog return none
Approved-by: Gregory Nutt <gnutt@nuttx.org>
stm32f7: Add basic PWM support to nucleo-144 board
More PWMs and multi channels support
may be investigated and added later.
It was tested on nucleo-f767zi
with those features enabled in configuration:
```
CONFIG_EXAMPLES_PWM=y
CONFIG_PWM=y
CONFIG_STM32F7_TIM1=y
CONFIG_STM32F7_TIM1_PWM=y
CONFIG_STM32F7_TIM2=y
(...)
CONFIG_STM32F7_TIM4_PWM=y
```
Change-Id: I08ebd4a538d15661788a0a54c2113ad767f22747
Bug: https://bitbucket.org/nuttx/nuttx/issues/153
Relate-to: https://github.com/rzr/webthing-iotjs/issues/3
Forwarded: https://bitbucket.org/nuttx/nuttx/pull-requests/862
Signed-off-by: Philippe Coval <p.coval@samsung.com>
Approved-by: Gregory Nutt <gnutt@nuttx.org>
nucleo-144: Mount sysfs for ifconfig for f767-netnsh/defconfig
Even if ifconfig is working to set IP,
it will not work to display NICs (without args)
Change-Id: I62e0b2b5517620c5bc2dd4d3f5bf6f1e0f329d44
Relate-to: https://github.com/rzr/webthing-iotjs/issues/3
Signed-off-by: Philippe Coval <p.coval@samsung.com>
Approved-by: Gregory Nutt <gnutt@nuttx.org>
This reverts commit 2bc709d4b9.
Commit 2bc709d4b9 was intended to handle the case where up_timer_gettime may not start from zero case. However, this change has the side-effect of breaking every implementation of tickless mode: After this change the tickless timer structures are used before they are initialized in clock_inittime(). Initialization happens later when up_initialize is called() when arm_timer_initialize().
Since the tickless mode timer is very special, one solution might be to
1. Rename xxx_timer_initialize to up_timer_initialize
2 Move up_timer_initialize to include/nuttx/arch.h
3. Call it from clock subsystem instead up_initialize
Basically, this change make timer initialization almost same as rtc initialization(up_rtc_initialize).
For now, however, we just need to revert the change.
nucleo-144: Regenerate f767-netnsh/defconfig
It appear that CONFIG_NET_SOCKOPTS,
is no more explicity needed.
Change-Id: I33e1b60ce1778bb963f709b963c89ef6b489c362
Signed-off-by: Philippe Coval <p.coval@samsung.com>
Approved-by: Gregory Nutt <gnutt@nuttx.org>
arch/arm/src/stm32/stm32_i2s.c: In debug assertions, it on a sample rate of 0, but based on other code comments this value implies disabling the i2s master clock.
arch/arm/src/stm32/stm32_usbhost.h and arch/arm/src/stm32/Kconfig: Allow vbus monitoring for the OTG_HS host driver.
