Re: [PATCH 10/13 v5] OMAP: GPIO: Implement GPIO as a platform device

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

 



"Basak, Partha" <p-basak2@xxxxxx> writes:

>> Instead, please propose an API to hwmod for getting the optional
>> clock(s), or possibly cleaner, an API to directly enable/disable
>> optional clocks for an omap_device.
>
> As per our discussion with Paul & you during workshop, I believe,
> optional clock control should be done using clock APIs. So, I would go
> by your suggestion 1 of exposing an API to expose the optional clocks
> in the hwmod, something like: 
>
> struct omap_hwmod_opt_clk * omap_hwmod_get_opt_clks(struct omap_hwmod
> *oh); 
>
> If agreed, Charu will send updated patch.

OK with me.


--
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