From: Jarkko Sakkinen <jarkko@kernel.org>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: atmel: depend on X86
Date: Sat, 18 Jul 2026 21:35:20 +0300 [thread overview]
Message-ID: <alvHaDuqU-HIm_G1@kernel.org> (raw)
In-Reply-To: <20260712183234.23125-1-kmehltretter@gmail.com>
On Sun, Jul 12, 2026 at 08:32:34PM +0200, Karl Mehltretter wrote:
> tpm_atmel probes for the chip at fixed x86 Super-I/O ports (0x4e) with
> inb()/outb(), so it only works on x86. TCG_ATMEL nevertheless depends
> only on HAS_IOPORT_MAP/HAS_IOPORT, which arm and arm64 also satisfy.
> There the probe is useless, and on platforms whose unbacked I/O access
> faults it oopses in init_atmel() at boot (e.g. arm/versatile):
>
> Unable to handle kernel paging request at virtual address fee0004e
> PC is at init_atmel+0x34/0x244
>
> TCG_NSC and TCG_TIS already "depends on X86" (commit 2f592f2a7d74 ("TPM:
> NSC and TIS drivers X86 dependency fix")); TCG_ATMEL was missed. Add the
> same dependency.
>
> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
> ---
> drivers/char/tpm/Kconfig | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/char/tpm/Kconfig b/drivers/char/tpm/Kconfig
> index 8a8f692b6088..5f672f2c01b0 100644
> --- a/drivers/char/tpm/Kconfig
> +++ b/drivers/char/tpm/Kconfig
> @@ -163,8 +163,7 @@ config TCG_NSC
>
> config TCG_ATMEL
> tristate "Atmel TPM Interface"
> - depends on HAS_IOPORT_MAP
> - depends on HAS_IOPORT
> + depends on X86
> help
> If you have a TPM security chip from Atmel say Yes and it
> will be accessible from within Linux. To compile this driver
> --
> 2.39.5 (Apple Git-154)
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
prev parent reply other threads:[~2026-07-18 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 18:32 [PATCH] tpm: atmel: depend on X86 Karl Mehltretter
2026-07-18 18:35 ` Jarkko Sakkinen [this message]
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=alvHaDuqU-HIm_G1@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kmehltretter@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.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