qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ninad Palsule <ninad@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	"Joel Stanley" <joel@jms.id.au>,
	"Ninad Palsule" <ninad@linux.ibm.com>
Cc: qemu-devel@nongnu.org, andrew@aj.id.au, stefanb@linux.ibm.com
Subject: Re: [PATCH v7 1/3] docs: Add support for TPM devices over I2C bus
Date: Mon, 27 Mar 2023 10:28:20 -0500	[thread overview]
Message-ID: <30895b98-fa50-65c3-d750-9ed960446073@linux.vnet.ibm.com> (raw)
In-Reply-To: <9d72b22b-9d53-8825-e7e1-fdcd9fa2d53d@kaod.org>


On 3/27/23 10:10 AM, Cédric Le Goater wrote:
>>>>> +In case a ast2600-evb bmc machine is emulated and want to use TPM 
>>>>> device
>>>>> +attached to I2C bus, use the following command line:
>>>>> +
>>>>> +.. code-block:: console
>>>>> +
>>>>> +  qemu-system-arm -M ast2600-evb -nographic \
>>>>> +    -kernel arch/arm/boot/zImage \
>>>>> +    -dtb arch/arm/boot/dts/aspeed-ast2600-evb.dtb \
>>>>> +    -initrd rootfs.cpio \
>>>>> +    -chardev socket,id=chrtpm,path=/tmp/mytpm1/swtpm-sock \
>>>>> +    -tpmdev emulator,id=tpm0,chardev=chrtpm \
>>>>> +    -device 
>>>>> tpm-tis-i2c,tpmdev=tpm0,bus=aspeed.i2c.bus.12,address=0x2e
>>>>
>>>> For testing, use this command to load the driver to the correct 
>>>> address:
>>>>
>>>> echo tpm_tis_i2c 0x2e > /sys/bus/i2c/devices/i2c-12/new_device
>>>>
>>>> (I don't know how specific we want to make the instructions, but
>>>> adding a line like above would help others from having to re-discover
>>>> the command).
>>>
>>> or/and add an avocado test for it. See tests/avocado/machine_aspeed.py.
>>>
>>> The avocado framework is a bit fragile when reading from the console 
>>> but
>>> we hope to fix that.
>>
>> I never used it before so it will take little longer.
>>
>> Is it required to merge this i2c work?
>
> It isn't.


Ok, Thanks. I will continue to check the test frame work and add the 
test in a separate drop.

Ninad

>
> C.
>
>
>


  reply	other threads:[~2023-03-27 15:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 22:44 [PATCH v7 0/3] Add support for TPM devices over I2C bus Ninad Palsule
2023-03-26 22:44 ` [PATCH v7 1/3] docs: " Ninad Palsule
2023-03-27  7:47   ` Joel Stanley
2023-03-27  7:52     ` Cédric Le Goater
2023-03-27 14:48       ` Ninad Palsule
2023-03-27 15:10         ` Cédric Le Goater
2023-03-27 15:28           ` Ninad Palsule [this message]
2023-03-27 13:04     ` Ninad Palsule
2023-03-26 22:44 ` [PATCH v7 2/3] tpm: Extend common APIs to support TPM TIS I2C Ninad Palsule
2023-03-27  0:14   ` Stefan Berger
2023-03-26 22:44 ` [PATCH v7 3/3] tpm: Add support for TPM device over I2C bus Ninad Palsule
2023-03-27 13:40   ` Stefan Berger
2023-03-27 15:54     ` Ninad Palsule
2023-03-27  1:05 ` [PATCH v7 0/3] Add support for TPM devices " Joel Stanley
2023-03-27  3:52   ` Ninad Palsule
2023-03-27  8:04     ` Joel Stanley
2023-03-27  8:20       ` Cédric Le Goater
2023-03-27 10:49         ` Joel Stanley
2023-03-27 11:17       ` Stefan Berger
2023-03-27 11:11   ` Stefan Berger
2023-03-27 11:18     ` Joel Stanley
2023-03-27 11:24       ` Stefan Berger
2023-03-27 12:31     ` Stefan Berger
2023-03-27 13:09       ` Stefan Berger

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=30895b98-fa50-65c3-d750-9ed960446073@linux.vnet.ibm.com \
    --to=ninad@linux.vnet.ibm.com \
    --cc=andrew@aj.id.au \
    --cc=clg@kaod.org \
    --cc=joel@jms.id.au \
    --cc=ninad@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.ibm.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).