Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>,
	linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, gregkh@linuxfoundation.org,
	jens.wiklander@linaro.org, linux-integrity@vger.kernel.org,
	arnd@linaro.org, sumit.garg@linaro.org
Subject: Re: [PATCH 2/2] tpm_ftpm_tee: register driver on tee bus
Date: Mon, 18 May 2020 22:38:06 +0300
Message-ID: <e886d85baa24c09a6b571dd993e7450d5b16d48c.camel@linux.intel.com> (raw)
In-Reply-To: <20200518133459.28019-3-maxim.uvarov@linaro.org>

On Mon, 2020-05-18 at 16:34 +0300, Maxim Uvarov wrote:
> Register driver on tee bus. module tee registers bus,
> and module optee calls optee_enumerate_devices() to scan
> all devices on the bus. This TA can be Early TA's ( can be
> compiled into optee-os). In that case it will be on optee
> bus before linux booting. Also optee-suplicant application
> is needed to be loaded between optee module and ftpm module to
> to maintain functionality for ftpm driver.

Please use proper casing in the commit message e.g. tee to TEE
and so forth. What is TA?

/Jarkko


  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 13:34 [PATCH 0/2] optee: register drivers on optee bus Maxim Uvarov
2020-05-18 13:34 ` [PATCH 1/2] optee: do drivers initialization before and after tee-supplicant run Maxim Uvarov
2020-05-20  2:19   ` kbuild test robot
2020-05-21  5:49   ` [RFC PATCH] optee: __optee_enumerate_devices() can be static kbuild test robot
2020-05-18 13:34 ` [PATCH 2/2] tpm_ftpm_tee: register driver on tee bus Maxim Uvarov
2020-05-18 19:38   ` Jarkko Sakkinen [this message]
2020-05-19  7:09     ` Maxim Uvarov
2020-05-21  6:47 [PATCHv2 0/2] optee: register drivers on optee bus Maxim Uvarov
2020-05-21  6:47 ` [PATCH 2/2] tpm_ftpm_tee: register driver on tee bus Maxim Uvarov

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=e886d85baa24c09a6b571dd993e7450d5b16d48c.camel@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=arnd@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jens.wiklander@linaro.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxim.uvarov@linaro.org \
    --cc=peterhuewe@gmx.de \
    --cc=sumit.garg@linaro.org \
    --cc=tee-dev@lists.linaro.org \
    /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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org
	public-inbox-index linux-integrity

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git