Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml

Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml

File Facts

System
Linux kernel
Corpus path
Documentation/devicetree/bindings/net/can/ti,tcan4x5x.yaml
Extension
.yaml
Size
5788 bytes
Lines
200
Domain
Support Tooling And Documentation
Bucket
Documentation
Inferred role
Support Tooling And Documentation: configuration, schema, or hardware description
Status
atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

Detected Declarations

Annotated Snippet

# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/net/can/ti,tcan4x5x.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Texas Instruments TCAN4x5x CAN Controller

maintainers:
  - Marc Kleine-Budde <mkl@pengutronix.de>

properties:
  compatible:
    oneOf:
      - items:
          - enum:
              - ti,tcan4552
              - ti,tcan4553
          - const: ti,tcan4x5x
      - const: ti,tcan4x5x

  reg:
    maxItems: 1

  interrupts:
    maxItems: 1
    description: The GPIO parent interrupt.

  clocks:
    maxItems: 1

  clock-names:
    items:
      - const: cclk

  reset-gpios:
    description: Hardwired output GPIO. If not defined then software reset.
    maxItems: 1

  device-state-gpios:
    description:
      Input GPIO that indicates if the device is in a sleep state or if the
      device is active. Not available with tcan4552/4553.
    maxItems: 1

  device-wake-gpios:
    description:
      Wake up GPIO to wake up the TCAN device.
      Not available with tcan4552/4553.
    maxItems: 1

  bosch,mram-cfg:
    description: |
      Message RAM configuration data.
      Multiple M_CAN instances can share the same Message RAM
      and each element(e.g Rx FIFO or Tx Buffer and etc) number
      in Message RAM is also configurable, so this property is
      telling driver how the shared or private Message RAM are
      used by this M_CAN controller.

      The format should be as follows:
      <offset sidf_elems xidf_elems rxf0_elems rxf1_elems rxb_elems txe_elems txb_elems>
      The 'offset' is an address offset of the Message RAM where
      the following elements start from. This is usually set to
      0x0 if you're using a private Message RAM. The remain cells
      are used to specify how many elements are used for each FIFO/Buffer.

      M_CAN includes the following elements according to user manual:
      11-bit Filter	0-128 elements / 0-128 words
      29-bit Filter	0-64 elements / 0-128 words

Annotation

Implementation Notes