Hi everyone,

Our company use Atmel TPM AT97SC3205 - SPI interface.
Accordingly to datasheests it's compliant to Trusted Computing Group (TCG) 
Trusted Platform Module TPM) Version 1.2 Specification. Compliant with TCG PC 
Client-Specific TPM Interface Specification (TIS Version 1.3).
On my target board I'm running Kernel from 
git://git.infradead.org/users/jjs/linux-tpmdd.git   next head.
I have made some additional changes on my Device Tree.

spi1: spi@fc000000 {
                pinctrl-names = "default";
                pinctrl-0 = <&pinctrl_spi1_default>;
                status = "okay";

                tpm_tis@0 {
                            compatible = "tcg,tpm_tis-spi";
                    reg = <0>;
                            spi-max-frequency = <10000000>;
                    };
            };

This is part of my kernel boot messages:
atmel_spi fc000000.spi: version: 0x311
atmel_spi fc000000.spi: Using dma0chan2 (tx) and dma0chan3 (rx) for DMA 
transfers
atmel_spi fc000000.spi: Using FIFO (16 data)
atmel_spi fc000000.spi: Atmel SPI Controller at 0xfc000000 (irq 36)
tpm tpm0: tpm_transmit: tpm_send: error -5
tpm_tis_spi: probe of spi32765.0 failed with error -5

I verified with an oscilloscope that all SPI bus signals are in order.

Following the above kernel boot messages - my question is :
    Can I use tpm_tis_spi device driver for AT97SC3205 device ?

Please advise and help with any directions.

Thanks in advance,
Alex Gershgorin





------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
tpmdd-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tpmdd-devel

Reply via email to