On 25-02-27 12:52:36, Jianfeng Liu wrote: > Hi Peter, > > I'm really happy to see the linux mainline upstream work sent. And I have > also reveived radxa orion o6 before the Chinese new year. I have heard > that CIX is testing vendor kernel with ACPI. And now the mainline upstream > work is based on devicetree. I want to know what the upstream work of CIX > would go in the future, are we going to toggle to ACPI instead of > devicetree? > > And it would be good to let outsiders know the plan/roadmap of upstream. > For example collaboara is doing good job on upstreaming rockchip[1][2] and > mediatek[3] socs. > > [1] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md > [2] https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3576/-/blob/main/mainline-status.md?ref_type=heads > [3] https://gitlab.collabora.com/mediatek/aiot/wiki/-/blob/main/mainline-status.md > Hi Jianfeng, Thanks for your interesting of our hardware. Radxa will open our v6.1 device tree vendor kernel source code at the beginning of next month. For ACPI vendor kernel source code based on v6.6, it has planned to open at Q2 of this year. For upstream, we will submit support based on device tree first, since some common code changes are needed for supporting ACPI well at Arm, it may involve lots of discussion. After most of IP drivers are supported by upstream kernel, we will start ACPI upstream work. For upstream status record for CIX SoC, we will find some public place for it. -- Best regards, Peter
