From: Matthieu CASTET <castet.matthieu@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6 of 6] tpm: move infineon driver off pci_dev
Date: Tue, 25 Oct 2005 22:17:30 +0200 [thread overview]
Message-ID: <pan.2005.10.25.20.17.26.57688@free.fr> (raw)
In-Reply-To: <1130253738.4839.65.camel@localhost.localdomain>
Hi,
nice to see that the tpm framework was cleanned.
Le Tue, 25 Oct 2005 10:22:18 -0500, Kylene Jo Hall a écrit :
> ---
>
> --- linux-2.6.14-rc4/drivers/char/tpm/tpm_infineon.c 2005-10-19 17:03:52.000000000 -0500
> +++ linux-2.6.13-tpm/drivers/char/tpm/tpm_infineon.c 2005-10-21 13:07:24.000000000 -0500
> @@ -14,6 +14,7 @@
> * License.
> */
>
> +#include <acpi/acpi_bus.h>
Why is it needed ?
> -/* These values will be filled after PnP-call */
> +/* These values will be filled after ACPI-call */
Why not keep PnP ?
> -MODULE_DEVICE_TABLE(pnp, tpm_pnp_tbl);
>
Why removing that ?
This will allow hotplug and udev to auto load the module.
> +
> + /* read IO-ports from ACPI */
> + TPM_INF_ADDR = (pnp_port_start(dev, 0) & 0xff);
> + TPM_INF_DATA = ((TPM_INF_ADDR + 1) & 0xff);
No need to set mask, this is already done by pnp_port_start.
And I'll keep PNP instead of ACPI.
> + tpm_inf.base = pnp_port_start(dev, 1);
Can't you be coherent ?
why not using tpm_inf.addr
or TPM_INF_BASE ?
> + dev_info(&dev->dev, "Found %s with ID %s\n",
> + dev->name, dev_id->id);
> + if (!((tpm_inf.base >> 8) & 0xff))
> + tpm_inf.base = 0;
>
> /* Make sure, we have received valid config ports */
You should also do :
pnp_port_flags(device, 0) & IORESOURCE_DISABLED) in order to check the
resources.
> + .probe = tpm_inf_acpi_probe,
> + .remove = tpm_inf_remove,
Not coherent : acpi vs nothing.
Again prefer pnp instead of acpi.
Matthieu
next prev parent reply other threads:[~2005-10-25 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 15:22 Kylene Jo Hall
2005-10-25 20:17 ` Matthieu CASTET [this message]
2005-10-25 20:46 ` Kylene Jo Hall
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=pan.2005.10.25.20.17.26.57688@free.fr \
--to=castet.matthieu@free.fr \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®