Hi Yang,
On Sat, Feb 3, 2024 at 10:59 AM Yang Xiwen forbidden405@foxmail.com wrote:
On 2/3/2024 5:45 PM, Yang Xiwen wrote:
On 2/3/2024 4:32 PM, Jorge Ramirez-Ortiz, Gmail wrote:
On 03/02/24 07:54:22, Shawn Guo wrote:
On Sat, Feb 3, 2024 at 5:44 AM Igor Opaniuk igor.opaniuk@foundries.io wrote:
Add myself as co-maintainer for Poplar board, as I'm currently working on it (re-testing releases, addressing issues etc).
CC: Jorge Ramirez-Ortiz jorge.ramirez.ortiz@gmail.com CC: Shawn Guo shawn.guo@linaro.org Signed-off-by: Igor Opaniuk igor.opaniuk@foundries.io
Acked-by: Shawn Guo shawn.guo@linaro.org
I'm not actively working on poplar any more, so maybe remove me in the meantime.
hi Igor,
Yes please go ahead and thanks for offering.
I'll sync with you later next week (I found my Poplar in storage, so maybe we cam improve things a little) Also it would be good if we knew there are still users.
Acked-by: Jorge Ramirez-Ortiz jorge.ramirez.ortiz@gmail.com
Hi, everyone. I'm working on a set-top box with a Hi3798MV200 SoC. It is very similar to the Hi3798CV200 SoC and many peripherals and drivers can be reused. I think you can try moving arch/arm/include/asm/arch-hi3798cv200 to arch/arm/mach-histb and let's maintain all HiSTB series SoCs/boards under it altogether? The same thing also applies to TF-A. Currently upstream code refers to poplar everywhere but actually the port is portable enough to handle a lot of other Hi3798-series SoCs such as Hi3798MV2x, Hi3798MV3x etc..
There are some patches i sent pending for review. They are mostly originally sent just for Hi3798MV200, but the framework(such as drivers/clk/hisilicon) can be also used for poplar too. I hope you guys can take a look at them[1] and give your opinions about them(RBs and Acks are welcomed).
Sure, I'll take a look during this week .
[1] HiSi clk framework: https://lore.kernel.org/u-boot/20240119-b4-hisi-clk-v1-0-279e38c95ca2@outloo...
Shawn