Hi Tom, Could you help us on the review of the following patches for Aspeed platform code? http://patchwork.ozlabs.org/project/uboot/cover/20200908072104.10067-1-chiawei_w...@aspeedtech.com/ http://patchwork.ozlabs.org/project/uboot/cover/20200907082507.22290-1-dylan_h...@aspeedtech.com/
These patches are in fact refactoring to the existing Aspeed code structure in U-Boot. When the refactoring is done, we would like to send a patch series for the support of Aspeed next generation SoC (AST2600). Thanks. Chiawei > -----Original Message----- > From: ChiaWei Wang <chiawei_w...@aspeedtech.com> > Sent: Tuesday, September 8, 2020 3:21 PM > To: Ryan Chen <ryan_c...@aspeedtech.com>; max...@google.com; > u-boot@lists.denx.de > Cc: BMC-SW <bmc...@aspeedtech.com> > Subject: [PATCH 0/2] Refactor AST2500 reset control > > This patch series refactors the reset method to use the System Control Unit > (SCU) reset control for simplicity. > > In addition, the naming of reset driver and Kconfig option is also refined for > future consistency. > > Chia-Wei, Wang (2): > reset: ast2500: Use SCU for reset control > cosmetic: reset: ast2500: Rename driver and configs > > arch/arm/dts/ast2500-u-boot.dtsi | 7 +- > drivers/reset/Kconfig | 11 +-- > drivers/reset/ast2500-reset.c | 104 --------------------- > drivers/reset/reset-ast2500.c | 109 > ++++++++++++++++++++++ > include/dt-bindings/reset/ast2500-reset.h | 73 ++++++++------- > 5 files changed, 156 insertions(+), 148 deletions(-) delete mode 100644 > drivers/reset/ast2500-reset.c create mode 100644 > drivers/reset/reset-ast2500.c > > -- > 2.17.1
