Hi,
On Fri, Aug 3, 2018 at 5:18 AM, <dkota@xxxxxxxxxxxxxx> wrote:
>>> + if (of_property_read_u32(pdev->dev.of_node, "spi-max-frequency",
>>> + &spi->max_speed_hz)) {
>
>
>> Why does this need to come from DT?
>
>
> This is required to set the SPI controller max frequency.
> As it is specific to the controller, so looks meaningful to specify it in
> dtsi.
> Also, spi core framework will set the transfer speed to controller max
> frequency
> if transfer frequency is greater than controller max frequency.
> Please mention if you have a other opinion.
Here are my thoughts:
1. It sure seems like the clock framework could be enforcing the max
speed here. SPI can just ask for the speed and the clock framework
will pick the highest speed it can if you ask for one too high. Isn't
that the whole point of the "struct freq_tbl" in the clock driver?
2. The device tree writer already provides a max clock speed for each
SPI slave in the device tree. ...shouldn't the device tree writer
already be taking into account the max of the SPI port when setting
this value?
3. If you really truly need code in the SPI driver then make sure you
include a compatible string for the SoC and have a table in the driver
that's found with of_device_get_match_data(). AKA:
compatible = "qcom,geni-spi-sdm845", "qcom,geni-spi";
...as per #1 and #2 I don't think this is useful
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
