Mark Rutland writes:
> Hi Robert,
>
> Given the addition of an of_device_id table and some (implicit) property
> parsing, this requires a device tree binding document.
Yes, you're right. I'll prepare that.
>> +ret = devm_request_irq(>dev, cot->irq, lubbock_irq_handler, 0,
>> +
Hi Robert,
On Sat, Jan 03, 2015 at 10:35:15PM +, Robert Jarzmik wrote:
> Lubbock () board is the IO motherboard of the Intel PXA25x Development
> Platform, which supports the Lubbock pxa25x soc board.
>
> Historically, this support was in arch/arm/mach-pxa/lubbock.c. When
> gpio-pxa was
Hi Robert,
On Sat, Jan 03, 2015 at 10:35:15PM +, Robert Jarzmik wrote:
Lubbock () board is the IO motherboard of the Intel PXA25x Development
Platform, which supports the Lubbock pxa25x soc board.
Historically, this support was in arch/arm/mach-pxa/lubbock.c. When
gpio-pxa was moved to
Mark Rutland mark.rutl...@arm.com writes:
Hi Robert,
Given the addition of an of_device_id table and some (implicit) property
parsing, this requires a device tree binding document.
Yes, you're right. I'll prepare that.
+ret = devm_request_irq(pdev-dev, cot-irq, lubbock_irq_handler, 0,
Lubbock () board is the IO motherboard of the Intel PXA25x Development
Platform, which supports the Lubbock pxa25x soc board.
Historically, this support was in arch/arm/mach-pxa/lubbock.c. When
gpio-pxa was moved to drivers/pxa, it became a driver, and its
initialization and probing happened at
Lubbock () board is the IO motherboard of the Intel PXA25x Development
Platform, which supports the Lubbock pxa25x soc board.
Historically, this support was in arch/arm/mach-pxa/lubbock.c. When
gpio-pxa was moved to drivers/pxa, it became a driver, and its
initialization and probing happened at
6 matches
Mail list logo
