From: "christophe.ricard" <christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Peter Hüwe" <PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
Cc: ashley-fm2HMyfA2y6tG0bUXCXiUA@public.gmane.org,
tpmdd-yWjUBOtONefk1uMJSBkQmQ@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
christophe-h.ricard-qxv4g6HH51o@public.gmane.org,
jean-luc.blanc-qxv4g6HH51o@public.gmane.org,
benoit.houyere-qxv4g6HH51o@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org,
jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: [PATCH v4 0/4] st33zp24 new architecture proposal and st33zp24 spi driver
Date: Mon, 26 Jan 2015 23:11:48 +0100 [thread overview]
Message-ID: <54C6BBA4.1010208@gmail.com> (raw)
In-Reply-To: <201501262239.25303.PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
Hi Peter,
Thanks for your time.
I think it will be fine to wait for kernel 3.21.
Best Regards
Christophe
On 26/01/2015 22:39, Peter Hüwe wrote:
> Hi Christophe,
>
> Am Sonntag, 25. Januar 2015, 22:11:29 schrieb Christophe Ricard:
>> Hi,
>>
>> The following patchset:
>> - propose a new architecture allowing to share a core st33zp24 data
>> management layer with different phy (i2c & spi). For st33zp24 both phy
>> have a proprietary transport protocol. Both are relying on the TCG TIS
>> protocol. At the end, it simplifies the maintenance. - Add an spi phy
>> allowing to support st33zp24 using with an SPI bus.
>>
>> The complete solution got tested in polling and interrupt mode successfully
>> with i2c & spi phy. This patchset applies on top of Peter's tree
>> https://github.com/PeterHuewe/linux-tpmdd.git for-james branch on top of:
>> d4989d9f693b9502f9288da5db279c2f8c2e50be tpm/tpm_tis: Add missing ifdef
>> CONFIG_ACPI for pnp_acpi_device
>>
>> I confirm also Jarkko Sakkinen's changes are working with this product with
>> both phy's.
>>
>> - v2 takes into account feedbacks from Jason Gunthorpe.
>> - v3 is reduced to 4 patches as 6 out of 10 got accepted for 3.20. Also
>> compare to v2: * Fix build issue with patch v2 04/10 "Replace access to
>> io_lpcpd from struct st33zp24_platform_data to tpm_stm_dev" * Fix link
>> issue with patch v2 08/10 "Split tpm_i2c_tpm_st33 in 2 layers (core +
>> phy)" when building as a module. The symbols wasn't exported in
>> st33zp24.c.
>> * Add missing MODULE_LICENSE in patch v2 09/10 "Add st33zp24 spi
>> phy" * Fix node example in dts spi documentation in patch v2 10/10 "Add
>> dts documentation for st33zp24 spi phy" * Fix typo on Jason Gunthorpe
>> first name. Sorry for that :(... * Change contact email address as
>> tpmsupport-qxv4g6HH51o@public.gmane.org is no more valid - v4 adds missing module_license in
>> st33zp24
> I'll review the stuff (since I cannot test :) during the next few days.
> Meanwhile I added to my 'staging tree'
> https://github.com/PeterHuewe/linux-tpmdd/tree/testing-and-review
>
> I doubt that James will accept it for 3.20.
>
> Thanks,
> Peter
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-01-26 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 21:11 [PATCH v4 0/4] st33zp24 new architecture proposal and st33zp24 spi driver Christophe Ricard
[not found] ` <1422220293-21005-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2015-01-25 21:11 ` [PATCH v4 1/4] tpm/tpm_i2c_stm_st33: Replace access to io_lpcpd from struct st33zp24_platform_data to tpm_stm_dev Christophe Ricard
[not found] ` <1422220293-21005-2-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2015-01-26 22:15 ` Peter Hüwe
[not found] ` <201501262315.07543.PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
2015-01-26 22:18 ` christophe.ricard
2015-01-25 21:11 ` [PATCH v4 2/4] tpm/tpm_i2c_stm_st33: Split tpm_i2c_tpm_st33 in 2 layers (core + phy) Christophe Ricard
[not found] ` <1422220293-21005-3-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2015-01-26 23:07 ` Peter Hüwe
2015-01-25 21:11 ` [PATCH v4 3/4] tpm/st33zp24/spi: Add st33zp24 spi phy Christophe Ricard
[not found] ` <1422220293-21005-4-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2015-01-26 23:28 ` Peter Hüwe
2015-01-25 21:11 ` [PATCH v4 4/4] tpm/st33zp24/dts/st33zp24-spi: Add dts documentation for " Christophe Ricard
2015-01-26 21:39 ` [PATCH v4 0/4] st33zp24 new architecture proposal and st33zp24 spi driver Peter Hüwe
[not found] ` <201501262239.25303.PeterHuewe-Mmb7MZpHnFY@public.gmane.org>
2015-01-26 22:11 ` christophe.ricard [this message]
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=54C6BBA4.1010208@gmail.com \
--to=christophe.ricard-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=PeterHuewe-Mmb7MZpHnFY@public.gmane.org \
--cc=ashley-fm2HMyfA2y6tG0bUXCXiUA@public.gmane.org \
--cc=benoit.houyere-qxv4g6HH51o@public.gmane.org \
--cc=christophe-h.ricard-qxv4g6HH51o@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=jean-luc.blanc-qxv4g6HH51o@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tpmdd-yWjUBOtONefk1uMJSBkQmQ@public.gmane.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
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).