Searched refs:persistence (Results 1 – 17 of 17) sorted by relevance
74 u8 persistence; member
245 .persistence = 255,659 chip->tsl2x7x_settings.persistence; in tsl2x7x_chip_on()1036 filter_delay = z * (chip->tsl2x7x_settings.persistence & 0x0F); in tsl2x7x_als_persistence_show()1062 chip->tsl2x7x_settings.persistence &= 0xF0; in tsl2x7x_als_persistence_store()1063 chip->tsl2x7x_settings.persistence |= (filter_delay & 0x0F); in tsl2x7x_als_persistence_store()1082 filter_delay = z * ((chip->tsl2x7x_settings.persistence & 0xF0) >> 4); in tsl2x7x_prox_persistence_show()1108 chip->tsl2x7x_settings.persistence &= 0x0F; in tsl2x7x_prox_persistence_store()1109 chip->tsl2x7x_settings.persistence |= ((filter_delay << 4) & 0xF0); in tsl2x7x_prox_persistence_store()
99 scm_attr(persistence);140 scmdev->attrs.persistence = sale->p; in scmdev_setup()
88 unsigned int persistence:4; member
111 unsigned char persistence; member147 if (((sp->status1 & SIXP_DCD_MASK) == 0) && (random < sp->persistence)) { in sp_xmit_on_air()200 case 2: sp->persistence = p[1]; in sp_encaps()620 sp->persistence = SIXP_PERSIST; in sixpack_open()
97 about in-kernel persistence:105 - Why OPTIONAL in-kernel persistence may be a good idea sometimes:
157 persistence template if it is to be used to schedule a new218 Controls the synchronisation of connections when using persistence223 for normal connections, do it only for persistence templates.
113 Filtered by persistence filter (prox0_thresh_above_count)
1 USB device persistence during system suspend74 reset or otherwise had lost power) then it applies a persistence check
23 Say N here if you don't want USB power session persistence
296 tristate "SIP persistence engine"300 Allow persistence based on the SIP Call-ID
294 not required for dentry persistence.298 refcounts are not required for persistence. Also we are free to perform mount
368 bool "Enable FPU state persistence across context switch"
719 persistance||persistence
102 Only the physical mode provides persistence of the data. i.e. The
174 and the backend guarantees the persistence of the data. In this case,
470 persistence!) but that's fine - it's a part of kernel development.