From: Kent Yoder <key@linux.vnet.ibm.com>
To: Mathias LEBLANC <Mathias.LEBLANC@st.com>
Cc: Rajiv Andrade <mail@srajiv.net>,
Marcel Selhorst <tpmdd@selhorst.net>,
Sirrix AG <tpmdd@sirrix.com>,
"tpmdd-devel@lists.sourceforge.net"
<tpmdd-devel@lists.sourceforge.net>,
Debora Velarde <debora@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jean-Luc BLANC <jean-luc.blanc@st.com>
Subject: Re: [PATCH 1/1] TPM: STMicroelectronics ST33 I2C
Date: Mon, 26 Nov 2012 09:51:48 -0600 [thread overview]
Message-ID: <20121126155148.GA10104@ennui.austin.ibm.com> (raw)
In-Reply-To: <35286B1AE75A7C47BFF0870081A31B4B3A990A7BE0@SAFEX1MAIL4.st.com>
On Tue, Nov 20, 2012 at 09:26:40AM +0100, Mathias LEBLANC wrote:
> Hello,
>
> Does anyone can say me when the driver will be integrated on linux kernel and where can we get it from the linux source code?
Hi Mathias, I'll work with you this week to get this pushed to the
security-next tree. From there the code is pushed to Linus' tree.
Kent
> Thanks,
>
> Mathias Leblanc
>
> -----Original Message-----
> From: Kent Yoder [mailto:key@linux.vnet.ibm.com]
> Sent: 14 November, 2012 23:07
> To: Mathias LEBLANC
> Cc: Rajiv Andrade; Marcel Selhorst; Sirrix AG; tpmdd-devel@lists.sourceforge.net; Debora Velarde; linux-kernel@vger.kernel.org; Jean-Luc BLANC
> Subject: Re: [PATCH 1/1] TPM: STMicroelectronics ST33 I2C
>
> Hi Mathias,
>
> On Wed, Nov 14, 2012 at 03:31:42PM +0100, Mathias Leblanc wrote:
> > * STMicroelectronics version 1.2.0, Copyright (C) 2010
> > * STMicroelectronics comes with ABSOLUTELY NO WARRANTY.
> > * This is free software, and you are welcome to redistribute it
> > * under certain conditions.
> >
> > This is the driver for TPM chip from ST Microelectronics.
> >
> > If you have a TPM security chip from STMicroelectronics working with
> > an I2C, in menuconfig or .config choose the tpm driver on device -->
> > tpm and activate the protocol of your choice before compiling the
> > kernel.
> > The driver will be accessible from within Linux.
> >
> > Tested on linux x86/x64, beagleboard REV B & XM REV C and CHROMIUM OS
>
> Getting some build errors here:
>
> drivers/char/tpm/tpm_stm_st33_i2c.c: In function ‘__check_interrupts’:
> drivers/char/tpm/tpm_stm_st33_i2c.c:615:1: warning: return from incompatible pointer type [enabled by default]
> drivers/char/tpm/tpm_stm_st33_i2c.c: In function ‘__check_power_mgt’:
> drivers/char/tpm/tpm_stm_st33_i2c.c:619:1: warning: return from incompatible pointer type [enabled by default]
> drivers/char/tpm/tpm_stm_st33_i2c.c: In function ‘tpm_st33_i2c_probe’:
> drivers/char/tpm/tpm_stm_st33_i2c.c:725:3: warning: suggest parentheses around arithmetic in operand of ‘|’ [-Wparentheses]
> drivers/char/tpm/tpm_stm_st33_i2c.c: In function
> ‘tpm_st33_i2c_pm_suspend’:
> drivers/char/tpm/tpm_stm_st33_i2c.c:826:3: error: too many arguments to function ‘tpm_pm_suspend’
> In file included from drivers/char/tpm/tpm_stm_st33_i2c.h:55:0,
> from drivers/char/tpm/tpm_stm_st33_i2c.c:35:
> drivers/char/tpm/tpm.h:326:12: note: declared here
> drivers/char/tpm/tpm_stm_st33_i2c.c: In function
> ‘tpm_st33_i2c_pm_resume’:
> drivers/char/tpm/tpm_stm_st33_i2c.c:855:3: error:
> implicit declaration of function
> ‘tpm_continue_selftest’
> [-Werror=implicit-function-declaration]
>
> [cut]
> > +/*
> > + * _wait_for_interrupt_serirq_timeout
> > + * @param: tpm, the chip description
> > + * @param: timeout, the timeout of the interrupt
> > + * @return: the status of the interruption.
> > + */
> > +static int _wait_for_interrupt_serirq_timeout(struct tpm_chip *chip,
> > + unsigned long timeout)
> > +{
> > + int status;
> > + struct i2c_client *client;
> > + struct st33zp24_platform_data *pin_infos;
> > +
> > + client = (struct i2c_client *) chip->vendor.iobase;
> > + pin_infos = client->dev.platform_data;
> > +
> > + status = wait_for_completion_interruptible_timeout(
> > + &pin_infos->irq_detection,
> > + timeout);
>
> status should be a long here.
>
> [cut]
> > +
> > + if (client == NULL) {
> > + pr_info("client is NULL. exiting.\n");
> > + err = -ENODEV;
> > + goto end;
> > + }
> > +
> > + if (!i2c_check_functionality(client->adapter, I2C_FUNC_I2C)) {
> > + pr_info("client not i2c capable\n");
> > + err = -ENODEV;
> > + goto end;
> > + }
> > +
> > + chip = tpm_register_hardware(&client->dev, &st_i2c_tpm);
> > + if (!chip) {
> > + pr_info("fail chip\n");
>
> Please use dev_info() in place of pr_info().
>
> Thanks,
> Kent
>
next prev parent reply other threads:[~2012-11-26 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 14:31 [PATCH 1/1] TPM: STMicroelectronics ST33 I2C Mathias Leblanc
2012-11-14 14:31 ` [PATCH 1/1] TPM: STMicroelectronics ST33 I2C CHROMIUM Mathias Leblanc
2012-11-14 14:31 ` [PATCH 1/1] TPM: STMicroelectronics ST33 I2C BUILD STUFF Mathias Leblanc
2012-11-14 22:06 ` [PATCH 1/1] TPM: STMicroelectronics ST33 I2C Kent Yoder
2012-11-19 13:48 ` Mathias LEBLANC
2012-11-20 8:26 ` Mathias LEBLANC
2012-11-26 15:51 ` Kent Yoder [this message]
2012-11-26 16:03 ` Mathias LEBLANC
-- strict thread matches above, loose matches on Subject: below --
2012-11-07 12:15 Mathias Leblanc
2012-11-07 15:02 ` Kent Yoder
2012-11-07 15:23 ` Mathias LEBLANC
2012-11-07 17:45 ` Kent Yoder
2012-11-12 9:28 ` Mathias LEBLANC
2012-10-30 13:28 Mathias Leblanc
2012-10-31 14:37 ` Kent Yoder
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=20121126155148.GA10104@ennui.austin.ibm.com \
--to=key@linux.vnet.ibm.com \
--cc=Mathias.LEBLANC@st.com \
--cc=debora@linux.vnet.ibm.com \
--cc=jean-luc.blanc@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@srajiv.net \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
--cc=tpmdd@sirrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.