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@xxxxxx 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
