Message ID | 20220118202234.410555-1-terry.bowman@amd.com |
---|---|
Headers | show |
Series | Watchdog: sp5100_tco: Replace cd6h/cd7h port I/O accesses with MMIO accesses | expand |
> I considered sending the request_muxed_mem_region() patch series first but > was concerned the patch might not be accepted without a need or usage. I > didn't see an obvious path forward for the order of submissions because of > the dependencies. My suggestion: make the request_muxed_mem_region() patch the new patch 1 of the piix4 series. Then, the user will directly come in the following patches. From this series, I will create an immutable branch which can be pulled in by the watchdog tree. It will then have the dependency for your watchdog series. During next merge window, we (the maintainers) will make sure that I2C will hit Linus' tree before the watchdog tree. This works the other way around as well, if needed. Make request_muxed_mem_region() the first patch of the watchdog series and let me pull an immutable branch from watchdog into I2C.
> Also, if the immutable branch only includes the patch introducing > request_muxed_mem_region(), the pull order should not really matter. Right, good point!
On Tue, 18 Jan 2022 14:22:30 -0600, Terry Bowman wrote: > Terry Bowman (4): > Watchdog: sp5100_tco: Move timer initialization into function > Watchdog: sp5100_tco: Refactor MMIO base address initialization > Watchdog: sp5100_tco: Add initialization using EFCH MMIO > Watchdog: sp5100_tco: Enable Family 17h+ CPUs > > drivers/watchdog/sp5100_tco.c | 335 ++++++++++++++++++++++------------ > drivers/watchdog/sp5100_tco.h | 6 + > 2 files changed, 227 insertions(+), 114 deletions(-) FWIW, I tested this patch series successfully on my AMD Ryzen 7 PRO 3700U-based laptop.