mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 12:43:55 +08:00
1a3377176b
It turns out that the only purpose of the CONFIG_PARTICIPANT clock flag is to prevent omap2_clk_set_rate() and omap2_clk_set_parent() from being executed on clocks with that flag set. The rate-changing component can be more directly accomplished by dropping the .set_rate and .round_rate function pointers from those CONFIG_PARTICIPANT struct clks. As far as the parent-changing component is concerned, it turns out that none of the CONFIG_PARTICIPANT clocks have multiple parent choices, so all that is necessary is for omap2_clk_set_parent() to bail out early if the new parent is equal to the old parent. Implement this change and get rid of the flag, which has always had a confusing name (it appears to be a Kconfig option, falsely). Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Richard Woodruff <r-woodruff2@ti.com> |
||
|---|---|---|
| .. | ||
| include/plat | ||
| clock.c | ||
| common.c | ||
| cpu-omap.c | ||
| debug-devices.c | ||
| debug-leds.c | ||
| devices.c | ||
| dma.c | ||
| dmtimer.c | ||
| fb.c | ||
| gpio.c | ||
| i2c.c | ||
| io.c | ||
| iommu-debug.c | ||
| iommu.c | ||
| iopgtable.h | ||
| iovmm.c | ||
| Kconfig | ||
| mailbox.c | ||
| Makefile | ||
| mcbsp.c | ||
| mux.c | ||
| ocpi.c | ||
| omap_device.c | ||
| omap-pm-noop.c | ||
| sram.c | ||
| usb.c | ||