Turris Omnia MCU driver
Subsystems (7)
Marek Behún
maintainerv7 cover Turris Omnia MCU driver
Hello Andy, Hans, Ilpo, Arnd, Gregory, and others,
this is v7 of the series adding Turris Omnia MCU driver.
This series depends on the immutable branch between LEDs and locking, introducing devm_mutex_init(), see the PR
https://lore.kernel.org/linux-leds/[email protected]/
See also cover letters for v1, v2, v3, v4, v5 and v6:
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
Changes since v6:
- moved the DT binding from arm/cznic,turris-omnia-mcu.yaml to firmware/cznic,turris-omnia-mcu.yaml, as suggested by Conor Dooley (patch 1)
- dropped the devm-helpers.h additions, for the reasons see
https://lore.kernel.org/soc/20240423184346.37eb0915@thinkpad/
- use gpiod_to_irq(gpiochip_get_desc(...)) instead of irq_create_mapping(), as suggested by Andy Shevchenko (patches 6 and
7)
- added a dummy read of TRNG entropy when registering TRNG, in case someone cleared the TRNG interrupt before probing the driver, but did not read the entropy (the MCU won't send a new TRNG interrupt if the entropy is not collected) (patch 6)
- fixed a bug in TRNG probing, wherein if the
Marek Behún (9):
dt-bindings: arm: add cznic,turris-omnia-mcu binding
platform: cznic: Add preliminary support for Turris Omnia MCU
platform: cznic: turris-omnia-mcu: Add support for MCU connected GPIOs
platform: cznic: turris-omnia-mcu: Add support for poweroff and wakeup
platform: cznic: turris-omnia-mcu: Add support for MCU watchdog
platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
platform: cznic: turris-omnia-mcu: Add support for digital message
signing via debugfs
ARM: dts: turris-omnia: Add MCU system-controller node
ARM: dts: turris-omnia: Add GPIO key node for front button
.../ABI/testing/debugfs-turris-omnia-mcu | 13 + .../sysfs-bus-i2c-devices-turris-omnia-mcu | 126 ++ .../firmware/cznic,turris-omnia-mcu.yaml | 86 ++ MAINTAINERS | 5 + .../dts/marvell/armada-385-turris-omnia.dts | 35 +- drivers/platform/Kconfig | 2 + drivers/platform/Makefile | 1 + drivers/platform/cznic/Kconfig | 51 + drivers/platform/cznic/Makefile | 9 + .../platform/cznic/turris-omnia-mcu-base.c | 439 +++++++ .../platform/cznic/turris-omnia-mcu-debugfs.c | 216 ++++ .../platform/cznic/turris-omnia-mcu-gpio.c | 1047 +++++++++++++++++ .../cznic/turris-omnia-mcu-sys-off-wakeup.c | 258 ++++ .../platform/cznic/turris-omnia-mcu-trng.c | 109 ++ .../cznic/turris-omnia-mcu-watchdog.c | 123 ++ drivers/platform/cznic/turris-omnia-mcu.h | 188 +++ include/linux/turris-omnia-mcu-interface.h | 249 ++++ 17 files changed, 2956 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/debugfs-turris-omnia-mcu create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml create mode 100644 drivers/platform/cznic/Kconfig create mode 100644 drivers/platform/cznic/Makefile create mode 100644 drivers/platform/cznic/turris-omnia-mcu-base.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-debugfs.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-gpio.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-trng.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-watchdog.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu.h create mode 100644 include/linux/turris-omnia-mcu-interface.h
Signature · 1 line
2.43.2
Marek Behún
maintainerPATCH v7 1/9 dt-bindings: arm: add cznic,turris-omnia-mcu binding
Add binding for cznic,turris-omnia-mcu, the device-tree node representing the system-controller features provided by the MCU on the Turris Omnia router.
--- .../firmware/cznic,turris-omnia-mcu.yaml | 86 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml
Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml new file +86 -0
@@ -0,0 +1,86 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/arm/cznic,turris-omnia-mcu.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: CZ.NIC's Turris Omnia MCU + +maintainers: + - Marek Behún <[email protected]> + +description: + The MCU on Turris Omnia acts as a system controller providing additional + GPIOs, interrupts, watchdog, system power off and wakeup configuration. + +properties: + compatible: + const: cznic,turris-omnia-mcu + + reg: + description: MCU I2C slave address + maxItems: 1 + + interrupts: + maxItems: 1 + + interrupt-controller: true + + '#interrupt-cells': + const: 2 + description: | + The first cell specifies the interrupt number (0 to 63), the second cell + specifies interrupt type (which can be one of IRQ_TYPE_EDGE_RISING, + IRQ_TYPE_EDGE_FALLING or IRQ_TYPE_EDGE_BOTH). + The interrupt numbers correspond sequentially to GPIO numbers, taking the + GPIO banks into account: + IRQ number GPIO bank GPIO pin within bank + 0 - 15 0 0 - 15 + 16 - 47 1 0 - 31 + 48 - 63 2 0 - 15 + There are several exceptions: + IRQ number meaning + 11 LED panel brightness changed by button press + 13 TRNG entropy ready + 14 ECDSA message signature computation done + + gpio-controller: true + + '#gpio-cells': + const: 3 + description: + The first cell is bank number (0, 1 or 2), the second cell is pin number + within the bank (0 to 15 for banks 0 and 2, 0 to 31 for bank 1), and the + third cell specifies consumer flags. + +required: + - compatible + - reg + - interrupts + - interrupt-controller + - gpio-controller + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + + i2c { + #address-cells = <1>; + #size-cells = <0>; + + system-controller@2a { + compatible = "cznic,turris-omnia-mcu"; + reg = <0x2a>; + + interrupt-parent = <&gpio1>; + interrupts = <11 IRQ_TYPE_NONE>; + + gpio-controller; + #gpio-cells = <3>; + + interrupt-controller; + #interrupt-cells = <2>; + }; + };
MAINTAINERS +1 -0
@@ -2143,6 +2143,7 @@ F: Documentation/ABI/testing/sysfs-bus-moxtet-devices F: Documentation/ABI/testing/sysfs-firmware-turris-mox-rwtm F: Documentation/devicetree/bindings/bus/moxtet.txt F: Documentation/devicetree/bindings/firmware/cznic,turris-mox-rwtm.txt +F: Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml F: Documentation/devicetree/bindings/gpio/gpio-moxtet.txt F: Documentation/devicetree/bindings/leds/cznic,turris-omnia-leds.yaml F: Documentation/devicetree/bindings/watchdog/armada-37xx-wdt.txt
Signature · 1 line
2.43.2
Rob Herring
maintainerRe: [PATCH v7 1/9] dt-bindings: arm: add cznic,turris-omnia-mcu binding
Quoted 4 lines · Marek Behún
Add binding for cznic,turris-omnia-mcu, the device-tree node representing the system-controller features provided by the MCU on the Turris Omnia router.
Quoted 8 lines
Signed-off-by Marek Behún <[email protected]>Reviewed-by Krzysztof Kozlowski <[email protected]>--- .../firmware/cznic,turris-omnia-mcu.yaml | 86 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename
$id: http://devicetree.org/schemas/arm/cznic,turris-omnia-mcu.yaml
file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
Marek Behún
maintainerRe: [PATCH v7 1/9] dt-bindings: arm: add cznic,turris-omnia-mcu binding
Quoted 34 lines · On Wed, 24 Apr 2024 13:16:18 -0500 Rob Herring <[email protected]> wrote:
Quoted 4 lines · Marek Behún
Add binding for cznic,turris-omnia-mcu, the device-tree node representing the system-controller features provided by the MCU on the Turris Omnia router.
Quoted 8 lines
Signed-off-by Marek Behún <[email protected]>Reviewed-by Krzysztof Kozlowski <[email protected]>--- .../firmware/cznic,turris-omnia-mcu.yaml | 86 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yamlMy bot found errors running 'make
dt_binding_check' on your patch:yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename(quoted diff) +0
-0$id: http://devicetree.org/schemas/arm/cznic,turris-omnia-mcu.yaml file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yamldoc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch.
If you already ran 'make
dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date:
Quoted 6 lines
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note that
DT_SCHEMA_FILEScan be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
Sigh. I moved the patch bud did not change it in $id...
Conor Dooley
Reviewed-byRe: [PATCH v7 1/9] dt-bindings: arm: add cznic,turris-omnia-mcu binding
Quoted 37 lines · Marek Behún
Quoted 34 lines · On Wed, 24 Apr 2024 13:16:18 -0500 Rob Herring <[email protected]> wrote:
Quoted 4 lines · Marek Behún
Add binding for cznic,turris-omnia-mcu, the device-tree node representing the system-controller features provided by the MCU on the Turris Omnia router.
Quoted 8 lines
Signed-off-by Marek Behún <[email protected]>Reviewed-by Krzysztof Kozlowski <[email protected]>--- .../firmware/cznic,turris-omnia-mcu.yaml | 86 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 87 insertions(+) create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yamlMy bot found errors running 'make
dt_binding_check' on your patch:yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename(quoted diff) +0
-0$id: http://devicetree.org/schemas/arm/cznic,turris-omnia-mcu.yaml file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yamldoc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/[email protected]
The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch.
If you already ran 'make
dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date:
Quoted 8 lines
Quoted 6 lines
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note that
DT_SCHEMA_FILEScan be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.Sigh. I moved the patch bud did not change it in $id...
A bit needless, given you've got a tag from Krzysztof, but with that fixed
Cheers,
Conor.
Marek Behún
maintainerPATCH v7 2/9 platform: cznic: Add preliminary support for Turris Omnia MCU
In reply to Marek BehúnAdd the basic skeleton for a new platform driver for the microcontroller found on the Turris Omnia board.
--- .../sysfs-bus-i2c-devices-turris-omnia-mcu | 81 ++++ MAINTAINERS | 3 + drivers/platform/Kconfig | 2 + drivers/platform/Makefile | 1 + drivers/platform/cznic/Kconfig | 26 ++ drivers/platform/cznic/Makefile | 4 + .../platform/cznic/turris-omnia-mcu-base.c | 376 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 50 +++ include/linux/turris-omnia-mcu-interface.h | 249 ++++++++++++ 9 files changed, 792 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu create mode 100644 drivers/platform/cznic/Kconfig create mode 100644 drivers/platform/cznic/Makefile create mode 100644 drivers/platform/cznic/turris-omnia-mcu-base.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu.h create mode 100644 include/linux/turris-omnia-mcu-interface.h
Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu new file +81 -0
@@ -0,0 +1,81 @@ +What: /sys/bus/i2c/devices/<mcu_device>/board_revision +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains board revision number. + + Only available if board information is burned in the MCU (older + revisions have board information burned in the ATSHA204-A chip). + + Format: %u. + +What: /sys/bus/i2c/devices/<mcu_device>/first_mac_address +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains device first MAC address. Each Turris Omnia is + allocated 3 MAC addresses. The two additional addresses are + computed from the first one by incrementing it. + + Only available if board information is burned in the MCU (older + revisions have board information burned in the ATSHA204-A chip). + + Format: %pM. + +What: /sys/bus/i2c/devices/<mcu_device>/fw_features +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Newer versions of the microcontroller firmware report the + features they support. These can be read from this file. If the + MCU firmware is too old, this file reads 0x0. + + Format: 0x%x. + +What: /sys/bus/i2c/devices/<mcu_device>/fw_version_hash_application +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains the version hash (commit hash) of the application + part of the microcontroller firmware. + + Format: %s. + +What: /sys/bus/i2c/devices/<mcu_device>/fw_version_hash_bootloader +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains the version hash (commit hash) of the bootloader + part of the microcontroller firmware. + + Format: %s. + +What: /sys/bus/i2c/devices/<mcu_device>/mcu_type +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains the microcontroller type (STM32, GD32, MKL). + + Format: %s. + +What: /sys/bus/i2c/devices/<mcu_device>/reset_selector +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains the selected factory reset level, determined by + how long the rear reset button was held by the user during board + reset. + + Format: %i. + +What: /sys/bus/i2c/devices/<mcu_device>/serial_number +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains the 64 bit long board serial number in hexadecimal + format. + + Only available if board information is burned in the MCU (older + revisions have board information burned in the ATSHA204-A chip). + + Format: %016X.
MAINTAINERS +3 -0
@@ -2139,6 +2139,7 @@ M: Marek Behún <[email protected]> S: Maintained W: https://www.turris.cz/ F: Documentation/ABI/testing/debugfs-moxtet +F: Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu F: Documentation/ABI/testing/sysfs-bus-moxtet-devices F: Documentation/ABI/testing/sysfs-firmware-turris-mox-rwtm F: Documentation/devicetree/bindings/bus/moxtet.txt
@@ -2152,10 +2153,12 @@ F: drivers/firmware/turris-mox-rwtm.c F: drivers/gpio/gpio-moxtet.c F: drivers/leds/leds-turris-omnia.c F: drivers/mailbox/armada-37xx-rwtm-mailbox.c +F: drivers/platform/cznic/ F: drivers/watchdog/armada_37xx_wdt.c F: include/dt-bindings/bus/moxtet.h F: include/linux/armada-37xx-rwtm-mailbox.h F: include/linux/moxtet.h +F: include/linux/turris-omnia-mcu-interface.h ARM/FARADAY FA526 PORT M: Hans Ulli Kroll <[email protected]>
drivers/platform/Kconfig +2 -0
@@ -7,6 +7,8 @@ source "drivers/platform/goldfish/Kconfig" source "drivers/platform/chrome/Kconfig" +source "drivers/platform/cznic/Kconfig" + source "drivers/platform/mellanox/Kconfig" source "drivers/platform/olpc/Kconfig"
drivers/platform/Makefile +1 -0
@@ -10,4 +10,5 @@ obj-$(CONFIG_MIPS) += mips/ obj-$(CONFIG_OLPC_EC) += olpc/ obj-$(CONFIG_GOLDFISH) += goldfish/ obj-$(CONFIG_CHROME_PLATFORMS) += chrome/ +obj-$(CONFIG_CZNIC_PLATFORMS) += cznic/ obj-$(CONFIG_SURFACE_PLATFORMS) += surface/
drivers/platform/cznic/Kconfig new file +26 -0
@@ -0,0 +1,26 @@ +# SPDX-License-Identifier: GPL-2.0-only +# +# For a description of the syntax of this configuration file, +# see Documentation/kbuild/kconfig-language.rst. +# + +menuconfig CZNIC_PLATFORMS + bool "Platform support for CZ.NIC's Turris hardware" + depends on MACH_ARMADA_38X || COMPILE_TEST + help + Say Y here to be able to choose driver support for CZ.NIC's Turris + devices. This option alone does not add any kernel code. + +if CZNIC_PLATFORMS + +config TURRIS_OMNIA_MCU + tristate "Turris Omnia MCU driver" + depends on MACH_ARMADA_38X || COMPILE_TEST + depends on I2C + help + Say Y here to add support for the features implemented by the + microcontroller on the CZ.NIC's Turris Omnia SOHO router. + To compile this driver as a module, choose M here; the module will be + called turris-omnia-mcu. + +endif # CZNIC_PLATFORMS
drivers/platform/cznic/Makefile new file +4 -0
@@ -0,0 +1,4 @@ +# SPDX-License-Identifier: GPL-2.0-only + +obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o +turris-omnia-mcu-y := turris-omnia-mcu-base.o
drivers/platform/cznic/turris-omnia-mcu-base.c new file +376 -0
376 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h new file +50 -0
50 lines not on this page · raw message
include/linux/turris-omnia-mcu-interface.h new file +249 -0
249 lines not on this page · raw message
Signature · 1 line
2.43.2
Marek Behún
maintainerPATCH v7 3/9 platform: cznic: turris-omnia-mcu: Add support for MCU connected GPIOs
In reply to Marek BehúnAdd support for GPIOs connected to the MCU on the Turris Omnia board.
This includes:
- front button pin
- enable pins for USB regulators
- MiniPCIe / mSATA card presence pins in MiniPCIe port 0
- LED output pins from WAN ethernet PHY, LAN switch and MiniPCIe ports
- on board revisions 32+ also various peripheral resets and another voltage regulator enable pin
--- .../sysfs-bus-i2c-devices-turris-omnia-mcu | 16 + drivers/platform/cznic/Kconfig | 15 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 33 +- .../platform/cznic/turris-omnia-mcu-gpio.c | 1047 +++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 69 +- 6 files changed, 1165 insertions(+), 16 deletions(-) create mode 100644 drivers/platform/cznic/turris-omnia-mcu-gpio.c
Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu +16 -0
@@ -22,6 +22,22 @@ Description: (RO) Contains device first MAC address. Each Turris Omnia is Format: %pM. +What: /sys/bus/i2c/devices/<mcu_device>/front_button_mode +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RW) The front button on the Turris Omnia router can be + configured either to change the intensity of all the LEDs on the + front panel, or to send the press event to the CPU as an + interrupt. + + This file switches between these two modes: + - "mcu" makes the button press event be handled by the MCU to + change the LEDs panel intensity. + - "cpu" makes the button press event be handled by the CPU. + + Format: %s. + What: /sys/bus/i2c/devices/<mcu_device>/fw_features Date: July 2024 KernelVersion: 6.10
drivers/platform/cznic/Kconfig +15 -0
@@ -17,9 +17,24 @@ config TURRIS_OMNIA_MCU tristate "Turris Omnia MCU driver" depends on MACH_ARMADA_38X || COMPILE_TEST depends on I2C + select GPIOLIB + select GPIOLIB_IRQCHIP help Say Y here to add support for the features implemented by the microcontroller on the CZ.NIC's Turris Omnia SOHO router. + The features include: + - GPIO pins + - to get front button press events (the front button can be + configured either to generate press events to the CPU or to change + front LEDs panel brightness) + - to enable / disable USB port voltage regulators and to detect + USB overcurrent + - to detect MiniPCIe / mSATA card presence in MiniPCIe port 0 + - to configure resets of various peripherals on board revisions 32+ + - to enable / disable the VHV voltage regulator to the SOC in order + to be able to program SOC's OTP on board revisions 32+ + - to get input from the LED output pins of the WAN ethernet PHY, LAN + switch and MiniPCIe ports To compile this driver as a module, choose M here; the module will be called turris-omnia-mcu.
drivers/platform/cznic/Makefile +1 -0
@@ -2,3 +2,4 @@ obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o turris-omnia-mcu-y := turris-omnia-mcu-base.o +turris-omnia-mcu-y += turris-omnia-mcu-gpio.o
drivers/platform/cznic/turris-omnia-mcu-base.c +20 -13
@@ -22,25 +22,31 @@#define OMNIA_FW_VERSION_HEX_LEN (2 * OMNIA_FW_VERSION_LEN + 1)#define OMNIA_BOARD_INFO_LEN 16 -int omnia_cmd_read (const struct i2c_client *client,u8 cmd,void *reply, -unsigned int len) +int omnia_cmd_write_read (const struct i2c_client *client, +void *cmd,unsigned int cmd_len, +void *reply,unsigned int reply_len) {struct i2c_msg msgs[2 ]; -int ret; +int ret, num; msgs[0 ].addr = client->addr; msgs[0 ].flags =0 ; - msgs[0 ].len =1 ; - msgs[0 ].buf = &cmd; - msgs[1 ].addr = client->addr; - msgs[1 ].flags =I2C_M_RD ; - msgs[1 ].len = len; - msgs[1 ].buf = reply; - - ret =i2c_transfer (client->adapter, msgs,ARRAY_SIZE (msgs)); + msgs[0 ].len = cmd_len; + msgs[0 ].buf = cmd; + num =1 ; + +if (reply_len) { + msgs[1 ].addr = client->addr; + msgs[1 ].flags =I2C_M_RD ; + msgs[1 ].len = reply_len; + msgs[1 ].buf = reply; + num++; + } + + ret =i2c_transfer (client->adapter, msgs, num);if (ret <0 )return ret; -if (ret !=ARRAY_SIZE (msgs)) +if (ret != num)return -EIO ;return 0 ;
@@ -188,6 +194,7 @@ static const struct attribute_group omnia_mcu_base_group = {static const struct attribute_group *omnia_mcu_groups[] = { &omnia_mcu_base_group, + &omnia_mcu_gpio_group,NULL };
@@ -353,7 +360,7 @@ static int omnia_mcu_probe(struct i2c_client *client) "Cannot read board info\n"); } -return 0 ; +return omnia_mcu_register_gpiochip (mcu); }static const struct of_device_id of_omnia_mcu_match[] = {
drivers/platform/cznic/turris-omnia-mcu-gpio.c new file +1047 -0
1,047 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h +66 -3
89 lines not on this page · raw message
Signature · 1 line
2.43.2
Marek Behún
maintainerPATCH v7 4/9 platform: cznic: turris-omnia-mcu: Add support for poweroff and wakeup
In reply to Marek BehúnAdd support for true board poweroff (MCU can disable all unnecessary voltage regulators) and wakeup at a specified time, implemented via a RTC driver so that the rtcwake utility can be used to configure it.
--- .../sysfs-bus-i2c-devices-turris-omnia-mcu | 16 ++ drivers/platform/cznic/Kconfig | 4 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 5 + .../cznic/turris-omnia-mcu-sys-off-wakeup.c | 258 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 20 ++ 6 files changed, 304 insertions(+) create mode 100644 drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.c
Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu +16 -0
@@ -38,6 +38,22 @@ Description: (RW) The front button on the Turris Omnia router can be Format: %s. +What: /sys/bus/i2c/devices/<mcu_device>/front_button_poweron +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RW) Newer versions of the microcontroller firmware of the + Turris Omnia router support powering off the router into true + low power mode. The router can be powered on by pressing the + front button. + + This file configures whether front button power on is enabled. + + This file is present only if the power off feature is supported + by the firmware. + + Format: %i. + What: /sys/bus/i2c/devices/<mcu_device>/fw_features Date: July 2024 KernelVersion: 6.10
drivers/platform/cznic/Kconfig +4 -0
@@ -19,10 +19,14 @@ config TURRIS_OMNIA_MCU depends on I2C select GPIOLIB select GPIOLIB_IRQCHIP + select RTC_CLASS help Say Y here to add support for the features implemented by the microcontroller on the CZ.NIC's Turris Omnia SOHO router. The features include: + - board poweroff into true low power mode (with voltage regulators + disabled) and the ability to configure wake up from this mode (via + rtcwake) - GPIO pins - to get front button press events (the front button can be configured either to generate press events to the CPU or to change
drivers/platform/cznic/Makefile +1 -0
@@ -3,3 +3,4 @@ obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o turris-omnia-mcu-y := turris-omnia-mcu-base.o turris-omnia-mcu-y += turris-omnia-mcu-gpio.o +turris-omnia-mcu-y += turris-omnia-mcu-sys-off-wakeup.o
drivers/platform/cznic/turris-omnia-mcu-base.c +5 -0
@@ -195,6 +195,7 @@ static const struct attribute_group omnia_mcu_base_group = {static const struct attribute_group *omnia_mcu_groups[] = { &omnia_mcu_base_group, &omnia_mcu_gpio_group, + &omnia_mcu_poweroff_group,NULL };
@@ -360,6 +361,10 @@ static int omnia_mcu_probe(struct i2c_client *client) "Cannot read board info\n"); } + err =omnia_mcu_register_sys_off_and_wakeup (mcu); +if (err) +return err; +return omnia_mcu_register_gpiochip (mcu); }
drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.c new file +258 -0
258 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h +20 -0
@@ -12,9 +12,11 @@#include <linux/gpio/driver.h> #include <linux/if_ether.h> #include <linux/mutex.h> +#include <linux/rtc.h> #include <linux/types.h> #include <linux/workqueue.h> #include <asm/byteorder.h> +#include <asm/unaligned.h> struct omnia_mcu {struct i2c_client *client;
@@ -34,6 +36,11 @@ struct omnia_mcu {struct delayed_work button_release_emul_work;u16 last_status;bool button_pressed_emul; + +/* RTC device for configuring wake-up */ +struct rtc_device *rtcdev; +u32 rtc_alarm; +bool front_button_poweron; }; int omnia_cmd_write_read(const struct i2c_client *client,
@@ -46,6 +53,17 @@ static inline int omnia_cmd_write(const struct i2c_client *client, void *cmd,return omnia_cmd_write_read (client, cmd, len,NULL ,0 ); } +static inline int omnia_cmd_write_u32 (const struct i2c_client *client,u8 cmd, +u32 val) +{ +u8 buf[5 ]; + + buf[0 ] = cmd; +put_unaligned_le32 (val, &buf[1 ]); + +return omnia_cmd_write (client, buf,sizeof (buf)); +} +static inline int omnia_cmd_read (const struct i2c_client *client,u8 cmd,void *reply,unsigned int len) {
@@ -107,7 +125,9 @@ static inline int omnia_cmd_read_u8(const struct i2c_client *client, u8 cmd) }extern const struct attribute_group omnia_mcu_gpio_group; +extern const struct attribute_group omnia_mcu_poweroff_group;int omnia_mcu_register_gpiochip (struct omnia_mcu *mcu); +int omnia_mcu_register_sys_off_and_wakeup (struct omnia_mcu *mcu);#endif /* __TURRIS_OMNIA_MCU_H */
Signature · 1 line
2.43.2
Re: [PATCH v7 4/9] platform: cznic: turris-omnia-mcu: Add support for poweroff and wakeup
Quoted 5 lines · Marek Behún
Add support for true board poweroff (MCU can disable all unnecessary voltage regulators) and wakeup at a specified time, implemented via a RTC driver so that the rtcwake utility can be used to configure it.
Signed-off-by Marek Behún <[email protected]>
Quoted 412 lines
--- .../sysfs-bus-i2c-devices-turris-omnia-mcu | 16 ++ drivers/platform/cznic/Kconfig | 4 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 5 + .../cznic/turris-omnia-mcu-sys-off-wakeup.c | 258 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 20 ++ 6 files changed, 304 insertions(+) create mode 100644 drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.cDocumentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu +16
-0@@ -38,6 +38,22 @@ Description: (RW) The front button on the Turris Omnia router can be Format: %s. +What: /sys/bus/i2c/devices/<mcu_device>/front_button_poweron +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RW) Newer versions of the microcontroller firmware of the + Turris Omnia router support powering off the router into true + low power mode. The router can be powered on by pressing the + front button. + + This file configures whether front button power on is enabled. + + This file is present only if the power off feature is supported + by the firmware. + + Format: %i. + What: /sys/bus/i2c/devices/<mcu_device>/fw_features Date: July 2024 KernelVersion: 6.10drivers/platform/cznic/Kconfig +4
-0@@ -19,10 +19,14 @@ config TURRIS_OMNIA_MCU depends on I2C select GPIOLIB select GPIOLIB_IRQCHIP + select RTC_CLASS help Say Y here to add support for the features implemented by the microcontroller on the CZ.NIC's Turris Omnia SOHO router. The features include: + - board poweroff into true low power mode (with voltage regulators + disabled) and the ability to configure wake up from this mode (via + rtcwake) - GPIO pins - to get front button press events (the front button can be configured either to generate press events to the CPU or to changedrivers/platform/cznic/Makefile +1
-0@@ -3,3 +3,4 @@ obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o turris-omnia-mcu-y := turris-omnia-mcu-base.o turris-omnia-mcu-y += turris-omnia-mcu-gpio.o +turris-omnia-mcu-y += turris-omnia-mcu-sys-off-wakeup.odrivers/platform/cznic/turris-omnia-mcu-base.c +5
-0@@ -195,6 +195,7 @@ static const struct attribute_group omnia_mcu_base_group = {static const struct attribute_group *omnia_mcu_groups[] = { &omnia_mcu_base_group, &omnia_mcu_gpio_group, + &omnia_mcu_poweroff_group,NULL };@@ -360,6 +361,10 @@ static int omnia_mcu_probe(struct i2c_client *client) "Cannot read board info\n"); } + err =omnia_mcu_register_sys_off_and_wakeup (mcu); +if (err) +return err; +return omnia_mcu_register_gpiochip (mcu); }drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.c new file +258
-0@@ -0,0 +1,258 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* CZ.NIC's Turris Omnia MCU system off and RTC wakeup driver +* +* This is not a true RTC driver (in the sense that it does not provide a +* real-time clock), rather the MCU implements a wakeup from powered off state +* at a specified time relative to MCU boot, and we expose this feature via RTC +* alarm, so that it can be used via the rtcwake command, which is the standard +* Linux command for this. +* +* 2024 by Marek Behún <[email protected]> +*/ + +#include <linux/crc32.h> +#include <linux/delay.h> +#include <linux/i2c.h> +#include <linux/reboot.h> +#include <linux/rtc.h> +#include <linux/sysfs.h> +#include <linux/turris-omnia-mcu-interface.h> +#include <linux/types.h> + +#include "turris-omnia-mcu.h" + +static int omnia_get_uptime_wakeup (const struct i2c_client *client,u32 *uptime, +u32 *wakeup) +{ +__le32 reply[2 ]; +int err; + + err =omnia_cmd_read (client,CMD_GET_UPTIME_AND_WAKEUP , reply, +sizeof (reply)); +if (err) +return err; + +if (uptime) + *uptime =le32_to_cpu (reply[0 ]); + +if (wakeup) + *wakeup =le32_to_cpu (reply[1 ]); + +return 0 ; +} + +static int omnia_read_time (struct device *dev,struct rtc_time *tm) +{ +u32 uptime; +int err; + + err =omnia_get_uptime_wakeup (to_i2c_client (dev), &uptime,NULL ); +if (err) +return err; + +rtc_time64_to_tm (uptime, tm); + +return 0 ; +} + +static int omnia_read_alarm (struct device *dev,struct rtc_wkalrm *alrm) +{ +struct i2c_client *client =to_i2c_client (dev); +struct omnia_mcu *mcu =i2c_get_clientdata (client); +u32 wakeup; +int err; + + err =omnia_get_uptime_wakeup (client,NULL , &wakeup); +if (err) +return err; + + alrm->enabled = !!wakeup; +rtc_time64_to_tm (wakeup ?: mcu->rtc_alarm, &alrm->time); + +return 0 ; +} + +static int omnia_set_alarm (struct device *dev,struct rtc_wkalrm *alrm) +{ +struct i2c_client *client =to_i2c_client (dev); +struct omnia_mcu *mcu =i2c_get_clientdata (client); + + mcu->rtc_alarm =rtc_tm_to_time64 (&alrm->time); + +if (alrm->enabled) +return omnia_cmd_write_u32 (client,CMD_SET_WAKEUP , + mcu->rtc_alarm); + +return 0 ; +} + +static int omnia_alarm_irq_enable (struct device *dev,unsigned int enabled) +{ +struct i2c_client *client =to_i2c_client (dev); +struct omnia_mcu *mcu =i2c_get_clientdata (client); + +return omnia_cmd_write_u32 (client,CMD_SET_WAKEUP , + enabled ? mcu->rtc_alarm :0 ); +} + +static const struct rtc_class_ops omnia_rtc_ops = { + .read_time = omnia_read_time, + .read_alarm = omnia_read_alarm, + .set_alarm = omnia_set_alarm, + .alarm_irq_enable = omnia_alarm_irq_enable, +}; + +static int omnia_power_off (struct sys_off_data *data) +{ +struct omnia_mcu *mcu = data->cb_data; +__be32 tmp; +u8 cmd[9 ]; +u16 arg; +int err; + +if (mcu->front_button_poweron) + arg =CMD_POWER_OFF_POWERON_BUTTON ; +else + arg =0 ; + + cmd[0 ] =CMD_POWER_OFF ; +put_unaligned_le16 (CMD_POWER_OFF_MAGIC , &cmd[1 ]); +put_unaligned_le16 (arg, &cmd[3 ]); + +/* +* Although all values from and to MCU are passed in little-endian, the +* MCU's CRC unit uses big-endian CRC32 polynomial (0x04c11db7), so we +* need to use crc32_be() here. +*/ + tmp =cpu_to_be32 (get_unaligned_le32 (&cmd[1 ])); +put_unaligned_le32 (crc32_be (0xffffffff , (void *)&tmp,sizeof (tmp)), + &cmd[5 ]); + + err =omnia_cmd_write (mcu->client, cmd,sizeof (cmd)); +if (err) +dev_err (&mcu->client->dev, +"Unable to send the poweroff command: %d\n" , err); + +return NOTIFY_DONE ; +} + +static int omnia_restart (struct sys_off_data *data) +{ +struct omnia_mcu *mcu = data->cb_data; +u8 cmd[3 ]; +int err; + + cmd[0 ] =CMD_GENERAL_CONTROL ; + +if (reboot_mode ==REBOOT_HARD ) + cmd[1 ] = cmd[2 ] =CTL_HARD_RST ; +else + cmd[1 ] = cmd[2 ] =CTL_LIGHT_RST ; + + err =omnia_cmd_write (mcu->client, cmd,sizeof (cmd)); +if (err) +dev_err (&mcu->client->dev, +"Unable to send the restart command: %d\n" , err); + +/* +* MCU needs a little bit to process the I2C command, otherwise it will +* do a light reset based on SOC SYSRES_OUT pin. +*/ +mdelay (1 ); + +return NOTIFY_DONE ; +} + +static ssize_t front_button_poweron_show (struct device *dev, +struct device_attribute *a,char *buf) +{ +struct omnia_mcu *mcu =dev_get_drvdata (dev); + +return sysfs_emit (buf,"%d\n" , mcu->front_button_poweron); +} + +static ssize_t front_button_poweron_store (struct device *dev, +struct device_attribute *a, +const char *buf,size_t count) +{ +struct omnia_mcu *mcu =dev_get_drvdata (dev); +bool val; +int err; + + err =kstrtobool (buf, &val); +if (err) +return err; + + mcu->front_button_poweron = val; + +return count; +} +static DEVICE_ATTR_RW (front_button_poweron); + +static struct attribute *omnia_mcu_poweroff_attrs[] = { + &dev_attr_front_button_poweron.attr, +NULL +}; + +static umode_t poweroff_attrs_visible (struct kobject *kobj,struct attribute *a, +int n) +{ +struct device *dev =kobj_to_dev (kobj); +struct omnia_mcu *mcu =dev_get_drvdata (dev); + +if (mcu->features &FEAT_POWEROFF_WAKEUP ) +return a->mode; + +return 0 ; +} + +const struct attribute_group omnia_mcu_poweroff_group = { + .attrs = omnia_mcu_poweroff_attrs, + .is_visible = poweroff_attrs_visible, +}; + +int omnia_mcu_register_sys_off_and_wakeup (struct omnia_mcu *mcu) +{ +struct device *dev = &mcu->client->dev; +int err; + +/* MCU restart is always available */ + err =devm_register_sys_off_handler (dev,SYS_OFF_MODE_RESTART , +SYS_OFF_PRIO_FIRMWARE , + omnia_restart, mcu); +if (err) +return dev_err_probe (dev, err, +"Cannot register system restart handler\n" ); + +/* +* Poweroff and wakeup are available only if POWEROFF_WAKEUP feature is +* present. +*/ +if (!(mcu->features &FEAT_POWEROFF_WAKEUP )) +return 0 ; + + err =devm_register_sys_off_handler (dev,SYS_OFF_MODE_POWER_OFF , +SYS_OFF_PRIO_FIRMWARE , + omnia_power_off, mcu); +if (err) +return dev_err_probe (dev, err, +"Cannot register system power off handler\n" ); + + mcu->rtcdev =devm_rtc_allocate_device (dev); +if (IS_ERR (mcu->rtcdev)) +return dev_err_probe (dev,PTR_ERR (mcu->rtcdev), +"Cannot allocate RTC device\n" ); + + mcu->rtcdev->ops = &omnia_rtc_ops; + mcu->rtcdev->range_max =U32_MAX ; +set_bit (RTC_FEATURE_ALARM_WAKEUP_ONLY , mcu->rtcdev->features); + + err =devm_rtc_register_device (mcu->rtcdev); +if (err) +return dev_err_probe (dev, err,"Cannot register RTC device\n" ); + + mcu->front_button_poweron = true; + +return 0 ; +}drivers/platform/cznic/turris-omnia-mcu.h +20
-0@@ -12,9 +12,11 @@#include <linux/gpio/driver.h> #include <linux/if_ether.h> #include <linux/mutex.h> +#include <linux/rtc.h> #include <linux/types.h> #include <linux/workqueue.h> #include <asm/byteorder.h> +#include <asm/unaligned.h> struct omnia_mcu {struct i2c_client *client;@@ -34,6 +36,11 @@ struct omnia_mcu {struct delayed_work button_release_emul_work;u16 last_status;bool button_pressed_emul; + +/* RTC device for configuring wake-up */ +struct rtc_device *rtcdev; +u32 rtc_alarm; +bool front_button_poweron; }; int omnia_cmd_write_read(const struct i2c_client *client,@@ -46,6 +53,17 @@ static inline int omnia_cmd_write(const struct i2c_client *client, void *cmd,return omnia_cmd_write_read (client, cmd, len,NULL ,0 ); } +static inline int omnia_cmd_write_u32 (const struct i2c_client *client,u8 cmd, +u32 val) +{ +u8 buf[5 ]; + + buf[0 ] = cmd; +put_unaligned_le32 (val, &buf[1 ]); + +return omnia_cmd_write (client, buf,sizeof (buf)); +} +static inline int omnia_cmd_read (const struct i2c_client *client,u8 cmd,void *reply,unsigned int len) {@@ -107,7 +125,9 @@ static inline int omnia_cmd_read_u8(const struct i2c_client *client, u8 cmd) }extern const struct attribute_group omnia_mcu_gpio_group; +extern const struct attribute_group omnia_mcu_poweroff_group;int omnia_mcu_register_gpiochip (struct omnia_mcu *mcu); +int omnia_mcu_register_sys_off_and_wakeup (struct omnia_mcu *mcu);#endif /* __TURRIS_OMNIA_MCU_H */ Signature · 1 line
2.43.2
Signature · 3 lines
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Marek Behún
maintainerPATCH v7 5/9 platform: cznic: turris-omnia-mcu: Add support for MCU watchdog
In reply to Marek BehúnAdd support for the watchdog mechanism provided by the MCU.
--- drivers/platform/cznic/Kconfig | 2 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 4 + .../cznic/turris-omnia-mcu-watchdog.c | 123 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 24 ++++ 5 files changed, 154 insertions(+) create mode 100644 drivers/platform/cznic/turris-omnia-mcu-watchdog.c
drivers/platform/cznic/Kconfig +2 -0
@@ -20,6 +20,7 @@ config TURRIS_OMNIA_MCU select GPIOLIB select GPIOLIB_IRQCHIP select RTC_CLASS + select WATCHDOG_CORE help Say Y here to add support for the features implemented by the microcontroller on the CZ.NIC's Turris Omnia SOHO router.
@@ -27,6 +28,7 @@ config TURRIS_OMNIA_MCU - board poweroff into true low power mode (with voltage regulators disabled) and the ability to configure wake up from this mode (via rtcwake) + - MCU watchdog - GPIO pins - to get front button press events (the front button can be configured either to generate press events to the CPU or to change
drivers/platform/cznic/Makefile +1 -0
@@ -4,3 +4,4 @@ obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o turris-omnia-mcu-y := turris-omnia-mcu-base.o turris-omnia-mcu-y += turris-omnia-mcu-gpio.o turris-omnia-mcu-y += turris-omnia-mcu-sys-off-wakeup.o +turris-omnia-mcu-y += turris-omnia-mcu-watchdog.o
drivers/platform/cznic/turris-omnia-mcu-base.c +4 -0
@@ -365,6 +365,10 @@ static int omnia_mcu_probe(struct i2c_client *client)if (err)return err; + err =omnia_mcu_register_watchdog (mcu); +if (err) +return err; +return omnia_mcu_register_gpiochip (mcu); }
drivers/platform/cznic/turris-omnia-mcu-watchdog.c new file +123 -0
123 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h +24 -0
@@ -14,6 +14,7 @@#include <linux/mutex.h> #include <linux/rtc.h> #include <linux/types.h> +#include <linux/watchdog.h> #include <linux/workqueue.h> #include <asm/byteorder.h> #include <asm/unaligned.h>
@@ -41,6 +42,9 @@ struct omnia_mcu {struct rtc_device *rtcdev;u32 rtc_alarm;bool front_button_poweron; + +/* MCU watchdog */ +struct watchdog_device wdt; }; int omnia_cmd_write_read(const struct i2c_client *client,
@@ -53,6 +57,25 @@ static inline int omnia_cmd_write(const struct i2c_client *client, void *cmd,return omnia_cmd_write_read (client, cmd, len,NULL ,0 ); } +static inline int omnia_cmd_write_u8 (const struct i2c_client *client,u8 cmd, +u8 val) +{ +u8 buf[2 ] = { cmd, val }; + +return omnia_cmd_write (client, buf,sizeof (buf)); +} + +static inline int omnia_cmd_write_u16 (const struct i2c_client *client,u8 cmd, +u16 val) +{ +u8 buf[3 ]; + + buf[0 ] = cmd; +put_unaligned_le16 (val, &buf[1 ]); + +return omnia_cmd_write (client, buf,sizeof (buf)); +} +static inline int omnia_cmd_write_u32 (const struct i2c_client *client,u8 cmd,u32 val) {
@@ -129,5 +152,6 @@ extern const struct attribute_group omnia_mcu_poweroff_group;int omnia_mcu_register_gpiochip (struct omnia_mcu *mcu);int omnia_mcu_register_sys_off_and_wakeup (struct omnia_mcu *mcu); +int omnia_mcu_register_watchdog (struct omnia_mcu *mcu);#endif /* __TURRIS_OMNIA_MCU_H */
Signature · 1 line
2.43.2
Marek Behún
maintainerPATCH v7 6/9 platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
In reply to Marek BehúnAdd support for true random number generator provided by the MCU. New Omnia boards come without the Atmel SHA204-A chip. Instead the crypto functionality is provided by new microcontroller, which has a TRNG peripheral.
--- drivers/platform/cznic/Kconfig | 2 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 6 +- .../platform/cznic/turris-omnia-mcu-gpio.c | 2 +- .../platform/cznic/turris-omnia-mcu-trng.c | 109 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 8 ++ 6 files changed, 126 insertions(+), 2 deletions(-) create mode 100644 drivers/platform/cznic/turris-omnia-mcu-trng.c
drivers/platform/cznic/Kconfig +2 -0
@@ -19,6 +19,7 @@ config TURRIS_OMNIA_MCU depends on I2C select GPIOLIB select GPIOLIB_IRQCHIP + select HW_RANDOM select RTC_CLASS select WATCHDOG_CORE help
@@ -28,6 +29,7 @@ config TURRIS_OMNIA_MCU - board poweroff into true low power mode (with voltage regulators disabled) and the ability to configure wake up from this mode (via rtcwake) + - true random number generator (if available on the MCU) - MCU watchdog - GPIO pins - to get front button press events (the front button can be
drivers/platform/cznic/Makefile +1 -0
@@ -4,4 +4,5 @@ obj-$(CONFIG_TURRIS_OMNIA_MCU) += turris-omnia-mcu.o turris-omnia-mcu-y := turris-omnia-mcu-base.o turris-omnia-mcu-y += turris-omnia-mcu-gpio.o turris-omnia-mcu-y += turris-omnia-mcu-sys-off-wakeup.o +turris-omnia-mcu-y += turris-omnia-mcu-trng.o turris-omnia-mcu-y += turris-omnia-mcu-watchdog.o
drivers/platform/cznic/turris-omnia-mcu-base.c +5 -1
@@ -369,7 +369,11 @@ static int omnia_mcu_probe(struct i2c_client *client)if (err)return err; -return omnia_mcu_register_gpiochip (mcu); + err =omnia_mcu_register_gpiochip (mcu); +if (err) +return err; + +return omnia_mcu_register_trng (mcu); }static const struct of_device_id of_omnia_mcu_match[] = {
drivers/platform/cznic/turris-omnia-mcu-gpio.c +1 -1
@@ -162,7 +162,7 @@ static const struct omnia_gpio { };/* mapping from interrupts to indexes of GPIOs in the omnia_gpios array */ -static const u8 omnia_int_to_gpio_idx[32 ] = { +const u8 omnia_int_to_gpio_idx[32 ] = { [__bf_shf (INT_CARD_DET )] =4 , [__bf_shf (INT_MSATA_IND )] =5 , [__bf_shf (INT_USB30_OVC )] =6 ,
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +109 -0
109 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h +8 -0
@@ -9,7 +9,9 @@#define __TURRIS_OMNIA_MCU_H#include <linux/bitops.h> +#include <linux/completion.h> #include <linux/gpio/driver.h> +#include <linux/hw_random.h> #include <linux/if_ether.h> #include <linux/mutex.h> #include <linux/rtc.h>
@@ -45,6 +47,10 @@ struct omnia_mcu {/* MCU watchdog */ struct watchdog_device wdt; + +/* true random number generator */ +struct hwrng trng; +struct completion trng_completion; }; int omnia_cmd_write_read(const struct i2c_client *client,
@@ -147,11 +153,13 @@ static inline int omnia_cmd_read_u8(const struct i2c_client *client, u8 cmd) return err ?: reply; } +extern const u8 omnia_int_to_gpio_idx[32 ];extern const struct attribute_group omnia_mcu_gpio_group;extern const struct attribute_group omnia_mcu_poweroff_group;int omnia_mcu_register_gpiochip (struct omnia_mcu *mcu);int omnia_mcu_register_sys_off_and_wakeup (struct omnia_mcu *mcu); +int omnia_mcu_register_trng (struct omnia_mcu *mcu);int omnia_mcu_register_watchdog (struct omnia_mcu *mcu);#endif /* __TURRIS_OMNIA_MCU_H */
Signature · 1 line
2.43.2
Re: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 4 lines · Marek Behún
Add support for true random number generator provided by the MCU. New Omnia boards come without the Atmel SHA204-A chip. Instead the crypto functionality is provided by new microcontroller, which has a TRNG peripheral.
...
drivers/platform/cznic/turris-omnia-mcu-trng.c line 62
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+static void omnia_irq_mapping_drop (void *res) +{ +irq_dispose_mapping ((unsigned int )(unsigned long )res); +}
Leftover?
Quoted 8 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +8
-0+int omnia_mcu_register_trng (struct omnia_mcu *mcu) +{ +struct device *dev = &mcu->client->dev; +u8 irq_idx, dummy; +int irq, err; + +if (!(mcu->features &FEAT_TRNG )) +return 0 ;
drivers/platform/cznic/turris-omnia-mcu-trng.c line 81
Quoted 10 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +9
-0+ + irq_idx = omnia_int_to_gpio_idx[__bf_shf (INT_TRNG )]; + irq =gpiod_to_irq (gpiochip_get_desc (&mcu->gc, irq_idx)); +if (irq <0 ) +return dev_err_probe (dev, irq,"Cannot get TRNG IRQ\n" ); + err =devm_add_action_or_reset (dev, omnia_irq_mapping_drop, + (void *)(unsigned long )irq); +if (err) +return err;
Are you sure it's correct now?
Quoted 27 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +27
-0+/* If someone else cleared the TRNG interrupt but did not read the +* entropy, a new interrupt won't be generated, and entropy collection +* will be stuck. Ensure an interrupt will be generated by executing +* the collect entropy command (and discarding the result). +*/ + err =omnia_cmd_read (mcu->client,CMD_TRNG_COLLECT_ENTROPY , &dummy,1 ); +if (err) +return err; + +init_completion (&mcu->trng_completion); + + err =devm_request_threaded_irq (dev, irq,NULL , omnia_trng_irq_handler, +IRQF_ONESHOT ,"turris-omnia-mcu-trng" , + mcu); +if (err) +return dev_err_probe (dev, err,"Cannot request TRNG IRQ\n" ); + + mcu->trng.name ="turris-omnia-mcu-trng" ; + mcu->trng.read = omnia_trng_read; + mcu->trng.priv = (unsigned long )mcu; + + err =devm_hwrng_register (dev, &mcu->trng); +if (err) +return dev_err_probe (dev, err,"Cannot register TRNG\n" ); + +return 0 ; +}
Signature · 2 lines
With Best Regards, Andy Shevchenko
Marek Behún
maintainerRe: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 6 lines · On Wed, 24 Apr 2024 21:33:44 +0300 Andy Shevchenko <[email protected]> wrote:
Quoted 4 lines · Marek Behún
Add support for true random number generator provided by the MCU. New Omnia boards come without the Atmel SHA204-A chip. Instead the crypto functionality is provided by new microcontroller, which has a TRNG peripheral.
Quoted 8 lines
...
drivers/platform/cznic/turris-omnia-mcu-trng.c line 62
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+static void omnia_irq_mapping_drop (void *res) +{ +irq_dispose_mapping ((unsigned int )(unsigned long )res); +}Leftover?
What do you mean? I dropped the devm-helpers.h changes, now I do devm_add_action_or_reset() manually, with this function as the action.
Quoted 14 lines
Quoted 13 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +13
-0+int omnia_mcu_register_trng (struct omnia_mcu *mcu) +{ +struct device *dev = &mcu->client->dev; +u8 irq_idx, dummy; +int irq, err; + +if (!(mcu->features &FEAT_TRNG )) +return 0 ; + + irq_idx = omnia_int_to_gpio_idx[__bf_shf (INT_TRNG )]; + irq =gpiod_to_irq (gpiochip_get_desc (&mcu->gc, irq_idx)); +if (irq <0 ) +return dev_err_probe (dev, irq,"Cannot get TRNG IRQ\n" );
Quoted 6 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c line 81
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+ err =devm_add_action_or_reset (dev, omnia_irq_mapping_drop, + (void *)(unsigned long )irq); +if (err) +return err;Are you sure it's correct now?
Yes, why wouldn't it?
Re: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 3 lines · Marek Behún
Quoted 1 line · On Wed, 24 Apr 2024 21:33:44 +0300 Andy Shevchenko <[email protected]> wrote:
On Wed, Apr 24, 2024 at 07:38:05PM +0200, Marek Behún wrote:
...
Quoted 9 lines
Quoted 6 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c line 62
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+static void omnia_irq_mapping_drop (void *res) +{ +irq_dispose_mapping ((unsigned int )(unsigned long )res); +}Leftover?
What do you mean? I dropped the
devm-helpers.hchanges, now I dodevm_add_action_or_reset()manually, with this function as the action.
But why?
...
Quoted 5 lines
Quoted 4 lines
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+ irq_idx = omnia_int_to_gpio_idx[__bf_shf (INT_TRNG )]; + irq =gpiod_to_irq (gpiochip_get_desc (&mcu->gc, irq_idx)); +if (irq <0 ) +return dev_err_probe (dev, irq,"Cannot get TRNG IRQ\n" );
Quoted 8 lines
Quoted 6 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c line 81
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+ err =devm_add_action_or_reset (dev, omnia_irq_mapping_drop, + (void *)(unsigned long )irq); +if (err) +return err;Are you sure it's correct now?
Yes, why wouldn't it?
For what purpose? I don't see drivers doing that. Are you expecting that the same IRQ mapping will be reused for something else? Can you elaborate how? (I can imagine one theoretical / weird case how to achieve that, but impractical.)
Besides above, this is asymmetrical call to gpiod_to_irq(). If we really care about this, it should be provided by GPIO library.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Marek Behún
maintainerRe: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 33 lines · On Wed, 24 Apr 2024 22:47:10 +0300 Andy Shevchenko <[email protected]> wrote:
Quoted 3 lines · Marek Behún
Quoted 1 line · On Wed, 24 Apr 2024 21:33:44 +0300 Andy Shevchenko <[email protected]> wrote:
On Wed, Apr 24, 2024 at 07:38:05PM +0200, Marek Behún wrote:
...
Quoted 9 lines
Quoted 6 lines
Review
Quoted 4 lines
(quoted diff) +4
-0+static void omnia_irq_mapping_drop(void *res) +{ + irq_dispose_mapping((unsigned int)(unsigned long)res); +}Leftover?
What do you mean? I dropped the
devm-helpers.hchanges, now I dodevm_add_action_or_reset()manually, with this function as the action.But why?
...
Quoted 12 lines
Quoted 11 lines
Review
Quoted 9 lines
(quoted diff) +8
-0+ irq_idx = omnia_int_to_gpio_idx[__bf_shf(INT_TRNG)]; + irq = gpiod_to_irq(gpiochip_get_desc(&mcu->gc, irq_idx)); + if (irq < 0) + return dev_err_probe(dev, irq, "Cannot get TRNG IRQ\n"); + err = devm_add_action_or_reset(dev, omnia_irq_mapping_drop, + (void *)(unsigned long)irq); + if (err) + return err;Are you sure it's correct now?
Quoted 6 lines
Quoted 1 line
Yes, why wouldn't it?
For what purpose? I don't see drivers doing that. Are you expecting that the same IRQ mapping will be reused for something else? Can you elaborate how? (I can imagine one theoretical / weird case how to achieve that, but impractical.)
I do a lot of binding/unbinding of that driver. I was under the impression that all resources should be dropped on driver unbind.
Quoted 3 lines
Besides above, this is asymmetrical call to
gpiod_to_irq(). If we really care about this, it should be provided by GPIO library.
Something like the following?
From 5aac93d55f6fb750726f7e879672142956981a4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Beh=C3=BAn?= <[email protected]>
Date: Thu, 25 Apr 2024 11:33:33 +0200
Subject: [PATCH] gpiolib: devres: Add resource managed version of
gpiod_to_irq()
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Add devm_gpiod_to_irq(), a resource managed version of gpiod_to_irq(). The release function calls irq_dispose_mapping().
--- drivers/gpio/gpiolib-devres.c | 27 +++++++++++++++++++++++++++ include/linux/gpio/consumer.h | 10 ++++++++++ 2 files changed, 37 insertions(+)
drivers/gpio/gpiolib-devres.c +27 -0
@@ -12,6 +12,7 @@#include <linux/gpio/consumer.h> #include <linux/device.h> #include <linux/gfp.h> +#include <linux/irqdomain.h> #include "gpiolib.h"
@@ -427,3 +428,29 @@ int devm_gpiochip_add_data_with_key(struct device *dev, struct gpio_chip *gc, voreturn devm_add_action_or_reset (dev, devm_gpio_chip_release, gc); }EXPORT_SYMBOL_GPL (devm_gpiochip_add_data_with_key); + +static void devm_gpiod_irq_release (void *data) +{ +irq_dispose_mapping ((unsigned int )(unsigned long )data); +} + +/** +* devm_gpiod_to_irq() - Resource managed devm_gpiod_to_irq() +* @dev: pointer to the device that gpio_chip belongs to. +* @desc: gpio whose IRQ will be returned +* +* Return the IRQ corresponding to the passed GPIO, or an error code in case of +* error. +*/ +int devm_gpiod_to_irq (struct device *dev,const struct gpio_desc *desc) +{ +int virq; + + virq =gpiod_to_irq (desc); +if (virq <0 ) +return virq; + +return devm_add_action_or_reset (dev, devm_gpiod_irq_release, + (void *)(unsigned long )virq); +} +EXPORT_SYMBOL_GPL (devm_gpiod_to_irq);
include/linux/gpio/consumer.h +10 -0
@@ -165,6 +165,8 @@ int gpiod_is_active_low(const struct gpio_desc *desc);int gpiod_cansleep (const struct gpio_desc *desc);int gpiod_to_irq (const struct gpio_desc *desc); +int devm_gpiod_to_irq (struct device *dev,const struct gpio_desc *desc); +int gpiod_set_consumer_name (struct gpio_desc *desc,const char *name);/* Convert between the old gpio_ and new gpiod_ interfaces */
@@ -519,6 +521,14 @@ static inline int gpiod_to_irq(const struct gpio_desc *desc)return -EINVAL ; } +static inline int devm_gpiod_to_irq (struct device *dev, +const struct gpio_desc *desc) +{ +/* GPIO can never have been requested */ +WARN_ON (desc); +return -EINVAL ; +} +static inline int gpiod_set_consumer_name (struct gpio_desc *desc,const char *name) {
Signature · 1 line
2.43.2
Re: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 3 lines · Marek Behún
Quoted 1 line · On Wed, 24 Apr 2024 22:47:10 +0300 Andy Shevchenko <[email protected]> wrote:
On Wed, Apr 24, 2024 at 08:51:23PM +0200, Marek Behún wrote:
...
Quoted 5 lines
Quoted 4 lines
For what purpose? I don't see drivers doing that. Are you expecting that the same IRQ mapping will be reused for something else? Can you elaborate how? (I can imagine one theoretical / weird case how to achieve that, but impractical.)
Quoted 7 lines
I do a lot of binding/unbinding of that driver. I was under the impression that all resources should be dropped on driver unbind.
Quoted 2 lines
Besides above, this is asymmetrical call to
gpiod_to_irq(). If we really care about this, it should be provided by GPIO library.Something like the following?
Not needed. IRQ mappings are per domain, and GPIO chip has its own associated with the respective lifetime, AFAIU when you remove the GPIO chip, all mappings will be disposed (as I pointed out in previous mail).
Signature · 2 lines
With Best Regards, Andy Shevchenko
Marek Behún
maintainerRe: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
Quoted 15 lines · On Thu, 25 Apr 2024 13:04:07 +0300 Andy Shevchenko <[email protected]> wrote:
Quoted 3 lines · Marek Behún
Quoted 1 line · On Wed, 24 Apr 2024 22:47:10 +0300 Andy Shevchenko <[email protected]> wrote:
On Wed, Apr 24, 2024 at 08:51:23PM +0200, Marek Behún wrote:
...
Quoted 8 lines
Quoted 4 lines
For what purpose? I don't see drivers doing that. Are you expecting that the same IRQ mapping will be reused for something else? Can you elaborate how? (I can imagine one theoretical / weird case how to achieve that, but impractical.)
I do a lot of binding/unbinding of that driver. I was under the impression that all resources should be dropped on driver unbind.
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
Besides above, this is asymmetrical call to
gpiod_to_irq(). If we really care about this, it should be provided by GPIO library.Something like the following?
Not needed. IRQ mappings are per domain, and GPIO chip has its own associated with the respective lifetime, AFAIU when you remove the GPIO chip, all mappings will be disposed (as I pointed out in previous mail).
OMG you are right :) of course. OK, I shall drop this.
Marek
Re: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
In reply to Andy ShevchenkoQuoted 4 lines · Andy Shevchenko
Quoted 3 lines · Marek Behún
Quoted 1 line · On Wed, 24 Apr 2024 21:33:44 +0300 Andy Shevchenko <[email protected]> wrote:
On Wed, Apr 24, 2024 at 07:38:05PM +0200, Marek Behún wrote:
...
Quoted 11 lines
Quoted 9 lines
Quoted 6 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c line 62
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+static void omnia_irq_mapping_drop (void *res) +{ +irq_dispose_mapping ((unsigned int )(unsigned long )res); +}Leftover?
What do you mean? I dropped the
devm-helpers.hchanges, now I dodevm_add_action_or_reset()manually, with this function as the action.But why?
...
Quoted 14 lines
Quoted 5 lines
Quoted 4 lines
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+ irq_idx = omnia_int_to_gpio_idx[__bf_shf (INT_TRNG )]; + irq =gpiod_to_irq (gpiochip_get_desc (&mcu->gc, irq_idx)); +if (irq <0 ) +return dev_err_probe (dev, irq,"Cannot get TRNG IRQ\n" );Quoted 8 lines
Quoted 6 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c line 81
Quoted 4 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +4
-0+ err =devm_add_action_or_reset (dev, omnia_irq_mapping_drop, + (void *)(unsigned long )irq); +if (err) +return err;Are you sure it's correct now?
Yes, why wouldn't it?
Quoted 7 lines
For what purpose? I don't see drivers doing that. Are you expecting that the same IRQ mapping will be reused for something else? Can you elaborate how? (I can imagine one theoretical / weird case how to achieve that, but impractical.)
Besides above, this is asymmetrical call to
gpiod_to_irq(). If we really care about this, it should be provided by GPIO library.
FWIW, gpiochip_irqchip_remove() disposes mappings for internally allocated IRQ domains. So with your code it even might be a double-disposal.
Signature · 2 lines
With Best Regards, Andy Shevchenko
Re: [PATCH v7 6/9] platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
In reply to Marek BehúnQuoted 4 lines · Marek Behún
Add support for true random number generator provided by the MCU. New Omnia boards come without the Atmel SHA204-A chip. Instead the crypto functionality is provided by new microcontroller, which has a TRNG peripheral.
...
drivers/platform/cznic/turris-omnia-mcu-trng.c line 87
Quoted 5 lines
drivers/platform/cznic/turris-omnia-mcu-trng.c new file +5
-0+/* If someone else cleared the TRNG interrupt but did not read the +* entropy, a new interrupt won't be generated, and entropy collection +* will be stuck. Ensure an interrupt will be generated by executing +* the collect entropy command (and discarding the result). +*/
/*
* Note, the above style is solely for net subsystem. The
* others should use the usual one, like in this example. */
Signature · 2 lines
With Best Regards, Andy Shevchenko
Marek Behún
maintainerPATCH v7 7/9 platform: cznic: turris-omnia-mcu: Add support for digital message signing via debugfs
In reply to Marek BehúnAdd support for digital message signing with private key stored in the MCU. Boards with MKL MCUs have a NIST256p ECDSA private key created when manufactured. The private key is not readable from the MCU, but MCU allows for signing messages with it and retrieving the public key.
As described in a similar commit 50524d787de3 ("firmware:
turris-mox-rwtm: support ECDSA signatures via debugfs"):
The optimal solution would be to register an akcipher provider via kernel's crypto API, but crypto API does not yet support accessing akcipher API from userspace (and probably won't for some time, see
https://www.spinics.net/lists/linux-crypto/msg38388.html).
Therefore we add support for accessing this signature generation mechanism via debugfs for now, so that userspace can access it.
--- .../ABI/testing/debugfs-turris-omnia-mcu | 13 ++ .../sysfs-bus-i2c-devices-turris-omnia-mcu | 13 ++ MAINTAINERS | 1 + drivers/platform/cznic/Kconfig | 2 + drivers/platform/cznic/Makefile | 1 + .../platform/cznic/turris-omnia-mcu-base.c | 45 +++- .../platform/cznic/turris-omnia-mcu-debugfs.c | 216 ++++++++++++++++++ drivers/platform/cznic/turris-omnia-mcu.h | 23 ++ 8 files changed, 313 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/debugfs-turris-omnia-mcu create mode 100644 drivers/platform/cznic/turris-omnia-mcu-debugfs.c
Documentation/ABI/testing/debugfs-turris-omnia-mcu new file +13 -0
@@ -0,0 +1,13 @@ +What: /sys/kernel/debug/turris-omnia-mcu/do_sign +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: + + ======= =========================================================== + (Write) Message to sign with the ECDSA private key stored in MCU. + The message must be exactly 32 bytes long (since this is + intended to be a SHA-256 hash). + (Read) The resulting signature, 64 bytes. This contains the R and + S values of the ECDSA signature, both in big-endian format. + ======= ===========================================================
Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu +13 -0
@@ -90,6 +90,19 @@ Description: (RO) Contains the microcontroller type (STM32, GD32, MKL). Format: %s. +What: /sys/bus/i2c/devices/<mcu_device>/public_key +Date: July 2024 +KernelVersion: 6.10 +Contact: Marek Behún <[email protected]> +Description: (RO) Contains board ECDSA public key. + + Only available if MCU supports signing messages with the ECDSA + algorithm. If so, the board has a private key stored in the MCU + that was generated during manufacture and cannot be retrieved + from the MCU. + + Format: %s. + What: /sys/bus/i2c/devices/<mcu_device>/reset_selector Date: July 2024 KernelVersion: 6.10
MAINTAINERS +1 -0
@@ -2139,6 +2139,7 @@ M: Marek Behún <[email protected]> S: Maintained W: https://www.turris.cz/ F: Documentation/ABI/testing/debugfs-moxtet +F: Documentation/ABI/testing/debugfs-turris-omnia-mcu F: Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu F: Documentation/ABI/testing/sysfs-bus-moxtet-devices F: Documentation/ABI/testing/sysfs-firmware-turris-mox-rwtm
drivers/platform/cznic/Kconfig +2 -0
@@ -30,6 +30,8 @@ config TURRIS_OMNIA_MCU disabled) and the ability to configure wake up from this mode (via rtcwake) - true random number generator (if available on the MCU) + - ECDSA message signing with board private key (if available on the + MCU) - MCU watchdog - GPIO pins - to get front button press events (the front button can be
drivers/platform/cznic/Makefile +1 -0
@@ -6,3 +6,4 @@ turris-omnia-mcu-y += turris-omnia-mcu-gpio.o turris-omnia-mcu-y += turris-omnia-mcu-sys-off-wakeup.o turris-omnia-mcu-y += turris-omnia-mcu-trng.o turris-omnia-mcu-y += turris-omnia-mcu-watchdog.o +turris-omnia-mcu-$(CONFIG_DEBUG_FS) += turris-omnia-mcu-debugfs.o
drivers/platform/cznic/turris-omnia-mcu-base.c +44 -1
81 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu-debugfs.c new file +216 -0
216 lines not on this page · raw message
drivers/platform/cznic/turris-omnia-mcu.h +23 -0
@@ -21,6 +21,9 @@#include <asm/byteorder.h> #include <asm/unaligned.h> +#define OMNIA_MCU_CRYPTO_PUBLIC_KEY_LEN 33 +#define OMNIA_MCU_CRYPTO_SIGNATURE_LEN 64 +struct omnia_mcu {struct i2c_client *client;const char *type;
@@ -30,6 +33,7 @@ struct omnia_mcu {u64 board_serial_number;u8 board_first_mac[ETH_ALEN ];u8 board_revision; +u8 board_public_key[OMNIA_MCU_CRYPTO_PUBLIC_KEY_LEN ];/* GPIO chip */ struct gpio_chip gc;
@@ -51,6 +55,16 @@ struct omnia_mcu {/* true random number generator */ struct hwrng trng;struct completion trng_completion; + +#ifdef CONFIG_DEBUG_FS +/* MCU ECDSA message signing via debugfs */ +struct dentry *debugfs_root; +struct completion msg_signed_completion; +struct mutex sign_lock; +unsigned int sign_state; +u8 signature[OMNIA_MCU_CRYPTO_SIGNATURE_LEN ]; +int sign_err; +#endif }; int omnia_cmd_write_read(const struct i2c_client *client,
@@ -162,4 +176,13 @@ int omnia_mcu_register_sys_off_and_wakeup(struct omnia_mcu *mcu);int omnia_mcu_register_trng (struct omnia_mcu *mcu);int omnia_mcu_register_watchdog (struct omnia_mcu *mcu); +#ifdef CONFIG_DEBUG_FS +int omnia_mcu_register_debugfs (struct omnia_mcu *mcu); +#else +static inline int omnia_mcu_register_debugfs (struct omnia_mcu *mcu) +{ +return 0 ; +} +#endif +#endif /* __TURRIS_OMNIA_MCU_H */
Signature · 1 line
2.43.2
Marek Behún
maintainerPATCH v7 8/9 ARM: dts: turris-omnia: Add MCU system-controller node
In reply to Marek BehúnTurris Omnia's MCU provides various features that can be configured over I2C at address 0x2a. Add device-tree node.
--- .../dts/marvell/armada-385-turris-omnia.dts | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts +21 -1
@@ -218,7 +218,22 @@ i2c@0 { #size-cells = <0>; reg = <0>; - /* STM32F0 command interface at address 0x2a */ + mcu: system-controller@2a { + compatible = "cznic,turris-omnia-mcu"; + reg = <0x2a>; + + pinctrl-names = "default"; + pinctrl-0 = <&mcu_pins>; + + interrupt-parent = <&gpio1>; + interrupts = <11 IRQ_TYPE_NONE>; + + gpio-controller; + #gpio-cells = <3>; + + interrupt-controller; + #interrupt-cells = <2>; + }; led-controller@2b { compatible = "cznic,turris-omnia-leds";
@@ -501,6 +516,11 @@ fixed-link { }; &pinctrl { + mcu_pins: mcu-pins { + marvell,pins = "mpp43"; + marvell,function = "gpio"; + }; + pcawan_pins: pcawan-pins { marvell,pins = "mpp46"; marvell,function = "gpio";
Signature · 1 line
2.43.2
Gregory CLEMENT
maintainerRe: [PATCH v7 8/9] ARM: dts: turris-omnia: Add MCU system-controller node
Hello Marek,
Quoted 4 lines
Turris Omnia's MCU provides various features that can be configured over I2C at address
0x2a. Add device-tree node.Fixes 26ca8b52d6e1 ("ARM: dts: add support for Turris Omnia")
Is it really a fix ?
It seems that the node you add depends on the firmware support that was not yet added.
Gregory
Quoted 47 lines
Signed-off-by Marek Behún <[email protected]>--- .../dts/marvell/armada-385-turris-omnia.dts | 22 ++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts +21
-1@@ -218,7 +218,22 @@ i2c@0 { #size-cells = <0>; reg = <0>; - /* STM32F0 command interface at address 0x2a */ + mcu: system-controller@2a { + compatible = "cznic,turris-omnia-mcu"; + reg = <0x2a>; + + pinctrl-names = "default"; + pinctrl-0 = <&mcu_pins>; + + interrupt-parent = <&gpio1>; + interrupts = <11 IRQ_TYPE_NONE>; + + gpio-controller; + #gpio-cells = <3>; + + interrupt-controller; + #interrupt-cells = <2>; + }; led-controller@2b { compatible = "cznic,turris-omnia-leds";@@ -501,6 +516,11 @@ fixed-link { }; &pinctrl { + mcu_pins: mcu-pins { + marvell,pins = "mpp43"; + marvell,function = "gpio"; + }; + pcawan_pins: pcawan-pins { marvell,pins = "mpp46"; marvell,function = "gpio";Signature · 1 line
2.43.2
Marek Behún
maintainerRe: [PATCH v7 8/9] ARM: dts: turris-omnia: Add MCU system-controller node
Quoted 5 lines · On Fri, 26 Apr 2024 18:01:20 +0200 Gregory CLEMENT…
Hello Marek,
Quoted 3 lines
Turris Omnia's MCU provides various features that can be configured over I2C at address
0x2a. Add device-tree node.
Quoted 8 lines
Quoted 1 line
Fixes 26ca8b52d6e1 ("ARM: dts: add support for Turris Omnia")Is it really a fix ?
It seems that the node you add depends on the firmware support that was not yet added.
Gregory
It is a fix in the sense that Omnia always had the MCU, and so device-tree without the MCU node was incorrect.
Since device-trees should be (if possible) backwards and forwards compatible, this should not be a problem.
But I am guessing it might be because of what new U-Boot does: if it finds the MCU node in the device-tree, it will add a reset gpio property for ethernet PHY, linking it to the MCU node. So if this patch got backported to older kernel where the MCU driver is not present, and the board had this new U-Boot, the kernel would not create the eth2 interface, because it would be waiting for a driver providing the GPIO.
So hmm, maybe I should drop the Fixes tag.
Andrew Lunn
maintainerRe: [PATCH v7 8/9] ARM: dts: turris-omnia: Add MCU system-controller node
Quoted 7 lines
But I am guessing it might be because of what new U-Boot does: if it finds the MCU node in the device-tree, it will add a reset gpio property for ethernet PHY, linking it to the MCU node. So if this patch got backported to older kernel where the MCU driver is not present, and the board had this new U-Boot, the kernel would not create the eth2 interface, because it would be waiting for a driver providing the GPIO.
You should make this clear in the commit message. There is a danger the ML algorithm which picks patches for back porting decides this is a candidate. Hopefully a human will read the commit message and then reject it.
Andrew
Marek Behún
maintainerPATCH v7 9/9 ARM: dts: turris-omnia: Add GPIO key node for front button
In reply to Marek BehúnNow that we have the MCU device-tree node, which acts as a GPIO controller, add GPIO key node for the front button.
--- .../boot/dts/marvell/armada-385-turris-omnia.dts | 13 +++++++++++++ 1 file changed, 13 insertions(+)
arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts +13 -0
@@ -112,6 +112,19 @@ sfp: sfp { status = "disabled"; }; + gpio-keys { + compatible = "gpio-keys"; + + front-button { + label = "Front Button"; + linux,code = <KEY_VENDOR>; + linux,can-disable; + gpios = <&mcu 0 12 GPIO_ACTIVE_HIGH>; + /* debouncing is done by the microcontroller */ + debounce-interval = <0>; + }; + }; + sound { compatible = "simple-audio-card"; simple-audio-card,name = "SPDIF";
Signature · 1 line
2.43.2
Gregory CLEMENT
maintainerRe: [PATCH v7 9/9] ARM: dts: turris-omnia: Add GPIO key node for front button
Hello Marek,
Quoted 4 lines
Now that we have the MCU device-tree node, which acts as a GPIO controller, add GPIO key node for the front button.
Fixes 26ca8b52d6e1 ("ARM: dts: add support for Turris Omnia")
Same as previous patch is it really a fix ?
Gregory
Quoted 31 lines
Signed-off-by Marek Behún <[email protected]>--- .../boot/dts/marvell/armada-385-turris-omnia.dts | 13 +++++++++++++ 1 file changed, 13 insertions(+)arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts +13
-0@@ -112,6 +112,19 @@ sfp: sfp { status = "disabled"; }; + gpio-keys { + compatible = "gpio-keys"; + + front-button { + label = "Front Button"; + linux,code = <KEY_VENDOR>; + linux,can-disable; + gpios = <&mcu 0 12 GPIO_ACTIVE_HIGH>; + /* debouncing is done by the microcontroller */ + debounce-interval = <0>; + }; + }; + sound { compatible = "simple-audio-card"; simple-audio-card,name = "SPDIF";Signature · 1 line
2.43.2
Gregory CLEMENT
maintainerHello all,
Quoted 31 lines
Hello Andy, Hans, Ilpo, Arnd, Gregory, and others,
this is v7 of the series adding Turris Omnia MCU driver.
This series depends on the immutable branch between LEDs and locking, introducing
devm_mutex_init(), see the PR
https://lore.kernel.org/linux-leds/[email protected]/See also cover letters for v1, v2, v3, v4, v5 and v6:
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/
https://patchwork.kernel.org/project/linux-soc/cover/[email protected]/Changes since v6:
- moved the DT binding fromarm/cznic,turris-omnia-mcu.yamltofirmware/cznic,turris-omnia-mcu.yaml, as suggested by Conor Dooley (patch 1)
- dropped thedevm-helpers.hadditions, for the reasons see
https://lore.kernel.org/soc/20240423184346.37eb0915@thinkpad/
- use gpiod_to_irq(gpiochip_get_desc(...)) instead ofirq_create_mapping(), as suggested by Andy Shevchenko (patches 6 and
7)
- added a dummy read of TRNG entropy when registering TRNG, in case someone cleared the TRNG interrupt before probing the driver, but did not read the entropy (the MCU won't send a new TRNG interrupt if the entropy is not collected) (patch 6)
- fixed a bug in TRNG probing, wherein if the
Quoted 9 lines
Marek Behún (9):
dt-bindings: arm: add cznic,turris-omnia-mcu binding
platform: cznic: Add preliminary support for Turris Omnia MCU
platform: cznic: turris-omnia-mcu: Add support for MCU connected GPIOs
platform: cznic: turris-omnia-mcu: Add support for poweroff and wakeup
platform: cznic: turris-omnia-mcu: Add support for MCU watchdog
platform: cznic: turris-omnia-mcu: Add support for MCU provided TRNG
platform: cznic: turris-omnia-mcu: Add support for digital message
signing via debugfs
It is still early as there are some comment pending but I wonder who will responsible of merging all theses patches ?
Arnd ? Hans ? Ilpo ? me ?
Gregory
Quoted 37 lines
ARM: dts: turris-omnia: Add MCU system-controller node
ARM: dts: turris-omnia: Add GPIO key node for front button.../ABI/testing/debugfs-turris-omnia-mcu | 13 + .../sysfs-bus-i2c-devices-turris-omnia-mcu | 126 ++ .../firmware/cznic,turris-omnia-mcu.yaml | 86 ++ MAINTAINERS | 5 + .../dts/marvell/armada-385-turris-omnia.dts | 35 +- drivers/platform/Kconfig | 2 + drivers/platform/Makefile | 1 + drivers/platform/cznic/Kconfig | 51 + drivers/platform/cznic/Makefile | 9 + .../platform/cznic/turris-omnia-mcu-base.c | 439 +++++++ .../platform/cznic/turris-omnia-mcu-debugfs.c | 216 ++++ .../platform/cznic/turris-omnia-mcu-gpio.c | 1047 +++++++++++++++++ .../cznic/turris-omnia-mcu-sys-off-wakeup.c | 258 ++++ .../platform/cznic/turris-omnia-mcu-trng.c | 109 ++ .../cznic/turris-omnia-mcu-watchdog.c | 123 ++ drivers/platform/cznic/turris-omnia-mcu.h | 188 +++ include/linux/turris-omnia-mcu-interface.h | 249 ++++ 17 files changed, 2956 insertions(+), 1 deletion(-) create mode 100644 Documentation/ABI/testing/debugfs-turris-omnia-mcu create mode 100644 Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu create mode 100644 Documentation/devicetree/bindings/firmware/cznic,turris-omnia-mcu.yaml create mode 100644 drivers/platform/cznic/Kconfig create mode 100644 drivers/platform/cznic/Makefile create mode 100644 drivers/platform/cznic/turris-omnia-mcu-base.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-debugfs.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-gpio.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-sys-off-wakeup.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-trng.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu-watchdog.c create mode 100644 drivers/platform/cznic/turris-omnia-mcu.h create mode 100644 include/linux/turris-omnia-mcu-interface.hSignature · 1 line
2.43.2
Marek Behún
maintainerQuoted 2 lines · On Fri, 26 Apr 2024 18:13:32 +0200 Gregory CLEMENT…
Hello all,
...
Quoted 5 lines
It is still early as there are some comment pending but I wonder who will responsible of merging all theses patches ?
Arnd ? Hans ? Ilpo ? me ?
I am assigning these patches to Arnd on patchwork all this time, so I guess it could be him, unless he has a problem with this?
I've just sent v8.
Marek