X-Git-Url: http://rtime.felk.cvut.cz/gitweb/lincan.git/blobdiff_plain/ce93567bb929614d283a248bc8dbf4caec26e59b..9c8ab08d7e8fca3916a7f91a3c001d151989137c:/lincan/src/bfadcan.c diff --git a/lincan/src/bfadcan.c b/lincan/src/bfadcan.c index 78c7660..5557ca1 100644 --- a/lincan/src/bfadcan.c +++ b/lincan/src/bfadcan.c @@ -1,17 +1,36 @@ -/* bfadcan.c - * Linux CAN-bus device driver. - * Written by Arnaud Westenberg email:arnaud@wanadoo.nl - * Rewritten for new CAN queues by Pavel Pisa - OCERA team member - * email:pisa@cmp.felk.cvut.cz - * This software is released under the GPL-License. - * Version lincan-0.3 17 Jun 2004 - */ - -/* This file is intended as a bfadcan file for currently unsupported hardware. - * Once you've changed/added the functions specific to your hardware it is - * possible to load the driver with the hardware option hw=bfadcan. - */ - +/**************************************************************************/ +/* File: bfadcan.c - support for BFAD can boards */ +/* */ +/* LinCAN - (Not only) Linux CAN bus driver */ +/* Copyright (C) 2002-2009 DCE FEE CTU Prague */ +/* Copyright (C) 2002-2009 Pavel Pisa */ +/* Funded by OCERA and FRESCOR IST projects */ +/* Based on CAN driver code by Arnaud Westenberg */ +/* */ +/* LinCAN is free software; you can redistribute it and/or modify it */ +/* under terms of the GNU General Public License as published by the */ +/* Free Software Foundation; either version 2, or (at your option) any */ +/* later version. LinCAN is distributed in the hope that it will be */ +/* useful, but WITHOUT ANY WARRANTY; without even the implied warranty */ +/* of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU */ +/* General Public License for more details. You should have received a */ +/* copy of the GNU General Public License along with LinCAN; see file */ +/* COPYING. If not, write to the Free Software Foundation, 675 Mass Ave, */ +/* Cambridge, MA 02139, USA. */ +/* */ +/* To allow use of LinCAN in the compact embedded systems firmware */ +/* and RT-executives (RTEMS for example), main authors agree with next */ +/* special exception: */ +/* */ +/* Including LinCAN header files in a file, instantiating LinCAN generics */ +/* or templates, or linking other files with LinCAN objects to produce */ +/* an application image/executable, does not by itself cause the */ +/* resulting application image/executable to be covered by */ +/* the GNU General Public License. */ +/* This exception does not however invalidate any other reasons */ +/* why the executable file might be covered by the GNU Public License. */ +/* Publication of enhanced or derived LinCAN files is required although. */ +/**************************************************************************/ #define WINDOWED_ACCESS @@ -23,12 +42,11 @@ #define __NO_VERSION__ #include -long clock_freq; -MODULE_PARM(clock_freq,"i"); +#define CAN_BFAD_CLOCKFREQ 20000000 /* cli and sti are not allowed in 2.5.5x SMP kernels */ #ifdef WINDOWED_ACCESS -static can_spinlock_t bfadcan_win_lock=SPIN_LOCK_UNLOCKED; +static CAN_DEFINE_SPINLOCK(bfadcan_win_lock); #endif /* @@ -42,8 +60,8 @@ static can_spinlock_t bfadcan_win_lock=SPIN_LOCK_UNLOCKED; #define IO_RANGE 0x100 #endif -unsigned bfadcan_read_register(unsigned long address); -void bfadcan_write_register(unsigned data, unsigned long address); +unsigned bfadcan_read_register(can_ioptr_t address); +void bfadcan_write_register(unsigned data, can_ioptr_t address); /** @@ -53,7 +71,7 @@ void bfadcan_write_register(unsigned data, unsigned long address); * * The function bfadcan_request_io() is used to reserve the io-memory. If your * hardware uses a dedicated memory range as hardware control registers you - * will have to add the code to reserve this memory as well. + * will have to add the code to reserve this memory as well. * %IO_RANGE is the io-memory range that gets reserved, please adjust according * your hardware. Example: #define IO_RANGE 0x100 for i82527 chips or * #define IO_RANGE 0x20 for sja1000 chips in basic CAN mode. @@ -94,8 +112,8 @@ int bfadcan_release_io(struct candevice_t *candev) * bfadcan_reset - hardware reset routine * @candev: Pointer to candevice/board structure * - * The function bfadcan_reset() is used to give a hardware reset. This is - * rather hardware specific so I haven't included example code. Don't forget to + * The function bfadcan_reset() is used to give a hardware reset. This is + * rather hardware specific so I haven't included example code. Don't forget to * check the reset status of the chip before returning. * Return Value: The function returns zero on success or %-ENODEV on failure * File: src/bfadcan.c @@ -106,10 +124,10 @@ int bfadcan_reset(struct candevice_t *candev) int i; struct canchip_t *chip=candev->chip[0]; unsigned cdr; - + bfadcan_write_register(sjaMOD_RM, chip->chip_base_addr+SJAMOD); udelay(1000); - + cdr=bfadcan_read_register(chip->chip_base_addr+SJACDR); bfadcan_write_register(cdr|sjaCDR_PELICAN, chip->chip_base_addr+SJACDR); @@ -127,7 +145,7 @@ int bfadcan_reset(struct candevice_t *candev) bfadcan_write_register(cdr|sjaCDR_PELICAN, chip->chip_base_addr+SJACDR); bfadcan_write_register(0, chip->chip_base_addr+SJAIER); - + return 0; } @@ -149,7 +167,7 @@ int bfadcan_reset(struct candevice_t *candev) * Return Value: The function always returns zero * File: src/bfadcan.c */ -int bfadcan_init_hw_data(struct candevice_t *candev) +int bfadcan_init_hw_data(struct candevice_t *candev) { candev->res_addr=RESET_ADDR; candev->nr_82527_chips=NR_82527; @@ -183,7 +201,7 @@ int bfadcan_init_hw_data(struct candevice_t *candev) * The entry @int_clk_reg holds hardware specific options for the Clock Out * register. Options defined in the %i82527.h file: * %iCLK_CD0, %iCLK_CD1, %iCLK_CD2, %iCLK_CD3, %iCLK_SL0, %iCLK_SL1. - * The entry @int_bus_reg holds hardware specific options for the Bus + * The entry @int_bus_reg holds hardware specific options for the Bus * Configuration register. Options defined in the %i82527.h file: * %iBUS_DR0, %iBUS_DR1, %iBUS_DT1, %iBUS_POL, %iBUS_CBY. * The entry @int_cpu_reg holds hardware specific options for the cpu interface @@ -196,17 +214,18 @@ int bfadcan_init_chip_data(struct candevice_t *candev, int chipnr) { unsigned int id1, id2; sja1000p_fill_chipspecops(candev->chip[chipnr]); - candev->chip[chipnr]->chip_base_addr=candev->io_addr; - candev->chip[chipnr]->clock = clock_freq; + candev->chip[chipnr]->chip_base_addr=can_ioport2ioptr(candev->io_addr); + if(candev->chip[chipnr]->clock<=0) + candev->chip[chipnr]->clock = CAN_BFAD_CLOCKFREQ; candev->chip[chipnr]->sja_cdr_reg = sjaCDR_CBP | sjaCDR_CLK_OFF; candev->chip[chipnr]->sja_ocr_reg = sjaOCR_MODE_NORMAL | sjaOCR_TX0_LH; - id1 = inb(0xe284); - id2 = inb(0xe285); + id1 = can_inb(0xe284); + id2 = can_inb(0xe285); CANMSG("can driver ver lincan-0.3, at %04lx, CPLD v%d.%d.%d.%d\n", - candev->chip[chipnr]->chip_base_addr, - id1>>4, id1&0x0f, id2>>4, id2&0x0f); + can_ioptr2ulong(candev->chip[chipnr]->chip_base_addr), + id1>>4, id1&0x0f, id2>>4, id2&0x0f); return 0; @@ -222,7 +241,7 @@ int bfadcan_init_chip_data(struct candevice_t *candev, int chipnr) * CAN chip. In case of the sja1000 there's only one message object but on the * i82527 chip there are 15. * The code below is for a i82527 chip and initializes the object base addresses - * The entry @obj_base_addr represents the first memory address of the message + * The entry @obj_base_addr represents the first memory address of the message * object. In case of the sja1000 @obj_base_addr is taken the same as the chips * base address. * Unless the hardware uses a segmented memory map, flags can be set zero. @@ -232,7 +251,7 @@ int bfadcan_init_chip_data(struct candevice_t *candev, int chipnr) int bfadcan_init_obj_data(struct canchip_t *chip, int objnr) { chip->msgobj[objnr]->obj_base_addr=chip->chip_base_addr+(objnr+1)*0x10; - + return 0; } @@ -240,10 +259,10 @@ int bfadcan_init_obj_data(struct canchip_t *chip, int objnr) * bfadcan_program_irq - program interrupts * @candev: Pointer to candevice/board structure * - * The function bfadcan_program_irq() is used for hardware that uses + * The function bfadcan_program_irq() is used for hardware that uses * programmable interrupts. If your hardware doesn't use programmable interrupts - * you should not set the @candevices_t->flags entry to %CANDEV_PROGRAMMABLE_IRQ and - * leave this function unedited. Again this function is hardware specific so + * you should not set the @candevices_t->flags entry to %CANDEV_PROGRAMMABLE_IRQ and + * leave this function unedited. Again this function is hardware specific so * there's no example code. * Return value: The function returns zero on success or %-ENODEV on failure * File: src/bfadcan.c @@ -264,16 +283,16 @@ int bfadcan_program_irq(struct candevice_t *candev) * Return Value: The function does not return a value * File: src/bfadcan.c */ -void bfadcan_write_register(unsigned data, unsigned long address) +void bfadcan_write_register(unsigned data, can_ioptr_t address) { #ifdef WINDOWED_ACCESS can_spin_irqflags_t flags; can_spin_lock_irqsave(&bfadcan_win_lock,flags); - outb(address&0x00ff,0x200); - outb(data, 0x201); + can_outb(can_ioptr2ulong(address)&0x00ff,0x200); + can_outb(data, 0x201); can_spin_unlock_irqrestore(&bfadcan_win_lock,flags); #else - outb(data,address); + can_outb(data,address); #endif } @@ -287,18 +306,18 @@ void bfadcan_write_register(unsigned data, unsigned long address) * Return Value: The function returns the value stored in @address * File: src/bfadcan.c */ -unsigned bfadcan_read_register(unsigned long address) +unsigned bfadcan_read_register(can_ioptr_t address) { #ifdef WINDOWED_ACCESS can_spin_irqflags_t flags; int ret; can_spin_lock_irqsave(&bfadcan_win_lock,flags); - outb(address&0x00ff,0x200); - ret = inb(0x201); + can_outb(can_ioptr2ulong(address)&0x00ff,0x200); + ret = can_inb(0x201); can_spin_unlock_irqrestore(&bfadcan_win_lock,flags); return ret; #else - return inb(address); + return can_inb(address); #endif }