On 04/14/2014 04:31 AM, Bart Tanghe wrote: > Is it the responsibility of the pwm driver to handle the pinmux of the > io pins? Or is the end user, or a parent driver responsible to handle this? > Idem for the clock?
The pinmux driver is responsible for writing to the pinmux registers. This can be set up either statically so it happens at system boot, or dynamically so that it's triggered by the SPI/... driver. Statically is preferred uneless there's a need to change the pinmux back/forth between different configurations at run-time. Any clock programming should be performed by a clock driver. We don't have one of those upstream yet, mainly because it would rely on talking to the firmware (running on the VideoCore) to manipulate the clocks, and we don't have a firmware protocol driver either. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
