From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Johannes Holland <johannes.holland@infineon.com>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Dhananjay Phadke <dphadke@linux.microsoft.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 2/2] tpm2: Add a TPMv2 MMIO TIS driver
Date: Tue, 13 Jul 2021 23:11:48 +0300 [thread overview]
Message-ID: <YO3zhL8JQTF/ofeT@enceladus> (raw)
In-Reply-To: <CAPnjgZ2TP0eP5WZmhoiVtAiyGDWUVp2nnd8J8YyqsUP591qk_Q@mail.gmail.com>
[...]
> > > Should be a uclass interface.
> > >
> >
> > Why? A uclass is supposed to describe and abstract hardware. This is just
> > a specific implementation of a TPM, not all TPMs are TIS compliant. We already
> > have a uclass for those.
>
> Who told you that a uclass is supposed to describe and abstract hardware? :-)
>
That's what I've mostly seen it used for, maybe i got the idea wrong.
> The uclass is how driver model does APIs, so normally a uclass would
> be used for any API. There are exceptions, but this one actually looks
> like a useful interface we should have.
>
the point is we already have a uclass for tpm devices. So why should the
we add another one that just describes the TIS interface?
> >
> > > > + .read_bytes = mmio_read_bytes,
> > > > + .write_bytes = mmio_write_bytes,
> > > > + .read16 = mmio_read16,
> > > > + .read32 = mmio_read32,
> > > > + .write32 = mmio_write32,
> > > > +};
> > > > +
> > > > +static int tpm_tis_probe(struct udevice *udev)
> > > > +{
> > > > + struct tpm_tis_chip_data *drv_data = (void *)dev_get_driver_data(udev);
> > > > + struct tpm_chip_priv *priv = dev_get_uclass_priv(udev);
> > > > + int ret = 0;
> > > > + fdt_addr_t ioaddr;
> > > > + u64 sz;
> > > > +
> > > > + ioaddr = dev_read_addr(udev);
> > > > + if (ioaddr == FDT_ADDR_T_NONE)
> > > > + return -EINVAL;
> > >
> > > consider this for easier debugging:
> > >
> > > return log_msg_ret("ioaddr", -EINVAL);
> > >
> >
> > Sure
> >
> > > > +
> > > > + ret = dev_read_u64(udev, "reg", &sz);
> > > > + if (ret)
> > > > + return -EINVAL;
> > > > +
> > > > + drv_data->iobase = ioremap(ioaddr, sz);
> > > > + log_info("Remapped TPM2 base: 0x%llx size: 0x%llx\n", ioaddr, sz);
> > >
> > > log_debug() I think?
> > >
> > Yea, that's a leftover of my initial code, were I needed to make sure the
> > ioremap worked.
> >
> > > > + tpm_tis_ops_register(udev, &phy_ops);
> > > > + ret = tpm_tis_init(udev);
> > > > + if (ret)
> > > > + goto iounmap;
> > > > +
> > > > + priv->pcr_count = drv_data->pcr_count;
> > > > + priv->pcr_select_min = drv_data->pcr_select_min;
> > > > + /*
> > > > + * Although the driver probably works with a TPMv1 our Kconfig
> > > > + * limits the driver to TPMv2 only
> > > > + */
> > > > + priv->version = TPM_V2;
> > > > +
> > > > + return ret;
> > > > +iounmap:
> > > > + iounmap(drv_data->iobase);
> > > > + return -EINVAL;
> > > > +}
> > > > +
> > > > +static int tpm_tis_remove(struct udevice *udev)
> > > > +{
> > > > + struct tpm_tis_chip_data *drv_data = (void *)dev_get_driver_data(udev);
> > > > +
> > > > + iounmap(drv_data->iobase);
> > > > + return tpm_tis_cleanup(udev);
> > > > +}
> > > > +
> > > > +static const struct tpm_ops tpm_tis_ops = {
> > > > + .open = tpm_tis_open,
> > > > + .close = tpm_tis_close,
> > > > + .get_desc = tpm_tis_get_desc,
> > > > + .send = tpm_tis_send,
> > > > + .recv = tpm_tis_recv,
> > > > + .cleanup = tpm_tis_cleanup,
> > > > +};
> > > > +
> > > > +static const struct tpm_tis_chip_data tpm_tis_std_chip_data = {
> > > > + .pcr_count = 24,
> > > > + .pcr_select_min = 3,
> > > > +};
> > > > +
> > > > +static const struct udevice_id tpm_tis_ids[] = {
> > > > + {
> > > > + .compatible = "tcg,tpm-tis-mmio",
> > > > + .data = (ulong)&tpm_tis_std_chip_data,
> > > > + },
> > > > + { }
> > > > +};
> > > > +
> > > > +U_BOOT_DRIVER(tpm_tis_mmio) = {
> > > > + .name = "tpm_tis_mmio",
> > > > + .id = UCLASS_TPM,
> > > > + .of_match = tpm_tis_ids,
> > > > + .ops = &tpm_tis_ops,
> > > > + .probe = tpm_tis_probe,
> > > > + .remove = tpm_tis_remove,
> > > > + .priv_auto = sizeof(struct tpm_chip),
> > > > +};
> > > > --
> > > > 2.32.0.rc0
> > > >
> > >
> > > Regards,
> > > Simon
> >
> > Thanks for looking at this
> > /Ilias
>
> Likewise.
>
> Regards,
> Simon
next prev parent reply other threads:[~2021-07-13 20:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:25 [PATCH 1/2 v2] tpm2: Introduce TIS tpm core Ilias Apalodimas
2021-07-07 16:25 ` [PATCH 2/2] tpm2: Add a TPMv2 MMIO TIS driver Ilias Apalodimas
2021-07-11 0:00 ` Simon Glass
2021-07-12 18:22 ` Ilias Apalodimas
2021-07-12 19:13 ` Heinrich Schuchardt
2021-07-12 19:43 ` Simon Glass
2021-07-12 22:46 ` Heinrich Schuchardt
2021-07-13 16:52 ` Simon Glass
2021-07-12 19:38 ` Simon Glass
2021-07-13 20:11 ` Ilias Apalodimas [this message]
2021-07-14 2:49 ` Simon Glass
2021-07-14 5:23 ` Ilias Apalodimas
2021-07-14 19:50 ` Simon Glass
2021-07-11 0:00 ` [PATCH 1/2 v2] tpm2: Introduce TIS tpm core Simon Glass
2021-07-12 6:24 ` Ilias Apalodimas
2021-07-12 11:42 ` Simon Glass
2021-07-12 14:03 ` Ilias Apalodimas
2021-07-12 19:43 ` Simon Glass
2021-07-13 5:51 ` Ilias Apalodimas
2021-07-13 20:17 ` Simon Glass
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=YO3zhL8JQTF/ofeT@enceladus \
--to=ilias.apalodimas@linaro.org \
--cc=dphadke@linux.microsoft.com \
--cc=johannes.holland@infineon.com \
--cc=masahisa.kojima@linaro.org \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@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