Skip to contentSkip to conversation

SMX UIO interface

UIO Armin Steinhoff 2 participants 7 messages Sep 1, 2010 – Sep 5, 2010

lore
Share & tools
lore
#0 lore raw

Hi Ben,

I have a question about the SMX UIO Interface.

In the SMX module you are reading the data of the platform resourses:

    regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
    if (!regs) {
        dev_err(&dev->dev, "No memory resource specified\n");
        goto out_free;
    }

But who sets these data initially ?

Cheers

--Armin

#1 lore raw
Quoted 6 lines · Armin Steinhoff

Hi Ben,

I have a question about the SMX UIO Interface.

In the SMX module you are reading the data of the platform resourses:

Quoted 7 lines
   regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
   if (!regs) {
       dev_err(&dev->dev, "No memory resource specified\n");
       goto out_free;
   }

But who sets these data initially ?

Who ever sets up the platform device that will bind to this driver, usually the board code (eg on avr32 arch/avr32/boards/*/setup.c, ARM is somewhere under arch/arm/mach-*/ I think).

The board code would create an array of struct resource with the appropriate memory regions and an IRQ entry, create a struct platform_device with the right content to bind to that driver, set the platform_device .resource field to the previously created array then call platform_device_register() to kick things off.

	--Ben.
Quoted 5 lines

Cheers

--Armin

#2 lore raw
Quoted 14 lines · Ben Nizette
Quoted 12 lines · Armin Steinhoff

Hi Ben,

I have a question about the SMX UIO Interface.

In the SMX module you are reading the data of the platform resourses:

    regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
    if (!regs) {
        dev_err(&dev->dev, "No memory resource specified\n");
        goto out_free;
    }
Quoted 5 lines
Quoted 1 line

But who sets these data initially ?

Who ever sets up the platform device that will bind to this driver, usually the board code (eg on avr32 arch/avr32/boards/*/setup.c, ARM is somewhere under arch/arm/mach-*/ I think).

The board code would create an array of struct resource with the appropriate memory regions and an IRQ entry, create a struct platform_device with the right content to bind to that driver, set the platform_device .resource field to the previously created array then call platform_device_register() to kick things off.

That means there is additionally an individual driver of the board
and the UIO interface is just for open up the hardware interfaces ?

Thanks

--Armin

Quoted 7 lines
	--Ben.
Quoted 4 lines

Cheers

--Armin

#3 lore raw
Quoted 15 lines · Armin Steinhoff
Quoted 14 lines · Ben Nizette
Quoted 12 lines · Armin Steinhoff

Hi Ben,

I have a question about the SMX UIO Interface.

In the SMX module you are reading the data of the platform resourses:

   regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
   if (!regs) {
       dev_err(&dev->dev, "No memory resource specified\n");
       goto out_free;
   }
Quoted 7 lines
Quoted 5 lines
Quoted 1 line

But who sets these data initially ?

Who ever sets up the platform device that will bind to this driver, usually the board code (eg on avr32 arch/avr32/boards/*/setup.c, ARM is somewhere under arch/arm/mach-*/ I think).

The board code would create an array of struct resource with the appropriate memory regions and an IRQ entry, create a struct platform_device with the right content to bind to that driver, set the platform_device .resource field to the previously created array then call platform_device_register() to kick things off.

That means there is additionally an individual driver of the board and the UIO interface is just for open up the hardware interfaces ?

Um, sort of, I guess.. :-)

The board code isn't a driver, it's just code that gets run at startup whose job is to register all the devices on the board. If your board only contains probe-able busses then you might not need any board code at all but if you've got busses which can't be automatically discovered then something else needs to tell the kernel what devices are where.

Maybe a good place to start would be to read up a bit more on the Linux device model and look through some example board code, you'll probably learn more than me just answering small bits like this :-)

	--Ben.
Quoted 19 lines

Thanks

--Armin

Quoted 7 lines
	--Ben.
Quoted 4 lines

Cheers

--Armin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#4 lore raw
Quoted 20 lines · Ben Nizette
Quoted 18 lines · Armin Steinhoff
Quoted 17 lines · Ben Nizette
Quoted 6 lines · Armin Steinhoff

Hi Ben,

I have a question about the SMX UIO Interface.

In the SMX module you are reading the data of the platform resourses:

Quoted 7 lines
    regs = platform_get_resource(dev, IORESOURCE_MEM, 0);
    if (!regs) {
        dev_err(&dev->dev, "No memory resource specified\n");
        goto out_free;
    }

But who sets these data initially ?

Who ever sets up the platform device that will bind to this driver, usually the board code (eg on avr32 arch/avr32/boards/*/setup.c, ARM is somewhere under arch/arm/mach-*/ I think).

Quoted 8 lines
Quoted 3 lines
Quoted 2 lines

The board code would create an array of struct resource with the appropriate memory regions and an IRQ entry, create a struct platform_device with the right content to bind to that driver, set the platform_device .resource field to the previously created array then call platform_device_register() to kick things off.

That means there is additionally an individual driver of the board and the UIO interface is just for open up the hardware interfaces ?

Um, sort of, I guess.. :-)

The board code isn't a driver, it's just code that gets run at startup whose job is to register all the devices on the board. If your board only contains probe-able busses then you might not need any board code at all but if you've got busses which can't be automatically discovered then something else needs to tell the kernel what devices are where.

Maybe a good place to start would be to read up a bit more on the Linux device model and look through some example board code, you'll probably learn more than me just answering small bits like this :-)

Yes, you are right. I'm currently learning a lot about the Linux
driver model ... it's a real jungle :)

Thanks for your small bits and bytes

--Armin

Quoted 19 lines
	--Ben.
Quoted 16 lines

Thanks

--Armin

Quoted 6 lines
	--Ben.
Quoted 4 lines

Cheers

--Armin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#5 lore raw

[ISA bus] or platform bus ?

In reply to Ben Nizette

Hi,

I have developed a UIO based driver using the platform bus. The target device is an ISA bus board.

Can an ISA bus board create interrupts for a device based on the platform bus ?

I don't see any interrupts. The hardware and BIOS settings are OK .. was verified on an other OS.

--Armin

#6 lore raw

[PC/104 interrupt bug] Fedora 13 problem

In reply to Ben Nizette

Hi,

I'm developing a driver for a PC/104 board and see that the flag IRQF_TRIGGER_RISING has no effect with a request_irq() call.

The related interrupt pin of the PIC / APIC isn't after the request_irq() call reconfigured for handling of an ISA interrupt !
The ISA interrupt is connected to a pull down resistor ... which leads to a catastrophic crash when that ISA interrupt line is handled as a PCI interrupt line.

Is this by design - that means no ISA interrupt supported - or is it a bug ?

--Armin