Re: DMA controller/engine

> thanks, for your answer. The device im working on can read/write data
> to/from memory/devices. So yes, it can also offload memory to memory
> access, but also works as the "normal" dma controller
> (devices->memory). It's the first time i have to implement the driver
> for a device like this so im not sure what direction should i follow.
> There are a couple of things to consider too, the dma controller can
> have priorities and also each peripheral has its own numeric id (to
> store on a register) in case the controller channel reads/writes
> to/from a device. Only using the drivers/dma API restricts the
> functionality but i guess at least is an API other subsystems (fb, v4l
> for example) can benefict from.
>
Here is what I have done for the iop series dma's:

patch introduction e-mail:
http://marc.theaimsgroup.com/?l=linux-raid&m=116491661527161&w=2
iop-adma device driver:
http://marc.theaimsgroup.com/?l=linux-raid&m=116491866629073&w=2
async_tx api:
http://marc.theaimsgroup.com/?l=linux-raid&m=116491753318175&w=2

Dan

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

MX21 i2c driver

hi ,
i wish to code  i2c driver for MX21 for kernel 2.6.14.is any one
already done this?
(no need to reinvent the wheel )
thanks.

dilan

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

Re: MX21 i2c driver

On 12/1/06, Dilan Weerakkody <dilan2005 <at> gmail.com> wrote:
> hi ,
> i wish to code  i2c driver for MX21 for kernel 2.6.14.is any one
> already done this?
> (no need to reinvent the wheel )
> thanks.

This looks like the right file. I haven't tried using it.

There is a minor ifdef added for the MX21.

--

-- 
Jon Smirl
jonsmirl <at> gmail.com

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

Re: Bug in at91mmc?

hi David,

> I think I may have found a bug in the at91 mmc driver whereby instead of 
> switching the power on vcc as intended, the code remaps the pin!

It won't be "remapping" the pin since at91_add_device_mmc() has already
done:
     if (data->vcc_pin)
         at91_set_gpio_output(data->vcc_pin, 0);

But you're right, at91_set_gpio_value() is the correct function to use
here since only the board/platform setup code should be doing to
at91_set_gpio_output() or at91_set_gpio_input().

[This was actually already fixed in the 2.6.19-rc6 patch on
http://maxim.org.za/at91_26.html].

Regards,
  Andrew Victor

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

MX21 i2c driver

hi jon,

i got some problem with marco i think this marco for setup pin for i2c
fucntions.(correct me if i am wrong.)
if u got header file define these marco please send it to me.i think
file should be something like
imx-regs.h
but i m not sure
thanks
dilan

	imx_gpio_mode(PA15_PF_I2C_SDA);
  	imx_gpio_mode(PA16_PF_I2C_SCL);

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

Re: Re: Re: AT91RM9200 pio interrupt prob lem on linux -2.6

hi, if on linux-2.4, does I register irq as follows:
register_irq(piob_no,handler,SA_SHIRQ,)
the irq_no is equal to pio_no?
Thank you.
best regards.

 

 在2006-11-29，"Andrew Victor" <andrew <at> sanpeople.com> ：

hi,

> Thank you , but how can I know which edge it is when interrupt
> happens.

You can use at91_get_gpio_value(AT91_PIN_xx) to determine the current
state of the pin.

So either compare the current state with the last state, or maybe ignore
every 2nd interrupt?

Or if it's an external device that you can query, check whether it
thinks it has an interrupt pending.  (that's what we do for the Ethernet
PHY interrupt).

Regards,
  Andrew Victor

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel

MX21 access to PCCR1 register

hi all,

when i writing modules for Key Pad i come across a problem with
enabling clock keypad with
pccr1 register . when i insmod my module it gives me whole set of
errors. A Segmentation fault.
i over come this by enabling clock when kernel start by coding in
generic.c clock init function.

i want to know weather access to these register are limited by kernel,thanks

dilan

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

Re: Re: Re: AT91RM9200 pio interrupt prob lem on linux -2.6

hi,

> hi, if on linux-2.4, does I register irq as follows:
> register_irq(piob_no,handler,SA_SHIRQ,)
> the irq_no is equal to pio_no?

The AT91 GPIO interrupts are handled totally differently in 2.4 using
the AT91-specific at91rm9200_gpio_request_irq() and
at91rm9200_gpio_free_irq().

I recommend you upgrade to 2.6.

Regards,
  Andrew Victor

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

Re: MX21 i2c driver

Dilan Weerakkody wrote:
> hi jon,
> 
> i got some problem with marco i think this marco for setup pin for i2c
> fucntions.(correct me if i am wrong.)
> if u got header file define these marco please send it to me.i think
> file should be something like
> imx-regs.h
> but i m not sure
> thanks
> dilan
> 
>     imx_gpio_mode(PA15_PF_I2C_SDA);
>      imx_gpio_mode(PA16_PF_I2C_SCL);
> 

Hi,

The i2c-driver works for iMX.L. I don't know, if it's working for MX21, 
but just try!

imx_gpio_mode is defined in the files:
arch/arm/mach-imx/generic.c
include/asm-arm/arch-imx/hardware.h

You have to look into the vanilla kernel sources since ~ 2.6.16.

Torsten

-------------------------------------------------------------------

Re: MX21 access to PCCR1 register

sorry wrong question.i mistakenly get wrong address.
thanks

On 12/1/06, Dilan Weerakkody <dilan2005 <at> gmail.com> wrote:
> hi all,
>
> when i writing modules for Key Pad i come across a problem with
> enabling clock keypad with
> pccr1 register . when i insmod my module it gives me whole set of
> errors. A Segmentation fault.
> i over come this by enabling clock when kernel start by coding in
> generic.c clock init function.
>
> i want to know weather access to these register are limited by kernel,thanks
>
> dilan
>

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php