Re: [PATCH v4 1/2] gpio/omap: don't create an IRQ mapping for every GPIO on DT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 29.07.2013 13:30, schrieb Alexander Holler:

So I think the driver has to be changed independently of the approach
for auto request GPIO used.

Maybe, but that isn't much effort. I had done that in 3 minutes (ok,
without the would be necessary #ifdef CONFIG_OF_GPIO). But you have a
chicken and egg situation here, because you can't change drivers without
the new patch and you can't introduce the new patch without changes to
drivers.

As I had mentioned before, another approach could be to map the irq when
gpio_to_irq() is called. I think that would be downward compatible
without the need for some changes in a dts.

Having send that, I had another idea: introduce a config option to enable/disable the new behaviour. That would make it possible to change drivers while not breaking compatibility, and when all are changed, the config option could go away.

Regards,

Alexander Holler

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux