On 08/12/2017 18:20, Ladislav Michl wrote:
> Daniel,
>
> On Thu, Dec 07, 2017 at 11:54:27AM +0100, Daniel Lezcano wrote:
>> On 01/12/2017 06:16, Keerthy wrote:
>>> Move the dmtimer driver out of plat-omap to clocksource.
>>> So that non-omap devices also could use this.
>>>
>>> No Code changes done to the driver file.
>>>
>>> Signed-off-by: Keerthy <j-keerthy@xxxxxx>
>>> Reviewed-by: Sebastian Reichel <sebastian.reichel@xxxxxxxxxxxxxxx>
>>> ---
>>>
>>> Changes in v3:
>>>
>>> * Added Sebastian's Reviewed-by.
>>>
>>> Changes in v2:
>>>
>>> * No code changes in this v2 version. Only enhanced patch
>>> statistics for renames.
>>>
>>> arch/arm/plat-omap/Kconfig | 6 ------
>>> arch/arm/plat-omap/Makefile | 1 -
>>> drivers/clocksource/Kconfig | 6 ++++++
>>> drivers/clocksource/Makefile | 1 +
>>> {arch/arm/plat-omap => drivers/clocksource}/dmtimer.c | 0
>>> 5 files changed, 7 insertions(+), 7 deletions(-)
>>> rename {arch/arm/plat-omap => drivers/clocksource}/dmtimer.c (100%)
>>
>> Take the opportunity to rename it timer-dm.c
>
> seems the drivers/clocksource subdirectory contains what its name state.
Yes, clocksource, clockevent.
> However OMAP dual mode timers have also event capture capability, which
> I'd like to use to measure pulse/space width and pass measured values
> to IR protocol decoders.
> Do you have any idea how to split code, so that event capture capability
> could be used by other drivers?
Not 100% sure but could be drivers/pwm, using the capture API.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
--
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
