lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 14 Feb 2020 13:32:09 -0800
From:   Julius Werner <>
To:     Guenter Roeck <>
Cc:     Evan Benn <>,
        LKML <>,
        Julius Werner <>,
        Bjorn Andersson <>,
        Mauro Carvalho Chehab <>,
        Marcin Juszkiewicz <>,
        Catalin Marinas <>,
        Olof Johansson <>,
        Leonard Crestez <>,
        Jonathan Cameron <>,
        Dinh Nguyen <>,,
        Greg Kroah-Hartman <>,
        Will Deacon <>,,
        Rob Herring <>,
        Wim Van Sebroeck <>,
        Clément Péron <>,
        Shawn Guo <>,
        "David S. Miller" <>,
        Anson Huang <>
Subject: Re: [PATCH 2/2] watchdog: Add new arm_smc_wdt watchdog driver

> > with a Secure Monitor firmware to forward watchdog operations to
> > firmware via a Secure Monitor Call. This may be useful for platforms
> > using TrustZone that want the Secure Monitor firmware to have the final
> > control over the watchdog.
> >
> As written, one would assume this to work on all systems implementing
> ARM secure firmware, which is not the case. Please select a different
> name, and provide information about the systems where this is actually
> supported.
> If it happens to be standardized, we will need a reference to the standard
> supported. This needs to distinguish from IMX_SC_WDT, which also supports
> a secure monitor based watchdog (but doesn't claim to be generic).

Back when I wrote this I was hoping it could be something that other
platforms can pick up if they want to, but that hasn't happened yet
and the code on the Trusted Firmware side is still MediaTek-specific.
Unfortunately Arm doesn't make it easy to write generic SMC interfaces
and my attempts to change that haven't been very fruitful for now. So
yes, probably makes sense to treat this as MediaTek-specific for now,
we can still consider expanding it later if there's interest from
other platforms. (I would like to avoid every vendor writing their own
driver and SMC interface for this, although looking at that IMX driver
it seems that we're already there.)

Powered by blists - more mailing lists