-
Notifications
You must be signed in to change notification settings - Fork 1.4k
arch/arm64/imx9: add support for imx95 #16743
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: lipengfei28 <lipengfei28@xiaomi.com>
@@ -0,0 +1,263 @@ | |||
/**************************************************************************** | |||
* boards/arm64/imx9/imx93-evk/include/board.h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change imx93-evk -> imx95-a55-evk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please split the commit into
arch/arm64/imx9: add imx95 support
boards/arm64/imx9: add imx95 support
documentation/arm64/imx9: add imx95 support
and add commit messages for all commits
|
||
ifeq ($(CONFIG_ARCH_CHIP_IMX93),y) | ||
CHIP_CSRCS += imx9_lpuart.c imx9_lowputc.c | ||
ifeq ($(CONFIG_IMX95_BOOTL_FROM_LINUX),n) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we avoid using this CONFIG_IMX95_BOOTL_FROM_LINUX
macro.
It makes the code unreadable and it's quite a niche try to foucs on
CONFIG_ARCH_CHIP_IMX93
CONFIG_ARCH_CHIP_IMX95
And then in some cases use the CONFIG_IMX95_BOOTL_FROM_LINUX
Note: Please adhere to Contributing Guidelines.
Summary
imx95 board run linux and nuttx at the same time
https://gitee.com/qaq-cmd/adbd/tree/master
cp adbd.service /etc/systemd/system
systemctl start adbd
systemctl enable adbd
./tools/configure.sh imx95-a55-evk:nsh && make
adb push nuttx.bin /root
echo 0 > /sys/devices/system/cpu/cpu0/online
insmod nuttx.ko
[ 1.975564] platform 4acf0000.dsi: Fixed dependency cycle(s) with /soc/bus@44000000/i2c@44350000/hdmi@3d
[ 1.984898] platform hdmi-connector: Fixed dependency cycle(s) with /soc/bus@44000000/i2c@44350000/hdmi@3d
[ 1.994507] i2c 1-003d: Fixed dependency cycle(s) with /soc/dsi@4acf0000
[ 2.001114] i2c 1-003d: Fixed dependency cycle(s) with /hdmi-connector
[ 2.008196] adp5585 1-0034: error -EIO: Failed to read device ID
[ 2.014043] adp5585 1-0034: probe with driver adp5585 failed with error -5
[ 2.020874] i2c i2c-1: LPI2C adapter registered
[ 2.026425] imx8mq-usb-phy 4c1f0040.phy: supply vbus not found, using dummy regulator
[ 2.038785] platform 4ad50000.isi: Fixed dependency cycle(s) with /soc/syscon@4ac10000/formatter@20
[ 2.047684] platform 4ad30000.csi: Fixed dependency cycle(s) with /soc/syscon@4ac10000/formatter@20
[ 2.056765] platform 4ac10000.syscon:formatter@20: Fixed dependency cycle(s) with /soc/isi@4ad50000
[ 2.065674] platform 4ac10000.syscon:formatter@20: Fixed dependency cycle(s) with /soc/csi@4ad30000
[ 2.077393] platform 4acf0000.dsi: Fixed dependency cycle(s) with /soc/syscon@4b010000/bridge@8
[ 2.085936] platform 4b010000.syscon:bridge@8: Fixed dependency cycle(s) with /soc/dsi@4acf0000
[ 2.094563] platform 4b010000.syscon:bridge@8: Fixed dependency cycle(s) with /soc/bridge@4b0d0000/channel@0
[ 2.110173] 42590000.serial: ttyLP0 at MMIO 0x42590010 (irq = 110, base_baud = 1500000) is a FSL_LPUART
[ 2.119462] printk: legacy console [ttyLP0] enabled
[ 2.129043] printk: legacy bootconsole [lpuart32] disabled
NuttShell (NSH) NuttX-12.9.0
nsh>
nsh>
nsh>
nsh> ls
/:
dev/
proc/
nsh>
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.