mirror of
https://github.com/Evolution-X-Devices/kernel_oneplus_sm8550-devicetrees
synced 2026-02-01 09:04:24 +00:00
ARM: dts: qcom: Add qti-can device tree node
Add qti-can device node for sa8155 and documentation. Change-Id: If919fb31ab58914a3584211ada4faf3729c42d6f
This commit is contained in:
51
bindings/net/can/qti-can.txt
Normal file
51
bindings/net/can/qti-can.txt
Normal file
@@ -0,0 +1,51 @@
|
||||
* QTI CAN driver *
|
||||
|
||||
|
||||
Required properties:
|
||||
- compatible: Should be "qcom,renesas,rh850" or "qcom,nxp,mpc5746c".
|
||||
- reg: Should contain SPI chip select.
|
||||
- interrupt-parent: Should specify interrupt controller for the interrupt.
|
||||
- interrupts: Should contain IRQ line for the CAN controller.
|
||||
- spi-max-frequency: Should contain maximum spi clock frequency for slave device
|
||||
- qcom,clk-freq-mhz : The frequency at which the CAN clock should be configured.
|
||||
- qcom,max-can-channels : Maximum number of CAN channels supported by the controller.
|
||||
|
||||
|
||||
Optional properties:
|
||||
- qcom,reset-gpio: Reference to the GPIO connected to the reset input.
|
||||
- pinctrl-names : Names corresponding to the numbered pinctrl states.
|
||||
- pinctrl-0 : This explains the active state of the GPIO line.
|
||||
- pinctrl-1 : This explains the suspend state of the GPIO line.
|
||||
- qcom,bits-per-word: Indicate how many bits are in a SPI frame. e.g.: 8, 16, 32.
|
||||
Default to 16.
|
||||
- qcom,reset-delay-msec: Delay in milliseconds to be applied after resetting the chip.
|
||||
This is applicable only if the reset-gpio is specified. Default value is 1 ms.
|
||||
- qcom,support-can-fd: Whether CAN FD mode is supported or not.
|
||||
- qcom,can-fw-cmd-timeout-req: Whether a timeout is required if we don't get a response from
|
||||
the firmware after flash write.
|
||||
- qcom,can-fw-cmd-timeout-ms: The duration after which timeout will happen if we don't get a
|
||||
response from the firmware.
|
||||
- qcom,rem-all-buffering-timeout-ms: The duration after which timeout will happen if we don't get a
|
||||
response from the firmware while trying to remove all the buffered frames IDs from flash.
|
||||
|
||||
|
||||
Example:
|
||||
|
||||
can-controller@0 {
|
||||
compatible = "qcom,nxp,mpc5746c";
|
||||
reg = <0>;
|
||||
spi-max-frequency = <9600000>;
|
||||
interrupt-parent = <&tlmm_pinmux>;
|
||||
interrupts = <87 0>;
|
||||
qcom,reset-gpio = <&tlmm_pinmux 89 0x1>;
|
||||
qcom,clk-freq-mhz = <20000000>;
|
||||
qcom,max-can-channels = <2>;
|
||||
qcom,bits-per-word = <8>;
|
||||
qcom,reset-delay-msec = <150>;
|
||||
qcom,can-fw-cmd-timeout-req;
|
||||
qcom,can-fw-cmd-timeout-ms = <400>;
|
||||
qcom,rem-all-buffering-timeout-ms = <2000>;
|
||||
pinctrl-names = "active", "sleep";
|
||||
pinctrl-0 = <&can_rst_on>;
|
||||
pinctrl-1 = <&can_rst_off>;
|
||||
};
|
||||
@@ -9,6 +9,23 @@
|
||||
|
||||
};
|
||||
|
||||
&qupv3_se0_spi {
|
||||
status = "ok";
|
||||
#address-cells = <1>;
|
||||
#size-cells = <0>;
|
||||
can-controller@0 {
|
||||
compatible = "qcom,nxp,mpc5746c";
|
||||
reg = <0>;
|
||||
interrupt-parent = <&tlmm>;
|
||||
interrupts = <38 0>;
|
||||
spi-max-frequency = <5000000>;
|
||||
qcom,clk-freq-mhz = <40000000>;
|
||||
qcom,max-can-channels = <1>;
|
||||
qcom,bits-per-word = <8>;
|
||||
qcom,support-can-fd;
|
||||
};
|
||||
};
|
||||
|
||||
&pcie1 {
|
||||
qcom,boot-option = <0x0>;
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user