public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Marcel Selhorst <selhorst@crypto.rub.de>
Cc: linux-kernel@vger.kernel.org, Kylene Jo Hall <kjhall@us.ibm.com>
Subject: Re: [PATCH] tpm: Support for new chip type
Date: Tue, 5 Jul 2005 19:03:22 +0400	[thread overview]
Message-ID: <200507051903.22727.adobriyan@gmail.com> (raw)
In-Reply-To: <42CA81D4.5020906@crypto.rub.de>

On Tuesday 05 July 2005 16:49, Marcel Selhorst wrote:
> this patch supports the Infineon Trusted Platform Module SLD 9630 (TPM 1.1b),
> which is embedded on Intel-mainboards or in HP/Fujitsu-Siemens/Toshiba-Notebooks.

Please feed it to scripts/Lindent. It will at least place all curly bracers
right.

> --- linux-2.6.13-rc1-mm1/drivers/char/tpm/tpm_infineon.c
> +++ linux-2.6.13-rc-mm1-tpm_inf/drivers/char/tpm/tpm_infineon.c

> +/* Register */
> +enum tpm_register {

> +/* Command Bits */
> +enum tpm_command_bits {

> +/* Status Bits */
> +enum tpm_status_bits {

IMO, useless comments.

> +/* Global variable to count the Waiting-Time-Extensions */

Well, we see it's a variable and it's global in this file.

> +static int number_of_wtx = 0;	

You can also remove " = 0" and make it go to .bss.

> +static int empty_fifo(struct tpm_chip *chip, int clear_wrfifo) {

> +	int i=0;

Unneeded initialisation.

> +	/* Note: The Values which are currently in the FIFO of the TPM

values

> +	are thrown away since there is no usage for them. Usually,
> +	this has nothing to say, since the TPM will give its answer immidiately

immediately

> +	return(0);

return 0;

> +static int wait(struct tpm_chip *chip, int wait_for_bit) {

> +  int i = 0;

Unneeded initialisation.

> +  for (i = 0; i < TPM_MAX_TRIES; i++) {		/* Check the TPM_TIMEOUT-Variable in the definitions in Infineon.h */

There is no Infineon.h

> +  return(0);

return 0; everywhere, please.

> +static int tpm_inf_recv(struct tpm_chip *chip, u8 *buf, size_t count) {

> +	    return (size);

return size;

> +static struct attribute * inf_attrs[] = {
> +	0,

NULL

> +int __init tpm_inf_probe(struct pci_dev *pci_dev, const struct pci_device_id *pci_id) {

static

> +	    /* Finally, we're done, print some infos */	
> +	    dev_info(&pci_dev->dev,"************************************************\n");
> +	    dev_info(&pci_dev->dev,"*    TPM found with IO-Base 0x%x             *\n",tpm_inf.base);
> +	    dev_info(&pci_dev->dev,"*    Chip    ID %02x%02x                           *\n",version[0], version[1]);
> +	    dev_info(&pci_dev->dev,"*    Vendor  ID %x%x (Infineon)                *\n",vendor[0], vendor[1]);
> +	    if ((vendor[2] == 0) && (vendor[3] == 6))
> +		dev_info(&pci_dev->dev,"*    Product ID %02x%02x (SLD 9630 TT 1.1)         *\n",vendor[2],vendor[3]);
> +	    else
> +		dev_info(&pci_dev->dev,"*    Product ID %02x%02x                           *\n",vendor[2],vendor[3]);
> +	    dev_info(&pci_dev->dev,"************************************************\n");

Remove this silly banner.

	dev_info(&pci_dev->dev, ": TPM found: "
				"io base 0x%x, "
				"chip id %02x%02x, "
				"vendor id %x%x (Infineon), "
				"product id %02x%02x"
				"%s\n",
		tpm_inf.base,
		version[0], version[1],
		vendor[0], vendor[1],
		vendor[2],vendor[3],
		((vendor[2] == 0) && (vendor[3] == 6)) ? " (SLD 9630 TT 1.1)" : "");

should be enough. BTW, care to explain why something called "chip id" is in
something called "version" and something called "product id" in in something
called "vendor"?

> +	    /* Let's register our hardware */

Useless comment.

> +	    dev_dbg(&pci_dev->dev,"Registering TPM-Infineon-Driver: %x\n",rc);	

Will always print 0. Could you please also remove Studly Caps from debug, info
and error messages?

> +	    rc = tpm_register_hardware(pci_dev, &tpm_inf);	
> +	    if (rc < 0) {
> +		pci_disable_device(pci_dev);
> +		return -ENODEV;
> +	    }
> +	    return 0;
> +
> +	} else {
> +	    dev_err(&pci_dev->dev,": No Infineon TPM found! Sorry! \n");

Trailing space. Why be sorry? :-)

> +MODULE_AUTHOR("Marcel Selhorst (selhorst@crypto.rub.de)");

People usually enclose emails in <>.

  reply	other threads:[~2005-07-05 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 12:49 [PATCH] tpm: Support for new chip type Marcel Selhorst
2005-07-05 15:03 ` Alexey Dobriyan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-07 22:42 Marcel Selhorst
2005-07-08  6:54 ` Philipp Matthias Hahn
2005-07-08  7:16 ` Alexey Dobriyan
2005-07-09 19:19 ` Pavel Machek
2005-07-10 12:35   ` Vojtech Pavlik

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=200507051903.22727.adobriyan@gmail.com \
    --to=adobriyan@gmail.com \
    --cc=kjhall@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=selhorst@crypto.rub.de \
    /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