lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 26 Feb 2020 11:30:51 -0800 From: Julius Werner <jwerner@...omium.org> To: Rob Herring <robh+dt@...nel.org> Cc: Evan Benn <evanbenn@...omium.org>, LKML <linux-kernel@...r.kernel.org>, Julius Werner <jwerner@...omium.org>, "David S. Miller" <davem@...emloft.net>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Guenter Roeck <linux@...ck-us.net>, Jonathan Cameron <Jonathan.Cameron@...wei.com>, Mark Rutland <mark.rutland@....com>, Matthias Brugger <matthias.bgg@...il.com>, Mauro Carvalho Chehab <mchehab+samsung@...nel.org>, Wim Van Sebroeck <wim@...ux-watchdog.org>, devicetree@...r.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>, "moderated list:ARM/Mediatek SoC support" <linux-mediatek@...ts.infradead.org>, LINUX-WATCHDOG <linux-watchdog@...r.kernel.org> Subject: Re: [PATCH v2 1/2] dt-bindings: watchdog: Add mt8173,smc-wdt watchdog > Not quite. /firmware is generic container. I'd expect another layer in > the middle for the overall set of Mediatek firmware behind smc calls. > Look at 'xlnx,zynqmp-firmware' for an example. There are no other MediaTek firmware interfaces described in the device tree on those platforms. Is it okay if we just call it /firmware/watchdog in that case?
Powered by blists - more mailing lists