linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephane Grosjean <s.grosjean@peak-system.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: [PATCH v4.3] peak_pci: add support for PEAK-System PCIe/PCIeC/miniPCI cards
Date: Fri, 03 Feb 2012 11:14:49 +0100	[thread overview]
Message-ID: <4F2BB399.9000802@peak-system.com> (raw)
In-Reply-To: <4F2B16F9.8020903@hartkopp.net>

Le 03/02/2012 00:06, Oliver Hartkopp a écrit :
> On 02.02.2012 19:03, Oliver Hartkopp wrote:
>
>> The problem is that the PCAN-ExpressCards without galvanic isolation
>> (IPEH-003000, IPEH-003001) are not working at all when the I2C stuff is not
>> initialized.
>>
>> It's not only the LED handling.

Yes you're right: the existing code already enables the can transceiver, 
but I forgot that it used a led pin, sorry.

>> Alternatively you may just select I2C and I2C_ALGOBIT as it is done by other
>> drivers like this:
>>
>> http://lxr.linux.no/#linux+v3.2.2/drivers/net/ethernet/sfc/Kconfig#L7
>>
>> config CAN_PEAK_PCI
>> 	tristate "PEAK PCAN-PCI/PCIe/PCIeC/miniPCI Cards"
>> 	depends on PCI
>> 	select I2C
>> 	select I2C_ALGOBIT
>> 	---help---
>> 	  This driver is for the PCAN-PCI/PCIe/PCIeC/miniPCI cards
>> 	  (1, 2, 3 or 4 channels) from PEAK-System Technik
>> 	  (http://www.peak-system.com).
>>
>> ... which would also make the #ifdef stuff obsolete.

Well, if this is used in an already existing driver, we can suppose that 
this is the correct way to do that.
I personally prefer the "select" way of doing things rather than the 
"depends on".

Do someone disagree with?

Moreover, no response about my question of yesterday: since I have to 
post another (pcmcia) driver for the sja1000 subdir (and thus, change 
the Kconfig again), the best solution would be to post all through a 
serie of patches, wouldn't it?

Thanks for your reply,

Stéphane

--
PEAK-System Technik GmbH, Otto-Roehm-Strasse 69, D-64293 Darmstadt 
Geschaeftsleitung: A.Gach/U.Wilhelm,St.Nr.:007/241/13586 FA Darmstadt 
HRB-9183 Darmstadt, Ust.IdNr.:DE 202220078, WEE-Reg.-Nr.: DE39305391 
Tel.+49 (0)6151-817320 / Fax:+49 (0)6151-817329, info@peak-system.com

  reply	other threads:[~2012-02-03 10:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 13:19 [PATCH v4.3] peak_pci: add support for PEAK-System PCIe/PCIeC/miniPCI cards Stephane Grosjean
2012-02-02 18:03 ` Oliver Hartkopp
2012-02-02 23:06   ` Oliver Hartkopp
2012-02-03 10:14     ` Stephane Grosjean [this message]
2012-02-03 10:19     ` Wolfgang Grandegger
2012-02-03 10:44       ` Stephane Grosjean
2012-02-03 10:59         ` Wolfgang Grandegger
2012-02-03 11:34           ` Stephane Grosjean
2012-02-03 12:01           ` Stephane Grosjean
2012-02-03 12:28             ` Wolfgang Grandegger
2012-02-03 13:02               ` Stephane Grosjean
2012-02-03 12:09           ` Stephane Grosjean

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=4F2BB399.9000802@peak-system.com \
    --to=s.grosjean@peak-system.com \
    --cc=linux-can@vger.kernel.org \
    --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).