From: Wolfgang Grandegger <wg@grandegger.com>
To: Stephane Grosjean <s.grosjean@peak-system.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: [PATCH] can/sja1000: Add miniPCIe/cPCI PC/104Plus PCI/104e PEAK-System boards
Date: Wed, 24 Oct 2012 08:29:45 +0200 [thread overview]
Message-ID: <50878AD9.6070302@grandegger.com> (raw)
In-Reply-To: <1350988637-13581-1-git-send-email-s.grosjean@peak-system.com>
Hi Stephane,
On 10/23/2012 12:37 PM, Stephane Grosjean wrote:
> This patch adds the support for 4 new PCI boards based on the SJA1000 CAN
> controller, from PEAK-System Technik:
>
> . PCAN-miniPCIe (PCI-Express Mini slots, available as single or dual-channel)
> . PCAN-cPCI (CompactPCI format, available as single or dual-channel)
> . PCAN-PC/104-Plus (PC/104-Plus system, av. as 1, 2 or 4 channels)
> . PCAN-PCI/104-Express (PCI/104-Express system, av. as 1 or 2 channels)
>
> This patch also fixes a typo in existing "PEAK_MPCI_DEVICE_ID" identifier
> (missing "E" for Express). Finally, it also adds another author as well as it
> updates the module supported devices list.
>
> Signed-off-by: Stephane Grosjean <s.grosjean@peak-system.com>
> ---
> drivers/net/can/sja1000/peak_pci.c | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/can/sja1000/peak_pci.c b/drivers/net/can/sja1000/peak_pci.c
> index f0a1296..15a302e 100644
> --- a/drivers/net/can/sja1000/peak_pci.c
> +++ b/drivers/net/can/sja1000/peak_pci.c
> @@ -31,8 +31,10 @@
> #include "sja1000.h"
>
> MODULE_AUTHOR("Wolfgang Grandegger <wg@grandegger.com>");
> +MODULE_AUTHOR("Stephane Grosjean <s.grosjean@peak-system.com>");
Hm, does adding a second MODULE_AUTHOR work? Anyway, feel free to remove
my line.
> MODULE_DESCRIPTION("Socket-CAN driver for PEAK PCAN PCI family cards");
> MODULE_SUPPORTED_DEVICE("PEAK PCAN PCI/PCIe/PCIeC miniPCI CAN cards");
> +MODULE_SUPPORTED_DEVICE("PEAK PCAN miniPCIe/cPCI PC/104+ PCI/104e CAN Cards");
> MODULE_LICENSE("GPL v2");
>
> #define DRV_NAME "peak_pci"
> @@ -64,7 +66,11 @@ struct peak_pci_chan {
> #define PEAK_PCI_DEVICE_ID 0x0001 /* for PCI/PCIe slot cards */
> #define PEAK_PCIEC_DEVICE_ID 0x0002 /* for ExpressCard slot cards */
> #define PEAK_PCIE_DEVICE_ID 0x0003 /* for nextgen PCIe slot cards */
> -#define PEAK_MPCI_DEVICE_ID 0x0008 /* The miniPCI slot cards */
> +#define PEAK_CPCI_DEVICE_ID 0x0004 /* for nextgen cPCI slot cards */
> +#define PEAK_MPCI_DEVICE_ID 0x0005 /* for nextgen miniPCI slot cards */
> +#define PEAK_PC_104P_DEVICE_ID 0x0006 /* PCAN-PC/104+ cards */
> +#define PEAK_PCI_104E_DEVICE_ID 0x0007 /* PCAN-PCI/104 Express cards */
> +#define PEAK_MPCIE_DEVICE_ID 0x0008 /* The miniPCIe slot cards */
>
> #define PEAK_PCI_CHAN_MAX 4
>
> @@ -76,6 +82,10 @@ static DEFINE_PCI_DEVICE_TABLE(peak_pci_tbl) = {
> {PEAK_PCI_VENDOR_ID, PEAK_PCI_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> {PEAK_PCI_VENDOR_ID, PEAK_PCIE_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> {PEAK_PCI_VENDOR_ID, PEAK_MPCI_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> + {PEAK_PCI_VENDOR_ID, PEAK_MPCIE_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> + {PEAK_PCI_VENDOR_ID, PEAK_PC_104P_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> + {PEAK_PCI_VENDOR_ID, PEAK_PCI_104E_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> + {PEAK_PCI_VENDOR_ID, PEAK_CPCI_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> #ifdef CONFIG_CAN_PEAK_PCIEC
> {PEAK_PCI_VENDOR_ID, PEAK_PCIEC_DEVICE_ID, PCI_ANY_ID, PCI_ANY_ID,},
> #endif
Acked-by: Wolfgang Grandegger <wg@grandegger.com>
Thanks,
Wolfgang.
next prev parent reply other threads:[~2012-10-24 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 10:37 [PATCH] can/sja1000: Add miniPCIe/cPCI PC/104Plus PCI/104e PEAK-System boards Stephane Grosjean
2012-10-23 16:56 ` Oliver Hartkopp
2012-10-24 6:29 ` Wolfgang Grandegger [this message]
[not found] ` <508A4369.9010301@peak-system.com>
2012-10-26 8:11 ` Marc Kleine-Budde
2012-10-24 9:08 ` Marc Kleine-Budde
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=50878AD9.6070302@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-can@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
--cc=socketcan@hartkopp.net \
/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.