Driver provides probe and attach functions for LS1046A clockgen and passes
configuration information to QorIQ clockgen class. May be used as
reference implementation for different QorIQ clockgen devices.
Details
- Reviewers
mw manu mmel - Commits
- rS361459: Add LS1046A clockgen driver.
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
This is a comment for all the LS1046A reviews: Please add a new SOC_NXP_LS1046A option to sys/conf/options.arm64 and make the drivers depend on that in sys/conf/files.arm64
Thanks
I modified the driver to use the modified QorIQ clockgen classes.
Also added dependency on SOC_NXP_LS104A.
sys/arm64/qoriq/clk/ls1046a_clkgen.c | ||
---|---|---|
173 ↗ | (On Diff #71196) | No, that was not intentional. |
213 ↗ | (On Diff #71196) | I used init function here as the way FMAN nodes work is specific to SoC, so different way of creating this node may be needed. |
Imho, It will be better to wait with this until we find consensus with D24351, right ?
sys/arm64/qoriq/clk/ls1046a_clkgen.c | ||
---|---|---|
59 ↗ | (On Diff #71196) | There is no reason to obfuscate clock node name in this way, please use names from TRM |
126 ↗ | (On Diff #71196) | huh!. Use nitems() :) |
173 ↗ | (On Diff #71196) | again this is wrong way. Simply encode both cells into one id and use it. |
The LS family has too many members and can share 99% of the code. It seems unnecessary for me to have the option for each individual variant. How about 'SOC_NXP_LS' ?
from IRC:
There is at least 11 variants of QoriQ arm64 based SoCs. This is too much for per-SOC options.
We can always add a SOC_NXP_LS_BLAH and !it if one soc differs