Hi Sagar, On Tue, 28 Jul 2020 at 09:19, Sagar Kadam <[email protected]> wrote: > > Hello Rick, > > > -----Original Message----- > > From: Sagar Kadam > > Sent: Monday, July 27, 2020 8:56 PM > > To: [email protected] > > Cc: [email protected]; Paul Walmsley ( Sifive) > > <[email protected]>; [email protected]; [email protected]; > > [email protected]; [email protected]; Pragnesh Patel > > <[email protected]>; [email protected]; > > [email protected]; [email protected]; [email protected]; > > [email protected]; [email protected]; [email protected]; > > [email protected]; [email protected]; [email protected]; > > [email protected] > > Subject: RE: [PATCH v4 0/5] add DM based reset driver for SiFive SoC's > > > > Hi Rick, > > > -----Original Message----- > > > From: Sagar Kadam <[email protected]> > > > Sent: Friday, July 24, 2020 2:17 PM > > > To: [email protected] > > > Cc: [email protected]; Paul Walmsley ( Sifive) > > > <[email protected]>; [email protected]; > > [email protected]; > > > [email protected]; [email protected]; Pragnesh Patel > > > <[email protected]>; [email protected]; > > > [email protected]; [email protected]; [email protected]; > > > [email protected]; [email protected]; [email protected]; > > > [email protected]; [email protected]; > > [email protected]; > > > [email protected]; Sagar Kadam <[email protected]> > > > Subject: [PATCH v4 0/5] add DM based reset driver for SiFive SoC's > > > > > > The FU540-C000 support in U-Boot is missing DM based reset driver, and is > > > handling reset's to sub-system within the prci driver itself. > > > The series here adds a generic DM reset driver for SiFive SoC's so as to > > > leverage the U-Boot's reset framework and binds the reset driver with prci > > > driver. > > > The PRCI driver takes care of triggering the consumers reset signals > > > appropriately. > > > > > > Patch 1: Add necessary dt indexes for device reset register. > > > Patch 2: Update macro's to use common dt indexes from binding header. > > > Patch 3: Add reset producer and consumer entries within the device tree. > > > Patch 4: Add reset dm driver and bind it within prci module. > > > Patch 5: Add Kconfig, Makefile entries and enable the driver > > > > > > This series is re-based on mainline U-Boot commit 5d3a21df6694 ("Merge > > tag > > > 'dm-pull-20jul20' of git://git.denx.de/u-boot-dm") and depends on [1] > > > > > > [1] https://patchwork.ozlabs.org/project/uboot/list/?series=190862 > > > > > > > I have rebased this series on u-boot/master. > > Can you please pull it and let me know if any issues are there. > > > It seems that u-boot/master is moved ahead and the commit on which this series > was based is reverted "Revert "Merge tag 'dm-pull-20jul20' of > git://git.denx.de/u-boot-dm"" > and will again conflict considering other patch's that are merged in > u-boot/master. > I can rebase it again, but would like to know what you would prefer me to > rebase on u-boot/master > or u-boot-riscv/master?
Can you take another look? The DM stuff landed again yesterday. Regards, Simon
