| /linux-4.4.14/drivers/iio/adc/ |
| D | twl6030-gpadc.c | 120 const struct twl6030_ideal_code *ideal; member
426 static int twl6030_gpadc_lookup(const struct twl6030_ideal_code *ideal, in twl6030_gpadc_lookup() argument
432 if (ideal[i].channel == channel) in twl6030_gpadc_lookup()
441 const struct twl6030_ideal_code *ideal = pdata->ideal; in twl6030_channel_calibrated() local
444 i = twl6030_gpadc_lookup(ideal, channel, pdata->nchannels); in twl6030_channel_calibrated()
446 return pdata->ideal[i].code2; in twl6030_channel_calibrated()
452 const struct twl6030_ideal_code *ideal = gpadc->pdata->ideal; in twl6030_gpadc_make_correction() local
456 i = twl6030_gpadc_lookup(ideal, channel, gpadc->pdata->nchannels); in twl6030_gpadc_make_correction()
492 const struct twl6030_ideal_code *ideal = gpadc->pdata->ideal; in twl6030_gpadc_get_processed() local
502 i = twl6030_gpadc_lookup(ideal, channel, gpadc->pdata->nchannels); in twl6030_gpadc_get_processed()
[all …]
|
| /linux-4.4.14/sound/soc/fsl/ |
| D | fsl_asrc.c | 247 bool ideal; in fsl_asrc_config_pair() local
268 ideal = config->inclk == INCLK_NONE; in fsl_asrc_config_pair()
294 clk = asrc_priv->asrck_clk[clk_index[ideal ? OUT : IN]]; in fsl_asrc_config_pair()
299 inrate, clk_index[ideal ? OUT : IN]); in fsl_asrc_config_pair()
306 if (ideal) in fsl_asrc_config_pair()
365 if (!ideal) in fsl_asrc_config_pair()
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 14 an "ideal, precise multi-tasking CPU" on real hardware.
23 specifies when its next timeslice would start execution on the ideal
35 [ small detail: on "ideal" hardware, at any time all tasks would have the same
37 would ever get "out of balance" from the "ideal" share of CPU time. ]
42 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
|
| D | sched-deadline.txt | 380 now, and be able to change it easily later. The ideal situation (see 5.) is to
|
| /linux-4.4.14/drivers/media/platform/vivid/ |
| D | Kconfig | 17 It is highly configurable and is ideal for testing applications.
|
| /linux-4.4.14/drivers/gpu/drm/omapdrm/ |
| D | TODO | 9 etc..), which isn't really ideal.
|
| /linux-4.4.14/drivers/ras/ |
| D | Kconfig | 28 so have ideal availability, but may be unreliable, with frequent
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 3 KTD2692 is the ideal power solution for high-power flash LEDs.
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 67 thus introducing a small delay in servicing NFS calls. The ideal
82 thing. The ideal rate of change for this counter will be close
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | overview.txt | 11 CPU. This is not ideal and leads to code duplication - for example,
|
| /linux-4.4.14/Documentation/networking/ |
| D | policy-routing.txt | 86 route maintenance, but it is ideal for manual configuration.
|
| D | switchdev.txt | 297 packets up to the bridge driver for flooding. This is not ideal as the number
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | inotify.txt | 72 anything, for that matter. The ideal solution, from all perspectives, is a
|
| /linux-4.4.14/Documentation/ |
| D | futex-requeue-pi.txt | 18 gets to run first in classic thundering-herd formation. An ideal
|
| D | flexible-arrays.txt | 7 pages with vmalloc(). This solution not ideal, though. On 32-bit systems,
|
| D | dma-buf-sharing.txt | 348 it's ideal if the dma_buf fd itself can be used to access the backing storage
|
| D | SubmittingPatches | 777 changelog-style message to the tag; this is an ideal place to describe the
|
| /linux-4.4.14/Documentation/x86/ |
| D | kernel-stacks | 137 marks than ideal.
|
| /linux-4.4.14/fs/ |
| D | Kconfig.binfmt | 40 other. This makes this format ideal for use in environments where no
|
| /linux-4.4.14/Documentation/scsi/ |
| D | FlashPoint.txt | 143 test system provided an ideal environment for testing error recovery
|
| D | tmscsim.txt | 91 precautions. In an ideal world you would have a full backup of your disks.
92 The world isn't ideal and most people don't have full backups (me neither).
|
| /linux-4.4.14/Documentation/timers/ |
| D | timekeeping.txt | 95 system, it is ideal (and customary) to have one such event driving timer per
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 121 It is ideal if drivers can cope with a variable number of MSI interrupts;
277 It is ideal if drivers can cope with a variable number of MSI-X interrupts;
|
| /linux-4.4.14/Documentation/networking/dsa/ |
| D | dsa.txt | 43 The ideal case for using DSA is when an Ethernet switch supports a "switch tag"
581 DSA is currently implemented as a platform device driver which is far from ideal
|
| /linux-4.4.14/Documentation/vm/ |
| D | cleancache.txt | 111 is ideal when data is transformed to a different form and size (such
|
| D | frontswap.txt | 71 This interface is ideal when data is transformed to a different form
|
| D | transhuge.txt | 61 regions but it'd be ideal to move it to tmpfs and the pagecache
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 207 For now, at least, the writing of error-free code remains an ideal that few
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | vivid.txt | 457 ideal frequency. The initial frequency when the driver is loaded is set to
|