*/
int ns_dev_request_io(struct candevice_t *candev)
{
- /* Note hard-coded index for the chip number as this
+ /* Note hard-coded index for the chip number as this
* only supports a single instance of the C_CAN controller.
*/
DEBUGMSG("(c%d)ns_dev_request_io (...)\n", candev->chip[0]->chip_idx);
*
* The function ns_dev_init_obj_data() is used to initialize the hardware
* structure containing information about the different message objects on the
- * CAN chip.
- * The entry @obj_base_addr represents the first memory address of the message
- * object.
+ * CAN chip.
+ * The entry @obj_base_addr represents the first memory address of the message
+ * object.
* Unless the hardware uses a segmented memory map, flags can be set zero.
* Return Value: The function always returns zero
* File: src/template.c
* ns_dev_program_irq - program interrupts
* @candev: Pointer to candevice/board structure
*
- * The function ns_dev_program_irq() is used for hardware that uses
+ * The function ns_dev_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/template.c