diff options
author | Simon Glass <sjg@chromium.org> | 2015-08-30 22:55:13 (GMT) |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-09-03 03:28:22 (GMT) |
commit | c5acf4a2b3c6fd49aa0bc02db50f4b625b2e2991 (patch) | |
tree | 86e7a857184156f9caac84b48d15a654427f8644 /drivers/net | |
parent | 458a070076dc920a7106f0c8f0cfa880503ce498 (diff) | |
download | u-boot-fsl-qoriq-c5acf4a2b3c6fd49aa0bc02db50f4b625b2e2991.tar.xz |
pinctrl: Add the concept of peripheral IDs
My original pinctrl patch operating using a peripheral ID enum. This was
shared between pinmux and clock and provides an easy way to specify a device
that needs to be controlled, even it is does not (yet) have a driver within
driver model.
Masahiro's new simple pinctrl gets around this by providing a
set_state_simple() pinctrl method. By passing a device to that call the
peripheral ID becomes unnecessary. If the driver needs it, it can calculate
it itself and use it internally.
However this does not solve the problem for peripheral clocks. The 'pure'
solution would be to pass a driver to the clock uclass also. But this
requires that all devices should have a driver, and a struct udevide. Also
a key optimisation of the clock uclass is allowing a peripheral clock to
be set even when there is no device for that clock.
There may be a better way to achive the same goal, but for now it seems
expedient to add in peripheral ID to the pinctrl uclass. Two methods are
added - one to get the peripheral ID and one to select it. The existing
set_state_simple() is effectively the union of these.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions