From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: mtr@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] tee: drivers: rksecure: move header to soc/rockchip/
Date: Wed, 7 Jan 2026 13:58:36 +0100 [thread overview]
Message-ID: <20260107125837.3947578-1-a.fatoum@pengutronix.de> (raw)
We already have a directory for rockchip related headers, so move from
the top level to there.
No functional change intended.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
I don't mind if it's just absorbed/squashed into the original commits.
---
commands/rksecure.c | 2 +-
drivers/tee/optee/rksecure.c | 2 +-
include/{rk_secure_boot.h => soc/rockchip/secure_boot.h} | 6 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
rename include/{rk_secure_boot.h => soc/rockchip/secure_boot.h} (78%)
diff --git a/commands/rksecure.c b/commands/rksecure.c
index 81b4f1a62860..d761cac152ce 100644
--- a/commands/rksecure.c
+++ b/commands/rksecure.c
@@ -9,7 +9,7 @@
#include <libfile.h>
#include <linux/kstrtox.h>
-#include <rk_secure_boot.h>
+#include <soc/rockchip/secure_boot.h>
static int rksecure_write_hash_hex(const char *hex, u32 key_size_bits)
{
diff --git a/drivers/tee/optee/rksecure.c b/drivers/tee/optee/rksecure.c
index 3a5cb0cb7be1..408547dab322 100644
--- a/drivers/tee/optee/rksecure.c
+++ b/drivers/tee/optee/rksecure.c
@@ -8,7 +8,7 @@
#include <linux/array_size.h>
#include <uapi/linux/tee.h>
-#include <rk_secure_boot.h>
+#include <soc/rockchip/secure_boot.h>
#include "optee_private.h"
#include "pta_rk_secure_boot.h"
diff --git a/include/rk_secure_boot.h b/include/soc/rockchip/secure_boot.h
similarity index 78%
rename from include/rk_secure_boot.h
rename to include/soc/rockchip/secure_boot.h
index 6e247aa7eef3..128d60633359 100644
--- a/include/rk_secure_boot.h
+++ b/include/soc/rockchip/secure_boot.h
@@ -3,8 +3,8 @@
* Copyright (C) 2025 Pengutronix, Michael Tretter <m.tretter@pengutronix.de>
*/
-#ifndef __RK_SECURE_BOOT_H
-#define __RK_SECURE_BOOT_H
+#ifndef __SOC_ROCKCHIP_SECURE_BOOT_H
+#define __SOC_ROCKCHIP_SECURE_BOOT_H
#include <linux/types.h>
@@ -18,4 +18,4 @@ int rk_secure_boot_get_info(struct rk_secure_boot_info *info);
int rk_secure_boot_burn_hash(const u8 *hash, u32 key_size_bits);
int rk_secure_boot_lockdown_device(void);
-#endif /* __RK_SECURE_BOOT_H */
+#endif /* __SOC_ROCKCHIP_SECURE_BOOT_H */
--
2.47.3
next reply other threads:[~2026-01-07 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 12:58 Ahmad Fatoum [this message]
2026-01-08 20:57 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260107125837.3947578-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mtr@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox