Message ID | 20200421110520.197930-1-evanbenn@chromium.org (mailing list archive) |
---|---|
Headers | show |
Series | Add a watchdog driver that uses ARM Secure Monitor Calls. | expand |
On 4/21/20 4:05 AM, Evan Benn wrote: > This is currently supported in firmware deployed on oak, hana and elm mt8173 > chromebook devices. The kernel driver is written to be a generic SMC > watchdog driver. > > Arm Trusted Firmware upstreaming review: > https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/3405 > > Patch to add oak, hana, elm device tree: > https://lore.kernel.org/linux-arm-kernel/20200110073730.213789-1-hsinyi@chromium.org/ > I would like to add the device tree support after the above patch is > accepted. > > Changes in v4: > - Add arm,smc-id property > - Get smc-id from of property > - Return a1 instead of a0 in timeleft > Subject says v2. This is confusing, at the very least. Guenter > Changes in v3: > - Change name back to arm > - Add optional get_timeleft op > - change name to arm_smc_wdt > > Changes in v2: > - Change name arm > mt8173 > - use watchdog_stop_on_reboot > - use watchdog_stop_on_unregister > - use devm_watchdog_register_device > - remove smcwd_shutdown, smcwd_remove > - change error codes > > Evan Benn (1): > dt-bindings: watchdog: Add ARM smc wdt for mt8173 watchdog > > Julius Werner (1): > watchdog: Add new arm_smc_wdt watchdog driver > > .../bindings/watchdog/arm-smc-wdt.yaml | 36 ++++ > MAINTAINERS | 7 + > arch/arm64/configs/defconfig | 1 + > drivers/watchdog/Kconfig | 13 ++ > drivers/watchdog/Makefile | 1 + > drivers/watchdog/arm_smc_wdt.c | 194 ++++++++++++++++++ > 6 files changed, 252 insertions(+) > create mode 100644 Documentation/devicetree/bindings/watchdog/arm-smc-wdt.yaml > create mode 100644 drivers/watchdog/arm_smc_wdt.c >
> Subject says v2. This is confusing, at the very least. > > Guenter Apologies! I am using the patman script, it threw this message that I did not understand: 'Change log for unknown version v3'. And I did not spot the issue in the emails before send. Not sure why patman worked for v2 and v3 but not v4... I will take a look. Evan