Searched refs:relevant (Results 1 – 12 of 12) sorted by relevance
16 are returned to relevant protocol drivers based on their
10 * Remove the HAL layer and migrate its functionality into the relevant parts of
575 bool relevant = (item->buck_id <= variant_parameters[chip->variant_id].num_bucks); in da9121_status_poll_on() local580 if (relevant && supported && persisting && now_cleared) { in da9121_status_poll_on()646 bool relevant = (item->buck_id <= variant_parameters[chip->variant_id].num_bucks); in da9121_irq_handler() local651 if (relevant && enabled && active) { in da9121_irq_handler()
15 * struct rx_ring is used for rx and tx completions, with some members relevant
68 indentation deep making it very unpleasant to read. This is specially relevant
82 drive the relevant pins.
180 relevant. This driver provides a reset controller capable of
501 FIXME: is it relevant for us? in aty_init_pll_ct()
34 # controller, and the relevant drivers for each function declared
1921 supported via the relevant subsystems. This driver provides1935 supported via the relevant subsystems. This driver provides core2041 the relevant subsystems. This driver provides core support for the
10 uses pata-platform driver to enable the relevant driver in the
500 Support for CBUS access using I2C API. Mostly relevant for Nokia