2 * Linux CAN-bus device driver.
3 * Written by Arnaud Westenberg email:arnaud@wanadoo.nl
4 * Rewritten for new CAN queues by Pavel Pisa - OCERA team member
5 * email:pisa@cmp.felk.cvut.cz
6 * This software is released under the GPL-License.
7 * Version lincan-0.3 17 Jun 2004
10 #include "../include/can.h"
11 #include "../include/can_sysdep.h"
12 #include "../include/main.h"
13 #include "../include/pcm3680.h"
14 #include "../include/i82527.h"
15 #include "../include/sja1000p.h"
18 * IO_RANGE is the io-memory range that gets reserved, please adjust according
19 * your hardware. Example: #define IO_RANGE 0x100 for i82527 chips or
20 * #define IO_RANGE 0x20 for sja1000 chips in basic CAN mode.
22 #define IO_RANGE 0x400
25 * template_request_io: - reserve io or memory range for can board
26 * @candev: pointer to candevice/board which asks for io. Field @io_addr
27 * of @candev is used in most cases to define start of the range
29 * The function template_request_io() is used to reserve the io-memory. If your
30 * hardware uses a dedicated memory range as hardware control registers you
31 * will have to add the code to reserve this memory as well.
32 * %IO_RANGE is the io-memory range that gets reserved, please adjust according
33 * your hardware. Example: #define IO_RANGE 0x100 for i82527 chips or
34 * #define IO_RANGE 0x20 for sja1000 chips in basic CAN mode.
35 * Return Value: The function returns zero on success or %-ENODEV on failure
36 * File: src/template.c
38 int pcm3680_request_io(struct candevice_t *candev)
40 unsigned long remap_addr;
41 if (!can_request_mem_region(candev->io_addr,IO_RANGE,DEVICE_NAME " - pcm3680")) {
42 CANMSG("Unable to request IO-memory: 0x%lx\n",candev->io_addr);
45 if ( !( remap_addr = (long) ioremap( candev->io_addr, IO_RANGE ) ) ) {
46 CANMSG("Unable to access I/O memory at: 0x%lx\n", candev->io_addr);
47 can_release_mem_region(candev->io_addr,IO_RANGE);
51 can_base_addr_fixup(candev, remap_addr);
52 DEBUGMSG("Registered IO-memory: 0x%lx - 0x%lx\n", candev->io_addr, candev->io_addr + IO_RANGE - 1);
57 * template_release_io - free reserved io memory range
58 * @candev: pointer to candevice/board which releases io
60 * The function template_release_io() is used to free reserved io-memory.
61 * In case you have reserved more io memory, don't forget to free it here.
62 * IO_RANGE is the io-memory range that gets released, please adjust according
63 * your hardware. Example: #define IO_RANGE 0x100 for i82527 chips or
64 * #define IO_RANGE 0x20 for sja1000 chips in basic CAN mode.
65 * Return Value: The function always returns zero
66 * File: src/template.c
68 int pcm3680_release_io(struct candevice_t *candev)
70 iounmap((void*)candev->dev_base_addr);
71 can_release_mem_region(candev->io_addr,IO_RANGE);
76 * template_reset - hardware reset routine
77 * @candev: Pointer to candevice/board structure
79 * The function template_reset() is used to give a hardware reset. This is
80 * rather hardware specific so I haven't included example code. Don't forget to
81 * check the reset status of the chip before returning.
82 * Return Value: The function returns zero on success or %-ENODEV on failure
83 * File: src/template.c
85 int pcm3680_reset(struct candevice_t *candev)
91 DEBUGMSG("Resetting pcm3680 hardware ...\n");
92 for(chipnr=0;chipnr<candev->nr_sja1000_chips;chipnr++) {
93 chip=candev->chip[chipnr];
94 pcm3680_write_register(sjaMOD_RM, chip->chip_base_addr+SJAMOD);
96 pcm3680_write_register(0x00, chip->chip_base_addr + SJAIER);
97 /* Write arbitrary data to reset chip */
98 pcm3680_write_register(0x01, chip->chip_base_addr + 0x100);
101 while (pcm3680_read_register(chip->chip_base_addr+SJAMOD)&sjaMOD_RM){
102 if(!i--) return -ENODEV;
104 pcm3680_write_register(0, chip->chip_base_addr+SJAMOD);
107 pcm3680_write_register(sjaCDR_PELICAN, chip->chip_base_addr+SJACDR);
108 pcm3680_write_register(0x00, chip->chip_base_addr + SJAIER);
114 #define RESET_ADDR 0x100
119 * template_init_hw_data - Initialize hardware cards
120 * @candev: Pointer to candevice/board structure
122 * The function template_init_hw_data() is used to initialize the hardware
123 * structure containing information about the installed CAN-board.
124 * %RESET_ADDR represents the io-address of the hardware reset register.
125 * %NR_82527 represents the number of intel 82527 chips on the board.
126 * %NR_SJA1000 represents the number of philips sja1000 chips on the board.
127 * The flags entry can currently only be %CANDEV_PROGRAMMABLE_IRQ to indicate that
128 * the hardware uses programmable interrupts.
129 * Return Value: The function always returns zero
130 * File: src/template.c
132 int pcm3680_init_hw_data(struct candevice_t *candev)
134 candev->res_addr=RESET_ADDR;
135 candev->nr_82527_chips=NR_82527;
136 candev->nr_sja1000_chips=NR_SJA1000;
137 candev->nr_all_chips=NR_82527+NR_SJA1000;
138 candev->flags &= ~CANDEV_PROGRAMMABLE_IRQ;
144 * template_init_chip_data - Initialize chips
145 * @candev: Pointer to candevice/board structure
146 * @chipnr: Number of the CAN chip on the hardware card
148 * The function template_init_chip_data() is used to initialize the hardware
149 * structure containing information about the CAN chips.
150 * %CHIP_TYPE represents the type of CAN chip. %CHIP_TYPE can be "i82527" or
152 * The @chip_base_addr entry represents the start of the 'official' memory map
153 * of the installed chip. It's likely that this is the same as the @io_addr
154 * argument supplied at module loading time.
155 * The @clock entry holds the chip clock value in Hz.
156 * The entry @sja_cdr_reg holds hardware specific options for the Clock Divider
157 * register. Options defined in the %sja1000.h file:
158 * %sjaCDR_CLKOUT_MASK, %sjaCDR_CLK_OFF, %sjaCDR_RXINPEN, %sjaCDR_CBP, %sjaCDR_PELICAN
159 * The entry @sja_ocr_reg holds hardware specific options for the Output Control
160 * register. Options defined in the %sja1000.h file:
161 * %sjaOCR_MODE_BIPHASE, %sjaOCR_MODE_TEST, %sjaOCR_MODE_NORMAL, %sjaOCR_MODE_CLOCK,
162 * %sjaOCR_TX0_LH, %sjaOCR_TX1_ZZ.
163 * The entry @int_clk_reg holds hardware specific options for the Clock Out
164 * register. Options defined in the %i82527.h file:
165 * %iCLK_CD0, %iCLK_CD1, %iCLK_CD2, %iCLK_CD3, %iCLK_SL0, %iCLK_SL1.
166 * The entry @int_bus_reg holds hardware specific options for the Bus
167 * Configuration register. Options defined in the %i82527.h file:
168 * %iBUS_DR0, %iBUS_DR1, %iBUS_DT1, %iBUS_POL, %iBUS_CBY.
169 * Return Value: The function always returns zero
170 * File: src/template.c
172 int pcm3680_init_chip_data(struct candevice_t *candev, int chipnr)
174 sja1000p_fill_chipspecops(candev->chip[chipnr]);
175 candev->chip[chipnr]->chip_base_addr=
176 candev->io_addr + 0x200*chipnr;
177 candev->chip[chipnr]->clock = 16000000;
178 candev->chip[chipnr]->int_clk_reg = 0x0;
179 candev->chip[chipnr]->int_bus_reg = 0x0;
180 candev->chip[chipnr]->sja_cdr_reg = sjaCDR_CBP | sjaCDR_CLK_OFF;
181 candev->chip[chipnr]->sja_ocr_reg = sjaOCR_MODE_NORMAL |
188 * template_init_obj_data - Initialize message buffers
189 * @chip: Pointer to chip specific structure
190 * @objnr: Number of the message buffer
192 * The function template_init_obj_data() is used to initialize the hardware
193 * structure containing information about the different message objects on the
194 * CAN chip. In case of the sja1000 there's only one message object but on the
195 * i82527 chip there are 15.
196 * The code below is for a i82527 chip and initializes the object base addresses
197 * The entry @obj_base_addr represents the first memory address of the message
198 * object. In case of the sja1000 @obj_base_addr is taken the same as the chips
200 * Unless the hardware uses a segmented memory map, flags can be set zero.
201 * Return Value: The function always returns zero
202 * File: src/template.c
204 int pcm3680_init_obj_data(struct chip_t *chip, int objnr)
206 chip->msgobj[objnr]->obj_base_addr=chip->chip_base_addr;
212 * template_program_irq - program interrupts
213 * @candev: Pointer to candevice/board structure
215 * The function template_program_irq() is used for hardware that uses
216 * programmable interrupts. If your hardware doesn't use programmable interrupts
217 * you should not set the @candevices_t->flags entry to %CANDEV_PROGRAMMABLE_IRQ and
218 * leave this function unedited. Again this function is hardware specific so
219 * there's no example code.
220 * Return value: The function returns zero on success or %-ENODEV on failure
221 * File: src/template.c
223 int pcm3680_program_irq(struct candevice_t *candev)
229 * template_write_register - Low level write register routine
230 * @data: data to be written
231 * @address: memory address to write to
233 * The function template_write_register() is used to write to hardware registers
234 * on the CAN chip. You should only have to edit this function if your hardware
235 * uses some specific write process.
236 * Return Value: The function does not return a value
237 * File: src/template.c
239 void pcm3680_write_register(unsigned data, unsigned long address)
241 writeb(data,address);
245 * template_read_register - Low level read register routine
246 * @address: memory address to read from
248 * The function template_read_register() is used to read from hardware registers
249 * on the CAN chip. You should only have to edit this function if your hardware
250 * uses some specific read process.
251 * Return Value: The function returns the value stored in @address
252 * File: src/template.c
254 unsigned pcm3680_read_register(unsigned long address)
256 return readb(address);
259 /* !!! Don't change this function !!! */
260 int pcm3680_register(struct hwspecops_t *hwspecops)
262 hwspecops->request_io = pcm3680_request_io;
263 hwspecops->release_io = pcm3680_release_io;
264 hwspecops->reset = pcm3680_reset;
265 hwspecops->init_hw_data = pcm3680_init_hw_data;
266 hwspecops->init_chip_data = pcm3680_init_chip_data;
267 hwspecops->init_obj_data = pcm3680_init_obj_data;
268 hwspecops->write_register = pcm3680_write_register;
269 hwspecops->read_register = pcm3680_read_register;
270 hwspecops->program_irq = pcm3680_program_irq;