All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Ricard <christophe.ricard@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] tpm: Initial work to introduce TPM driver model
Date: Thu, 13 Aug 2015 22:37:50 +0200	[thread overview]
Message-ID: <55CD001E.60307@gmail.com> (raw)
In-Reply-To: <CAPnjgZ1RLO0HWGqk1xqBihfS86Ze_Ax7Y37zxtK-TddkfRL6aA@mail.gmail.com>

Hi Simon,

On 13/08/2015 17:55, Simon Glass wrote:
> Hi Christophe,
>
> On 9 August 2015 at 07:19, Christophe Ricard
> <christophe.ricard@gmail.com> wrote:
>> drivers/tpm/tpm.c is a TPM core driver port from Linux.
>> So far in u-boot only infineon i2c driver is using it but it could fit
>> for others...
>>
>> Introduce a new tpm uclass so that every TPM driver can register against it and
>> and take benefit of common functions and data such as tpm_transmit,
>> tpm_register_hardware & tpm_remove_hardware.
>> Finally tis_init, tis_open, tis_close, tis_sendrecv are using ops allowing
>> to introduce proprietary instructions.
>> Also this patch convert tpm_i2c_infineon for using this tpm uclass.
>>
>> Signed-off-by: Christophe Ricard <christophe-h.ricard@st.com>
>> ---
>>
>>   README                                      |   8 +-
>>   drivers/tpm/Makefile                        |   2 +-
>>   drivers/tpm/tpm.c                           | 275 +++++++---------------------
>>   drivers/tpm/tpm_i2c_infineon.c              | 271 ++++++++++++++++-----------
>>   drivers/tpm/tpm_private.h                   |  23 ++-
>>   include/dm/platform_data/tpm_i2c_infineon.h |  23 +++
>>   include/dm/uclass-id.h                      |   1 +
>>   7 files changed, 270 insertions(+), 333 deletions(-)
>>   create mode 100644 include/dm/platform_data/tpm_i2c_infineon.h
> There is a lot going on in this patch - in general I think it is
> better to split things up so that each patch does one thing.
I understand. I have basically seen in your work more or less the same 
approach as far as TPM class.
I believe, according to your plan, i can wait for you to update you tree 
integrating my first comments on tpm-working branch or
if you prefer i can send a merge between your work and my comments.

What's your prefered option ?

Best Regards
Christophe
> Regards,
> Simon

  reply	other threads:[~2015-08-13 20:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-09 13:19 [U-Boot] [PATCH 0/3] Introduce TPM driver model and STMicroelectronics ST33ZP24 TPMs Christophe Ricard
2015-08-09 13:19 ` [U-Boot] [PATCH 1/3] tpm: Move tpm_tis_i2c to tpm_i2c_infineon Christophe Ricard
2015-08-13 15:55   ` Simon Glass
2015-08-30 22:45     ` Simon Glass
2015-09-02 17:54       ` Christophe Ricard
2015-09-08 14:20         ` Simon Glass
2015-08-09 13:19 ` [U-Boot] [PATCH 2/3] tpm: Initial work to introduce TPM driver model Christophe Ricard
2015-08-13 15:55   ` Simon Glass
2015-08-13 20:37     ` Christophe Ricard [this message]
2015-08-13 22:53       ` Simon Glass
2015-08-09 13:19 ` [U-Boot] [PATCH 3/3] tpm: Add st33zp24 tpm with i2c and spi phy Christophe Ricard
2015-08-13 15:55   ` Simon Glass
2015-08-13 20:59     ` Christophe Ricard
2015-08-13 22:53       ` Simon Glass
2015-08-09 13:28 ` [U-Boot] [PATCH 0/3] Introduce TPM driver model and STMicroelectronics ST33ZP24 TPMs Simon Glass
2015-08-09 14:19   ` Christophe Ricard
2015-08-09 15:12     ` 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=55CD001E.60307@gmail.com \
    --to=christophe.ricard@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.