Searched full:will (Results 151 – 175 of 18360) sorted by relevance
12345678910>>...735
| /linux-6.15/drivers/staging/media/atomisp/pci/ |
| D | ia_css_pipe_public.h | 79 will OSYS receive, this resolution is equal to the output resolution of GDC
80 if not determined CSS will set output_system_in_res with main osys output pin resolution
95 then setting a zoom factor will have no effect.
101 /** Enabling BCI mode will cause yuv_scale binary to be picked up
140 * ~~~** DO NOT ADD NEW FIELD **~~~ This structure will be deprecated.
154 smaller than the input resolution, cropping will be performed by
155 the ISP. The first cropping that will be performed is on the upper
165 /** After an image pipe is created, this field will contain the info
168 /** After an image pipe is created, this field will contain the grid
173 many initial frames will contain invalid data; this allows the
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/rocketlake/ |
| D | floating-point.json | 12 …d double precision floating-point instructions retired; some instructions will count twice as note…
16 …d double precision floating-point instructions retired; some instructions will count twice as note…
21 …d single precision floating-point instructions retired; some instructions will count twice as note…
25 …d single precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
34 …d double precision floating-point instructions retired; some instructions will count twice as note…
39 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …d single precision floating-point instructions retired; some instructions will count twice as note…
48 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
52 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/tigerlake/ |
| D | floating-point.json | 12 …d double precision floating-point instructions retired; some instructions will count twice as note…
16 …d double precision floating-point instructions retired; some instructions will count twice as note…
21 …d single precision floating-point instructions retired; some instructions will count twice as note…
25 …d single precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
34 …d double precision floating-point instructions retired; some instructions will count twice as note…
39 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …d single precision floating-point instructions retired; some instructions will count twice as note…
48 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
52 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/icelake/ |
| D | floating-point.json | 12 …d double precision floating-point instructions retired; some instructions will count twice as note…
16 …d double precision floating-point instructions retired; some instructions will count twice as note…
21 …d single precision floating-point instructions retired; some instructions will count twice as note…
25 …d single precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
34 …d double precision floating-point instructions retired; some instructions will count twice as note…
39 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …d single precision floating-point instructions retired; some instructions will count twice as note…
48 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
52 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.15/drivers/char/ |
| D | Kconfig | 50 <file:Documentation/admin-guide/parport.rst>. The module will be called lp.
71 busy..) the kernel will stall until the printer is ready again.
92 module will be called ppdev.
106 /dev/vportNpn will be created when corresponding ports are
109 attribute called 'name' will be populated with a name for
127 will be created which exposes the operator panel display on IBM
156 times the button was pressed will be written to that device.
164 button; it will still execute a hard reset if the button is held
168 module will be called nwbutton.
170 Most people will answer Y to this question and "Reboot Using Button"
[all …]
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/icelakex/ |
| D | floating-point.json | 12 …d double precision floating-point instructions retired; some instructions will count twice as note…
16 …d double precision floating-point instructions retired; some instructions will count twice as note…
21 …d single precision floating-point instructions retired; some instructions will count twice as note…
25 …d single precision floating-point instructions retired; some instructions will count twice as note…
30 …d double precision floating-point instructions retired; some instructions will count twice as note…
34 …d double precision floating-point instructions retired; some instructions will count twice as note…
39 …d single precision floating-point instructions retired; some instructions will count twice as note…
43 …d single precision floating-point instructions retired; some instructions will count twice as note…
48 …56-bit packed double precision FP instructions retired; some instructions will count twice as note…
52 … double precision floating-point instructions retired; some instructions will count twice as note…
[all …]
|
| /linux-6.15/Documentation/filesystems/ |
| D | debugfs.rst | 17 even debugfs interfaces are best designed with the idea that they will need
32 of business will be to create at least one directory to hold a set of
37 This call, if successful, will make a directory called name underneath the
38 indicated parent directory. If parent is NULL, the directory will be
44 of the functions described below will work.
54 should hold the file, data will be stored in the i_private field of the
58 the return value will be a dentry pointer to the created file,
109 As might be expected, this function will create a debugfs file to represent
126 A read on the resulting file will yield either Y (for non-zero values) or
127 N, followed by a newline. If written to, it will accept either upper- or
[all …]
|
| /linux-6.15/Documentation/driver-api/fpga/ |
| D | fpga-mgr.rst | 79 The ops will implement whatever device specific register writes are needed to
89 The .parse_header function will set header_size and data_size to
92 .write function will get image buffer starting at header_size offset from the
93 beginning. If data_size is set, .write function will get data_size bytes of
94 the image buffer, otherwise .write will get data up to the end of image buffer.
95 This will not affect .write_sg, .write_sg will still get whole image in
97 whole buffer will be passed into .parse_header. If image is in scatter-gather
98 form, core code will buffer up at least .initial_header_size before the first
100 size into info->header_size and return -EAGAIN, then it will be called again
103 The .write_init function will prepare the FPGA to receive the image data. The
[all …]
|
| /linux-6.15/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 62 You will also want CoreSight support enabled in your kernel config.
84 When you run perf test, it will do a lot of self tests. Some of those
85 tests will cover CoreSight (only if enabled and on ARM64). You
87 kernel tree. Some tests will check some internal perf support like:
92 Some others will actually use perf record and some test binaries that
93 are in tests/shell/coresight and will collect traces to ensure a
95 tests are in the same directory. These will all look like:
102 These perf record tests will not run if the tool binaries do not exist
103 in tests/shell/coresight/\*/ and will be skipped. If you do not have
108 These tests will log historical results in the current working
[all …]
|
| /linux-6.15/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 20 command line is not present, the driver will register a backlight device
22 interface control. For every registered class device, there will be a
31 on read, control method _BQC will be evaluated to
34 not implemented, will set the current brightness instead;
36 on write, control method _BCM will run to set the requested brightness level;
42 Note that ACPI video backlight driver will always use index for
79 i) For some laptops, when user presses the hotkey, a scancode will be
82 following key code will appear to user space::
91 ii) For some laptops, the press of the hotkey will not generate the
92 scancode, instead, firmware will notify the video device ACPI node
[all …]
|
| /linux-6.15/Documentation/usb/ |
| D | iuu_phoenix.rst | 9 IUU unit in phoenix mode. Loading this module will
18 You can plug more than one IUU. Every unit will
50 - clockmode will provide 3 different base settings commonly adopted by
62 This will put the reader in a base of 3Mhz579 but boosted a 195 % !
63 the real clock will be now : 6979050 Hz ( 6Mhz979 ) and will increase
75 - debug will produce a lot of debugging messages...
82 is an abstraction, so use any speed or parity setting will
83 work. ( This will not change anything ).Later I will perhaps
|
| /linux-6.15/drivers/iio/humidity/ |
| D | Kconfig | 16 This driver can also be built as a module. If so, the module will
36 This driver can also be built as a module. If so, the module will be
50 will be called hdc100x.
60 will be called hdc2010.
72 will be called hdc3020.
85 will be called hid-sensor-humidity.
99 will be called hts221.
121 This driver can also be built as a module. If so, the module will
132 will be called si7005. This driver also
144 will be called si7020.
|
| /linux-6.15/drivers/net/ieee802154/ |
| D | Kconfig | 11 If you say N, all options in this submenu will be skipped and
22 The module will be called 'fakelb'.
34 the module will be called 'at86rf230'.
46 the module will be called 'mrf24j40'.
57 the module will be called 'cc2520'.
67 The module will be called 'atusb'.
78 the module will be called 'adf7242'.
90 the module will be called 'ca8210'.
112 the module will be called 'mcr20a'.
123 The module will be called 'mac802154_hwsim'.
|
| /linux-6.15/arch/riscv/ |
| D | Kconfig.errata | 8 this Kconfig will disable all Andes errata. Please say "Y"
19 This will apply the cache management errata to handle the
29 this Kconfig will disable all SiFive errata. Please say "Y"
39 This will apply the SiFive CIP-453 errata to add sign extension
50 This will apply the SiFive CIP-1200 errata to repalce all
80 this Kconfig will disable all T-HEAD errata. Please say "Y"
91 This will apply the memory attribute extension errata to handle the
104 This will apply the cache management errata to handle the
117 This will apply the overflow errata to handle the non-standard
128 instruction set. When this errata is enabled, the CPUs will be probed
|
| /linux-6.15/Documentation/core-api/ |
| D | cachetlb.rst | 28 Therefore when software page table changes occur, the kernel will
35 any previous page table modification whatsoever will be
46 'mm' will be visible to the cpu. That is, after running,
47 there will be no entries in the TLB for 'mm'.
60 'start' to 'end-1' will be visible to the cpu. That is, after
61 running, there will be no entries in the TLB for 'mm' for
85 user virtual address 'addr' will be visible to the cpu. That
86 is, after running, there will be no entries in the TLB for
110 the sequence will be in one of the following forms::
124 The cache level flush will always be first, because this allows
[all …]
|
| /linux-6.15/drivers/tty/serial/8250/ |
| D | Kconfig | 21 module will be called 8250.
23 non-standard serial ports, since the configuration information will
34 Most people will say Y or M here, so that they can use serial mice,
77 Selecting this option will add support for the RS232 and RS485
81 If this option is not selected the device will be configured as a
93 If you say Y here, it will be possible to use a serial port as the
100 (/dev/tty0) will still be used as the system console by default, but
107 kernel will automatically use the first serial line, /dev/ttyS0, as
113 and it will switch to normal serial console when the corresponding
117 it will not only setup early console.
[all …]
|
| /linux-6.15/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 108 characters. It should uniquely represent the volume and will be matched with
112 fscache will look up or create a cache cookie of that name and will use a cache
114 it will use the first cache that comes to hand and set the name to that.
116 The specified coherency data is stored in the cookie and will be matched
118 is provided. If the coherency data doesn't match, the entire cache volume will
124 pass a NULL cookie to any function that takes a volume cookie. This will
135 This will cause the volume to be committed or removed, and if sealed the
136 coherency data will be set to the value supplied. The amount of coherency data
164 of size aux_data_len will be allocated and the coherency data copied in. It is
170 used to trim the data and will be stored with the coherency data.
[all …]
|
| /linux-6.15/drivers/net/ethernet/ti/ |
| D | Kconfig | 14 kernel: saying N will just cause the configurator to skip all
15 the questions about TI devices. If you say Y, you will be asked for
30 will be called davinci_emac_driver. This is recommended.
41 will be called davinci_mdio. This is recommended.
63 will be called cpsw.
80 will be called cpsw_new.
114 will be called ti-am65-cpsw-nuss.
159 will be called keystone_netcp.
167 will be called keystone_netcp_ethss.
182 will be called tlan.
[all …]
|
| /linux-6.15/drivers/gpu/drm/tiny/ |
| D | Kconfig | 13 module will be called appletbdrm.
24 If M is selected the module will be called arcpgu.
36 If M is selected the module will be called bochs.
128 If M is selected the module will be called hx8357d.
142 If M is selected the module will be called ili9163.
155 If M is selected the module will be called ili9225.
169 If M is selected the module will be called ili9341.
184 If M is selected the module will be called ili9486.
196 If M is selected the module will be called mi0283qt.
211 If M is selected the module will be called repaper.
[all …]
|
| /linux-6.15/Documentation/devicetree/bindings/net/ |
| D | mediatek-dwmac.yaml | 86 or will round down. Range 0~31*170.
88 or will round down. Range 0~31*550.
90 or will round down. Range 0~31*290.
96 or will round down. Range 0~31*170.
98 or will round down. Range 0~31*550.
100 of 290, or will round down. Range 0~31*290.
118 1. tx clock will be inversed in MII/RGMII case,
119 2. tx clock inside MAC will be inversed relative to reference clock
121 3. the reference clock, which outputs to TXC pin will be inversed in RMII case
128 1. rx clock will be inversed in MII/RGMII case.
[all …]
|
| /linux-6.15/Documentation/userspace-api/media/v4l/ |
| D | dev-decoder.rst | 220 * The full set of supported formats will be returned, regardless of the
231 will be returned.
242 format will include all possible coded resolutions supported by the
246 will include all possible frame buffer resolutions supported by the
269 from the stream for the given coded format; otherwise the decoder will
270 use this resolution as a placeholder resolution that will likely change
285 * The ``CAPTURE`` format will be updated with an appropriate frame buffer
289 after the decoder is done parsing the information from the stream, it will
358 buffers will be processed and returned to the client in order, until
364 this to occur. Processing of the buffers will continue as long as more
[all …]
|
| /linux-6.15/drivers/media/test-drivers/vidtv/ |
| D | vidtv_psi.h | 404 * This will free the previous service loop in the table.
405 * This will assign ownership of the service loop to the table, i.e. the table
406 * will free this service loop when a call to its destroy function is made.
415 * @desc: The descriptor loop that will be assigned.
417 * This will free the loop in 'to', if any.
424 * @pmt: The PMT section that will contain the descriptor loop
426 * @desc: The descriptor loop that will be assigned.
428 * This will free the loop in 'to', if any.
429 * This will assign ownership of the loop to the table, i.e. the table
430 * will free this loop when a call to its destroy function is made.
[all …]
|
| /linux-6.15/Documentation/admin-guide/media/ |
| D | cafe_ccic.rst | 16 RGB565, and RGB444 formats. (Anybody looking at the code will see RGB32 as
17 well, but that is a debugging aid which will be removed shortly). VGA and
21 To try it out: either of these commands will work:
36 - alloc_bufs_at_load: Normally, the driver will not allocate any DMA
38 then worst-case-sized buffers will be allocated at module load time.
44 allocated at run time, they will be sized appropriately for the current
49 systems, however, it will work well with only two.
52 will consent to work with. Default is one, but, on slower systems,
60 - flip: If this boolean parameter is set, the sensor will be instructed to
|
| /linux-6.15/drivers/iio/frequency/ |
| D | Kconfig | 22 module will be called ad9523.
40 module will be called adf4350.
51 module will be called adf4371.
62 module will be called adf4377.
72 module will be called admfm2000.
82 module will be called admv1013.
92 module will be called admv1014.
103 module will be called admv4420.
114 module will be called adrf6780.
|
| /linux-6.15/Documentation/filesystems/nfs/ |
| D | rpc-cache.rst | 48 It will also contain a key and some content.
105 includes it on a list of caches that will be regularly
113 This will be passed to ->match to identify the target entry. If no
114 entry is found, a new entry will be create, added to the cache, and
117 The item returned is typically passed to cache_check which will check
119 cache_check will return -ENOENT in the entry is negative or if an up
128 item does become valid, the deferred copy of the request will be
129 revisited (->revisit). It is expected that this method will
154 expected that a message written will contain:
169 Successive reads will return successive requests.
[all …]
|
12345678910>>...735