linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grosjean Stephane <s.grosjean@peak-system.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Wolfgang Grandegger <wg@grandegger.com>,
	linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: Add support for PEAK PCMCIA PCAN-PC card
Date: Wed, 11 Jan 2012 15:11:29 +0100	[thread overview]
Message-ID: <4F0D9891.6070901@peak-system.com> (raw)
In-Reply-To: <4F0C53C6.1020704@hartkopp.net>



Le 10/01/2012 16:05, Oliver Hartkopp a écrit :
> On 10.01.2012 14:41, Wolfgang Grandegger wrote:
>
>> Nice, I have such a pcmcia card...
>
> Yes. Me too :-)

Happy to please you :-))

>
> +config CAN_PEAK_PCMCIA
> +	tristate "PEAK PCAN PC-CARD Card"
>
> tristate "PEAK PCAN PC-Card (PCMCIA)"
>
> ??

Please confirm: you'd like me to add the "(PCMCIA)" string at the end of 
the menu text, wouldn't you?

> Should we probably put all PCMCIA cards into a separate
>
> linux/drivers/net/can/sja1000/pcmcia
>
> directory - like we have it for the USB devices?

If my Humble Opinion may help you: not sure this will be lots of other 
pcmcia (can) adapters in the future...

>>> +	depends on PCMCIA
>>> +	---help---
>>> +	  This driver is for the PCAN PC-CARD PCMCIA card with 1 or 2 channels
>>> +	  from PEAK Systems (http://www.peak-system.com).
>>> +
>>>   config CAN_PEAK_PCI
>>>   	tristate "PEAK PCAN PCI/PCIe Cards"
>>>   	depends on PCI
>>> diff --git a/drivers/net/can/sja1000/Makefile b/drivers/net/can/sja1000/Makefile
>>> index 0604f24..b3d05cb 100644
>>> --- a/drivers/net/can/sja1000/Makefile
>>> +++ b/drivers/net/can/sja1000/Makefile
>>> @@ -9,6 +9,7 @@ obj-$(CONFIG_CAN_SJA1000_OF_PLATFORM) += sja1000_of_platform.o
>>>   obj-$(CONFIG_CAN_EMS_PCMCIA) += ems_pcmcia.o
>>>   obj-$(CONFIG_CAN_EMS_PCI) += ems_pci.o
>>>   obj-$(CONFIG_CAN_KVASER_PCI) += kvaser_pci.o
>>> +obj-$(CONFIG_CAN_PEAK_PCMCIA) += peak_pcmcia.o
>
> This should be the module/driver name too.
>>> +
>>> +/* PEAK-System PCMCIA driver name */
>>> +#define DRV_NAME "peak_pccard"
>> I find the mix of "peak_pcmcia" and "peak_pccard" and "pcan_pccard" for
>> the same hardware confusing. Please use just one name and prefix.
>
> Yep - peak_pcmcia

We just finished to talk about that and, as far as the PCAN-PC Card is a 
PC-CARD (16bit), we'd like to use the "peak_pccard" text for the 
module/module file/source file names instead of "peak_pcmcia".
Related question: I suppose I'll have to change the 
"CONFIG_CAN_PEAK_PCMCIA" into "CONFIG_CAN_PEAK_PCCARD" too.
Please confirm.

> +
> +#define DRV_CHAN_MAX 2
> +
> +#define DRV_CAN_CLOCK (16000000 / 2)
>> Hm, the prefix DRV_ here and below does not really make sense. But well,
>> it's a minor issue.
>
> ack. Remove DRV_ or rename it so someting like to PCC_

Ok, changed to "PCC_" prefix.

> No more nitpicks in additions to Wolfgangs remarks.

Just one last question: FYI, I built the peak_pcmcia.c starting from 
peak_pci.c, so I suppose that the DRV_ prefix should be changed into 
that file too.

> Tnx&  best regards,
> Oliver

Many thanks for all!

Best regards,

Stéphane


  reply	other threads:[~2012-01-11 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 14:51 Add support for PEAK PCMCIA PCAN-PC card Stephane Grosjean
2012-01-09 23:23 ` Marc Kleine-Budde
2012-01-11 15:13   ` Grosjean Stephane
2012-01-10 13:41 ` Wolfgang Grandegger
2012-01-10 15:05   ` Oliver Hartkopp
2012-01-11 14:11     ` Grosjean Stephane [this message]
2012-01-11 14:43       ` Wolfgang Grandegger
2012-01-11 15:00       ` Oliver Hartkopp
2012-01-11 15:11         ` Wolfgang Grandegger
2012-01-11 17:10   ` Grosjean Stephane
2012-01-11 18:35     ` Wolfgang Grandegger

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=4F0D9891.6070901@peak-system.com \
    --to=s.grosjean@peak-system.com \
    --cc=linux-can@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.com \
    /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).