From: Marc Kleine-Budde <mkl@pengutronix.de>
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 v6] peak_pci: add support for PEAK-System PCIe/PCIeC/miniPCI cards
Date: Mon, 13 Feb 2012 10:24:57 +0100 [thread overview]
Message-ID: <4F38D6E9.8060506@pengutronix.de> (raw)
In-Reply-To: <4F38D5F0.2070605@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]
On 02/13/2012 10:20 AM, Marc Kleine-Budde wrote:
> On 02/06/2012 04:46 PM, Stephane Grosjean wrote:
>> This patch adds the support for the following 3x sja1000 based PCI cards
>> from PEAK-System Technik (www.peak-system.com):
>>
>> PCAN-PCI Express (1 or 2 channels)
>> PCAN-ExpressCard (1 or 2 channels)
>> PCAN-miniPCI (1 or 2 channels)
>>
>> The PCAN-ExpressCard card needs I2C bit-banging interface, so it must be
>> explicitly selected. Doing this automatically selects I2C and I2C_ALGOBIT
>> bit-banging kernel configuration options.
>>
>> Signed-off-by: Stephane Grosjean <s.grosjean@peak-system.com>
>> Acked-by: Wolfgang Grandegger <wg@grandegger.com>
>> ---
>> v6 changes:
>> - the PCANExpressCard device id belongs to the module device id. table only if
>> the kernel is configured for (see CONFIG_CAN_PEAK_PCIEC)
>>
>> drivers/net/can/sja1000/Kconfig | 18 +-
>> drivers/net/can/sja1000/peak_pci.c | 509 +++++++++++++++++++++++++++++++++++-
>> 2 files changed, 510 insertions(+), 17 deletions(-)
>>
>> diff --git a/drivers/net/can/sja1000/Kconfig b/drivers/net/can/sja1000/Kconfig
>> index 36e9d59..8116336 100644
>> --- a/drivers/net/can/sja1000/Kconfig
>> +++ b/drivers/net/can/sja1000/Kconfig
>> @@ -44,11 +44,23 @@ config CAN_EMS_PCI
>> (http://www.ems-wuensche.de).
>>
>> config CAN_PEAK_PCI
>> - tristate "PEAK PCAN PCI/PCIe Cards"
>> + tristate "PEAK PCAN-PCI/PCIe/miniPCI Cards"
>> depends on PCI
>> ---help---
>> - This driver is for the PCAN PCI/PCIe cards (1, 2, 3 or 4 channels)
>> - from PEAK Systems (http://www.peak-system.com).
>> + This driver is for the PCAN-PCI/PCIe/miniPCI cards
>> + (1, 2, 3 or 4 channels) from PEAK-System Technik
>> + (http://www.peak-system.com).
>> +
>> +config CAN_PEAK_PCIEC
>> + bool "PEAK PCAN-ExpressCard Cards"
>
> Is there a particular reason to make this bool, why not tristate? Todays
> dekstop distros usually build everything modular.
Where's my brown paper bag - Sorry for the noise. :)
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2012-02-13 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 15:46 [PATCH v6] peak_pci: add support for PEAK-System PCIe/PCIeC/miniPCI cards Stephane Grosjean
2012-02-13 9:12 ` Marc Kleine-Budde
2012-02-13 9:20 ` Marc Kleine-Budde
2012-02-13 9:24 ` Marc Kleine-Budde [this message]
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=4F38D6E9.8060506@pengutronix.de \
--to=mkl@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).