On 2014-06-16 10:36, Nikita Yushchenko wrote:
SPARC does not use OF_IRQ and has a different implementation of
irq_of_parse_and_map than the one in drivers/of/irq.c. All code
converted from irq_of_parse_and_map to devm_irq_of_parse_and_map in this
patch set will be unlinkable for SPARC. This
On 2014-06-12 21:02, Nikita Yushchenko wrote:
Currently many device tree aware drivers use irq_of_parse_and_map() to
get
IRQ number and then devm_request_irq() to set up IRQ handler.
This causes a problem for exit path and for error paths: undo action for
irq_of_parse_and_map() is
>>> SPARC does not use OF_IRQ and has a different implementation of
>>> irq_of_parse_and_map than the one in drivers/of/irq.c. All code
>>> converted from irq_of_parse_and_map to devm_irq_of_parse_and_map in this
>>> patch set will be unlinkable for SPARC. This includes SPI in general and
>>> many
SPARC does not use OF_IRQ and has a different implementation of
irq_of_parse_and_map than the one in drivers/of/irq.c. All code
converted from irq_of_parse_and_map to devm_irq_of_parse_and_map in this
patch set will be unlinkable for SPARC. This includes SPI in general and
many drivers that
On 2014-06-12 21:02, Nikita Yushchenko wrote:
Currently many device tree aware drivers use irq_of_parse_and_map() to
get
IRQ number and then devm_request_irq() to set up IRQ handler.
This causes a problem for exit path and for error paths: undo action for
irq_of_parse_and_map() is
On 2014-06-16 10:36, Nikita Yushchenko wrote:
SPARC does not use OF_IRQ and has a different implementation of
irq_of_parse_and_map than the one in drivers/of/irq.c. All code
converted from irq_of_parse_and_map to devm_irq_of_parse_and_map in this
patch set will be unlinkable for SPARC. This
>> Currently many device tree aware drivers use irq_of_parse_and_map() to
>> get
>> IRQ number and then devm_request_irq() to set up IRQ handler.
>>
>> This causes a problem for exit path and for error paths: undo action for
>> irq_of_parse_and_map() is irq_dispose_mapping() that must not be
On 2014-06-04 13:13, nyushche...@dev.rtsoft.ru wrote:
Currently many device tree aware drivers use irq_of_parse_and_map() to get
IRQ number and then devm_request_irq() to set up IRQ handler.
This causes a problem for exit path and for error paths: undo action for
irq_of_parse_and_map() is
On 2014-06-04 13:13, nyushche...@dev.rtsoft.ru wrote:
Currently many device tree aware drivers use irq_of_parse_and_map() to get
IRQ number and then devm_request_irq() to set up IRQ handler.
This causes a problem for exit path and for error paths: undo action for
irq_of_parse_and_map() is
Currently many device tree aware drivers use irq_of_parse_and_map() to
get
IRQ number and then devm_request_irq() to set up IRQ handler.
This causes a problem for exit path and for error paths: undo action for
irq_of_parse_and_map() is irq_dispose_mapping() that must not be called
while IRQ
10 matches
Mail list logo