On Sat, Aug 08, 2015 at 02:24:04AM +0530, raghu MG wrote:
> Hi Andrew,
> I added these entries into armada-xp-gp.dtb
> gpio_rtm {
> compatible = "gpio-rtm";
> #address-cells = <1>;
> #size-cells = <0>;
> pinctrl-0 = <&keys_pin>;
>
Hi Andrew,
I added these entries into armada-xp-gp.dtb
gpio_rtm {
compatible = "gpio-rtm";
#address-cells = <1>;
#size-cells = <0>;
pinctrl-0 = <&keys_pin>;
pinctrl-names = "default";
rtm@57 {
Ok...
my bad never realised DT entries are necessary.
will try this & post the results.
Regards
Raghu
On Thu, Aug 6, 2015 at 10:43 PM, Andrew Lunn wrote:
> On Thu, Aug 06, 2015 at 10:28:12PM +0530, raghu MG wrote:
>> Ok,I think I need to understand more about this gpio driver.
>>
>> As you said
On Thu, Aug 06, 2015 at 10:28:12PM +0530, raghu MG wrote:
> Ok,I think I need to understand more about this gpio driver.
>
> As you said its registering chained handler,but why are they(IRQs) not
> visible in cat /proc/interrupts.
chained interrupts are never visible there. All you see are leaf
i
Ok,I think I need to understand more about this gpio driver.
As you said its registering chained handler,but why are they(IRQs) not
visible in cat /proc/interrupts.
What could be the reason.?
Do I need to further initialize marvell GPIO registers to trigger
these events. The driver is unmasking a
> mvebu_gpio_irq_handler is only called if I register a another handler
> at irq=82/83/84/85/87/88/89/90/92. I am registering this handler using
> minimal kernel module.
This is totally wrong. The gpio driver needs these interrupts, and
will register a chained interrupt handle for these. Don't mes
Hi Andrew,
My platform/board is ATCA carrier card which is getting interface to I/O card.
The I/O card is hot-pluggable or Jack-in or Jack out.
Also I/O card consists of hot-plugable SFP interface.
These events are triggered using GPIO's
So the events the carrier card recieves are
1) If I/O card
On Wed, Aug 05, 2015 at 08:31:27PM +0530, raghu MG wrote:
> Hi Andrew,
>
> The issue I found was irq_alloc_descs is called twice
> 1st time inside mvebu_gpio_probe & 2nd time inside irq_domain_add_simple.
So i'm somewhat confused. I just tested on my Kirkwood and 370
platforms, and an Armada X
Hi Andrew,
The issue I found was irq_alloc_descs is called twice
1st time inside mvebu_gpio_probe & 2nd time inside irq_domain_add_simple.
The warning is thrown up when irq_alloc_descs is called 2nd
time(irq_domain_add_simple) & bitmap_find_next_zero_area gives new
value of start which is not
Hi Andrew,
Thanks for your quick response,dont mind for the delay(India,US timings).
I checked with both multi_v7_defconfig & mvebu_v7_defconfig , the result is same
"irq: Cannot allocate irq_descs @ IRQ47, assuming pre-allocated"
Pasting here the GPIO driver probe debug statements
armada-xp-pin
On Tue, Aug 04, 2015 at 08:52:17PM +0530, raghu MG wrote:
> Hello,
>
> I am working on a card which as GPIOs connected to external I/O's. The
> board consists of ARMADAXP 78460 host cpu.
>
> Board currently runs Linux-4.1 with modified armada-xp-gp.dtb for ArmadaXP.
> I enabled "orion-gpio" driv
11 matches
Mail list logo
