diff options
author | Stephan Gerhold <stephan@gerhold.net> | 2021-05-19 12:16:13 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-05-19 22:44:23 +0300 |
commit | 340f42f7ff0b87a92e69b50706a6c872da756c89 (patch) | |
tree | 11d90713ad3e0ca420b6355e047e352060e96bbc /net/ipv6/sysctl_net_ipv6.c | |
parent | 9cc52f5a533a321136b9e447042ad9f8224f738c (diff) | |
download | linux-340f42f7ff0b87a92e69b50706a6c872da756c89.tar.xz |
nfc: s3fwrn5: i2c: Enable optional clock from device tree
S3FWRN5 depends on a clock input ("XI" pin) to function properly.
Depending on the hardware configuration this could be an always-on
oscillator or some external clock that must be explicitly enabled.
So far we assumed that the clock is always-on.
Make the driver request an (optional) clock from the device tree
and make sure the clock is running before starting S3FWRN5.
Note: S3FWRN5 asserts "GPIO2" whenever it needs the clock input to
function correctly. On some hardware configurations, GPIO2 is
connected directly to an input pin of the external clock provider
(e.g. the main PMIC of the SoC). In that case, it can automatically
AND the clock enable bit and clock request from S3FWRN5 so that
the clock is actually only enabled when needed.
It is also conceivable that on some other hardware configuration
S3FWRN5's GPIO2 might be connected as a regular GPIO input
of the SoC. In that case, follow-up patches could extend the
driver to request the GPIO, set up an interrupt and only enable
the clock when requested by S3FWRN5.
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/sysctl_net_ipv6.c')
0 files changed, 0 insertions, 0 deletions