STRUCT HTE_CHIP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

struct hte_chip β€” Abstract HTE chip. This is from the Kernel API Manual, section 9, bestie, and it's literally the blueprint for an HTE chip. No cap.


✨ SYNOPSIS ✨

okay so the struct is exactly this, every field present and accounted for πŸ’…

       struct hte_chip {
           const char *name;
           struct device *dev;
           const struct hte_ops *ops;
           u32 nlines;
           int (*xlate_of)(struct hte_chip *gc, const struct of_phandle_args
       *args, struct hte_ts_desc *desc, u32 *xlated_id);
           int (*xlate_plat)(struct hte_chip *gc, struct hte_ts_desc *desc, u32
       *xlated_id);
           bool (*match_from_linedata)(const struct hte_chip *chip, const
       struct hte_ts_desc *hdesc);
           u8 of_hte_n_cells;
           struct hte_device *gdev;
           void *data;
        };

πŸ¦‹ Members πŸ¦‹

okay bestie, here's every single member and what it does. We are not skipping one, periodt.

  • name β€” functional name of the HTE IP block. It's giving name tag energy.
  • dev β€” device providing the HTE. Like, the actual device behind the vibes.
  • ops β€” callbacks for this HTE. The whole callback situation.
  • nlines β€” number of lines/signals supported by this chip. That's the line count, no cap.
  • xlate_of β€” callback that translates consumer-supplied logical ids to physical ids. It returns 0 for the success and negative for the failures, and on success it stores a value between 0 to nlines in the xlated_id parameter. Bestie, 0 is the slay, negative is the fail 😭
  • xlate_plat β€” literally same as above but for the consumers with no DT node. No DT, no problem 🫢
  • match_from_linedata β€” match HTE device using the line_data. It's giving matchmaker energy.
  • of_hte_n_cells β€” number of cells used to form the HTE specifier. Important little cell count.
  • gdev β€” HTE subsystem abstract device, internal to the HTE subsystem. iykyk, it's internal.
  • data β€” chip specific private data. Private means private, bestie πŸ’…

🌈 SEE ALSO 🌈

Kernel file ./include/linux/hte.h β€” yes, that's the file. Then the whole reading list, in order: enum hte_edge(9), enum hte_return(9), struct hte_ts_data(9), struct hte_clk_info(9), hte_ts_cb_t(9), hte_ts_sec_cb_t(9), struct hte_line_attr(9), struct hte_ts_desc(9), struct hte_ops(9). Obsessed with a linked-list of lore? Same.


okay bestie, that's the whole page. Source: ./include/linux; version/date: October 2026; page: struct hte_chip(9). Stay slaying, and remember: no cap, read the header file πŸ’–βœ¨

πŸ“¦ where this page comes from