From: Jarkko Sakkinen <jarkko@kernel.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: sudeep.holla@arm.com, peterhuewe@gmx.de, jgg@ziepe.ca,
stuart.yoder@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: [PATCH v4 2/2] tpm: tpm_crb_ffa: try to probe tpm_crb_ffa when it's built-in
Date: Wed, 25 Jun 2025 20:03:08 +0300 [thread overview]
Message-ID: <aFwrzEPUAbLaOAgY@kernel.org> (raw)
In-Reply-To: <aFvRePYyX/Xuxe8N@e129823.arm.com>
On Wed, Jun 25, 2025 at 11:37:44AM +0100, Yeoreum Yun wrote:
> Hi Jarkkok,
>
> > > --- a/drivers/char/tpm/tpm_crb_ffa.c
> > > +++ b/drivers/char/tpm/tpm_crb_ffa.c
> > > @@ -115,6 +115,7 @@ struct tpm_crb_ffa {
> > > };
> > >
> > > static struct tpm_crb_ffa *tpm_crb_ffa;
> > > +static struct ffa_driver tpm_crb_ffa_driver;
> > >
> > > static int tpm_crb_ffa_to_linux_errno(int errno)
> > > {
> > > @@ -168,13 +169,23 @@ static int tpm_crb_ffa_to_linux_errno(int errno)
> > > */
> > > int tpm_crb_ffa_init(void)
> > > {
> > > + int ret = 0;
> > > +
> > > + if (!IS_MODULE(CONFIG_TCG_ARM_CRB_FFA)) {
> > > + ret = ffa_register(&tpm_crb_ffa_driver);
> > > + if (ret) {
> > > + tpm_crb_ffa = ERR_PTR(-ENODEV);
> > > + return ret;
> > > + }
> > > + }
> > > +
> > > if (!tpm_crb_ffa)
> > > - return -ENOENT;
> > > + ret = -ENOENT;
> > >
> > > if (IS_ERR_VALUE(tpm_crb_ffa))
> > > - return -ENODEV;
> > > + ret = -ENODEV;
> > >
> > > - return 0;
> > > + return ret;
> > > }
> > > EXPORT_SYMBOL_GPL(tpm_crb_ffa_init);
> > >
> > > @@ -369,7 +380,9 @@ static struct ffa_driver tpm_crb_ffa_driver = {
> > > .id_table = tpm_crb_ffa_device_id,
> > > };
> > >
> > > +#ifdef MODULE
> > > module_ffa_driver(tpm_crb_ffa_driver);
> > > +#endif
> > >
> > > MODULE_AUTHOR("Arm");
> > > MODULE_DESCRIPTION("TPM CRB FFA driver");
> > > --
> > > LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
> > >
> >
> > NAK
>
> If you NACK with your comment on the cover letter,
> Would you check the my comments please?
>
> Actually, this wouldn't be fixed with the Kconfig.
I got into the same page (see my response to your response at 0/2) :-)
Thanks for the patience.
>
> Thanks
>
> --
> Sincerely,
> Yeoreum Yun
BR, Jarkko
next prev parent reply other threads:[~2025-06-25 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 10:23 [PATCH v4 0/2] generate boot_aggregate log in IMA with TPM using CRB over FF-A Yeoreum Yun
2025-06-18 10:23 ` [PATCH v4 1/2] firmware: arm_ffa: Change initcall level of ffa_init() to rootfs_initcall Yeoreum Yun
2025-06-22 12:22 ` Mimi Zohar
2025-06-24 23:29 ` Jarkko Sakkinen
2025-06-18 10:23 ` [PATCH v4 2/2] tpm: tpm_crb_ffa: try to probe tpm_crb_ffa when it's built-in Yeoreum Yun
2025-06-22 12:23 ` Mimi Zohar
2025-06-24 23:29 ` Jarkko Sakkinen
2025-06-25 10:37 ` Yeoreum Yun
2025-06-25 17:03 ` Jarkko Sakkinen [this message]
2025-06-24 23:28 ` [PATCH v4 0/2] generate boot_aggregate log in IMA with TPM using CRB over FF-A Jarkko Sakkinen
2025-06-25 10:36 ` Yeoreum Yun
2025-06-25 16:59 ` Jarkko Sakkinen
2025-06-25 17:01 ` Jarkko Sakkinen
2025-06-25 19:35 ` Sudeep Holla
2025-06-25 21:47 ` Jarkko Sakkinen
2025-06-26 19:53 ` Sudeep Holla
2025-07-02 22:24 ` Jarkko Sakkinen
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=aFwrzEPUAbLaOAgY@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stuart.yoder@arm.com \
--cc=sudeep.holla@arm.com \
--cc=yeoreum.yun@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).