Searched refs:by (Results 1 – 25 of 3611) sorted by relevance
12345678910>>...145
16 Userspace software can test for features by acquiring the AT_HWCAP entry29 Where software relies on a feature described by a hwcap, it should check43 which are described by architected ID registers inaccessible to50 Functionality implied by idreg.field == val.55 indicate the absence of functionality implied by other values of59 described by ID registers alone. These may be described without68 Functionality implied by ID_AA64PFR0_EL1.FP == 0b0000.72 Functionality implied by ID_AA64PFR0_EL1.AdvSIMD == 0b0000.81 Functionality implied by ID_AA64ISAR1_EL1.AES == 0b0001.85 Functionality implied by ID_AA64ISAR1_EL1.AES == 0b0010.[all …]
3 This document is maintained by Keiichi KII <k-keiichi@bx.jp.nec.com>336 Signed-off-by: Random J Developer <random@developer.example.org>352 Signed-off-by とあなたがその末尾に追加する Signed-off-by の間に、修正を358 Signed-off-by: Random J Developer <random@developer.example.org>360 Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org>388 13) いつ Acked-by: と Cc: を使うのか390 「 Signed-off-by: 」タグはその署名者がパッチの開発に関わっていたことやパッチ394 る承認を記録し、示したいとします。その場合、その人を示すのに Acked-by: が使395 えます。Acked-by: はパッチのチェンジログにも追加されます。398 の伝播パスにいなかった時にも、メンテナは Acked-by: をしばしば利用します。[all …]
7 * it under the terms of the GNU General Public License as published by81 cpu-release-addr = <0>; // Fixed by the boot loader89 cpu-release-addr = <0>; // Fixed by the boot loader97 cpu-release-addr = <0>; // Fixed by the boot loader105 cpu-release-addr = <0>; // Fixed by the boot loader113 cpu-release-addr = <0>; // Fixed by the boot loader121 cpu-release-addr = <0>; // Fixed by the boot loader129 cpu-release-addr = <0>; // Fixed by the boot loader137 cpu-release-addr = <0>; // Fixed by the boot loader145 cpu-release-addr = <0>; // Fixed by the boot loader[all …]
15 * booting cluster (big or LITTLE) is chosen by IROM code by reading33 #cooling-cells = <2>; /* min followed by max */45 #cooling-cells = <2>; /* min followed by max */57 #cooling-cells = <2>; /* min followed by max */69 #cooling-cells = <2>; /* min followed by max */81 #cooling-cells = <2>; /* min followed by max */93 #cooling-cells = <2>; /* min followed by max */105 #cooling-cells = <2>; /* min followed by max */117 #cooling-cells = <2>; /* min followed by max */
14 * booting cluster (big or LITTLE) is chosen by IROM code by reading32 #cooling-cells = <2>; /* min followed by max */44 #cooling-cells = <2>; /* min followed by max */56 #cooling-cells = <2>; /* min followed by max */68 #cooling-cells = <2>; /* min followed by max */80 #cooling-cells = <2>; /* min followed by max */92 #cooling-cells = <2>; /* min followed by max */104 #cooling-cells = <2>; /* min followed by max */116 #cooling-cells = <2>; /* min followed by max */
156 .set by, \b define167 .rept (by - 1)183 club DDQ_DATA, by191 .rept (by - 1)200 .rept by215 .rept by221 add $(16*by), p_in232 .rept by246 .rept by266 .rept by[all …]
8 Written by John R. Hauser. This work was made possible in part by the10 Street, Berkeley, California 94704. Funding was partially provided by the14 overseen by Profs. Nelson Morgan and John Wawrzynek. More information34 Shifts `a' right by the number of bits given in `count'. If any nonzero36 the result by setting the least significant bit to 1. The value of `count'39 The result is stored in the location pointed to by `zPtr'.59 Shifts `a' right by the number of bits given in `count'. If any nonzero61 the result by setting the least significant bit to 1. The value of `count'64 The result is stored in the location pointed to by `zPtr'.87 Shifts the 128-bit value formed by concatenating `a0' and `a1' right by 64[all …]
9 These formats are not defined by this specification, they are just46 - 8 bit RGB format used by the BTTV driver.51 - YUV 4:2:0 format used by the IVTV driver,60 - YUV format used by the gspca cpia1 driver.71 - YUYV per line used by the gspca driver.76 - YYUV per line used by the gspca driver.81 - YUVY per line used by the gspca driver.86 - Compressed GBRG Bayer format used by the gspca driver.91 - Compressed BGGR Bayer format used by the gspca driver.96 - Compressed BGGR Bayer format used by the gspca driver.[all …]
33 - Reserved for future extensions. Should be zeroed by drivers and77 - Flags set by the application or driver, see :ref:`format-flags`.84 This information supplements the ``colorspace`` and must be set by85 the driver for capture streams and by the application for output90 This information supplements the ``colorspace`` and must be set by91 the driver for capture streams and by the application for output99 This information supplements the ``colorspace`` and must be set by100 the driver for capture streams and by the application for output105 This information supplements the ``colorspace`` and must be set by106 the driver for capture streams and by the application for output[all …]
37 - The pixel format or type of compression, set by the application.59 the value requested by the application, returning ``width`` times60 bytes per pixel or a larger value required by the hardware. That71 to the first plane and is divided by the same factor as the82 - Size in bytes of the buffer to hold a complete image, set by the90 by the driver for capture streams and by the application for102 must first ensure that the feature is supported by querying the120 - Flags set by the application or driver, see :ref:`format-flags`.127 This information supplements the ``colorspace`` and must be set by128 the driver for capture streams and by the application for output[all …]
31 areas that can be sampled is given by the ``V4L2_SEL_TGT_CROP_BOUNDS``37 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.43 Each capture device has a default source rectangle, given by the53 the image size set by :ref:`VIDIOC_S_FMT <VIDIOC_G_FMT>`.55 The part of a buffer into which the image is inserted by the hardware is56 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's69 The part of a buffer that is modified by the hardware is given by71 ``V4L2_SEL_TGT_COMPOSE`` plus all padding data modified by hardware73 be changed by the hardware. The content of pixels that lie inside the96 the area from which image date are processed by the hardware, is given[all …]
26 other entities. Data (not restricted to video) produced by an entity37 A media device is represented by a struct :c:type:`media_device`39 Allocation of the structure is handled by the media device driver, usually by43 Drivers register media device instances by calling45 and unregistered by calling :c:func:`media_device_unregister()`.50 Entities are represented by a struct :c:type:`media_entity`56 Drivers initialize entity pads by calling59 Drivers register entities with a media device by calling61 and unregistred by calling67 Interfaces are represented by a[all …]
16 | bit 63. The fraction is multiplied by 10 using a mul by 217 | shift and a mul by 8 shift. The bits shifted out of the28 | A3. Multiply the fraction in d2:d3 by 8 using bit-field32 | A4. Multiply the fraction in d4:d5 by 2 using shifts. The msb33 | will be collected by the carry.51 | d2: upper 32-bits of fraction for mul by 852 | d3: lower 32-bits of fraction for mul by 853 | d4: upper 32-bits of fraction for mul by 254 | d5: lower 32-bits of fraction for mul by 287 | A3. Multiply d2:d3 by 8; extract msbs into d1.[all …]
8 Note that bits are numbered as by the usual s390 convention (most significant15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies16 all supported DIAGNOSE calls need to be handled by either KVM or its19 All DIAGNOSE calls supported by KVM use the RS-a format:26 The second-operand address (obtained by the base/displacement calculation)30 The supported DIAGNOSE function codes vary by the userspace used. For50 Handled by userspace.53 Handled by userspace.56 Handled by userspace.59 Handled by either userspace or KVM (ioeventfd case).[all …]
5 are not saved by the BIOS and so do not persist after unload and reload.18 If the dsp irq has not been setup and stored in bios by the 20 irq used by the dsp to be configured.23 If the dsp io range has not been setup and stored in bios by the 25 io range used by the dsp to be configured.28 If the mwave's uart irq has not been setup and stored in bios by the 30 irq used by the mwave uart to be configured.33 If the uart io range has not been setup and stored in bios by the 35 io range used by the mwave uart to be configured.
11 to be present on a single jack but handled by separate bits of18 This is done by splitting the jacks up into three things working19 together: the jack itself represented by a struct snd_soc_jack, sets of33 user space. The jack itself is completely passive, it is set up by the34 machine driver and updated by jack detection methods.36 Jacks are created by the machine driver calling snd_soc_jack_new().42 bits supported by the jack. Each snd_soc_jack has zero or more of these43 which are updated automatically. They are created by the machine driver52 Actual jack detection is done by code which is able to monitor some53 input to the system and update a jack by calling snd_soc_jack_report(),[all …]
10 All firmware packages on the Modules or Interfaces are managed by a special11 Firmware Management Protocol. To support Firmware Management by the AP, the61 be used by the user to identify the right character device for it. The class76 The Character device (gb-fw-mgmt-0 in example) can be opened by the userspace142 This ioctl shall be used by the user to get the version and firmware-tag of144 fw_mgmt_ioc_get_fw' are filled by the kernel.148 This ioctl shall be used by the user to get the version of a currently149 running Backend Interface Firmware identified by a firmware-tag. The user is151 in this case. The 'major' and 'minor' fields are set by the kernel in156 This ioctl shall be used by the user to load an Interface Firmware package on[all …]
53 protected by pcmcia_socket_list_rwsem;58 The resource_ops and their data are protected by ops_mutex.63 - by pcmcia_socket_list_rwsem:66 - by thread_lock:69 - by skt_mutex:75 - by ops_mutex:103 - by pcmcia_socket->ops_mutex:114 - by the PCMCIA driver:
9 Should be selected by any drivers that do in-kernel push15 Provides the generic IIO DMA buffer infrastructure that can be used by18 Should be selected by drivers that want to use the generic DMA buffer26 DMAengine framework. This can be used by converter drivers with a DMA port27 connected to an external DMA controller which is supported by the30 Should be selected by drivers that want to use this functionality.37 are handled by hardware.39 Should be selected by drivers that want to use the generic Hw consumer
21 For the processors supported by ``intel_pstate``, the P-state concept is broader23 `LinuxCon Europe 2015 presentation by Kristen Accardi <LCEU2015_>`_ for more25 by ``intel_pstate`` internally follows the hardware specification (for details29 frequencies are involved in the user space interface exposed by it, so34 that. Some functionality of the core is limited by that.36 Since the hardware P-state selection interface used by ``intel_pstate`` is77 For example, the ``powersave`` P-state selection algorithm provided by81 There are two P-state selection algorithms provided by ``intel_pstate`` in the86 Which of the P-state selection algorithms is used by default depends on the88 Namely, if that option is set, the ``performance`` algorithm will be used by[all …]
4 The "concap" interface is intended to be used by network device6 It is assumed that the protocol interacts with a linux network device by28 encapsulation protocols. The encapsulation protocol is configured by a35 encapsulation is usually done by just sticking a header on the data. Thus,37 encapsulation protocol directly (usually by just providing a hard_header()62 isdn_net.c harder to maintain. Thus, by identifying an abstract68 Likewise, a similar encapsulation protocol will frequently be needed by70 synchronous ppp implementation used by the isdn driver and the71 asynchronous ppp implementation used by the ppp driver have a lot of98 - process (xmit) data handed down by upper protocol layer[all …]
1 Functions Exported by fmc.ko26 allocated by the caller, but must not be released after unregistering.31 by carriers that host more than one mezzanine. The devices must all be35 are already driven by a reprogrammed FPGA.37 If a carrier hosts slots that are driven by different FPGA devices, it38 should register as a group only mezzanines that are driven by the same42 *note The API Offered by Carriers:: and also scans the memory area for45 entry point. The function is meant to factorize common code, and by46 the time you read this it is already used by the spec-sw and fine-delay
11 A consumer driver can get access to its supply regulator by calling :-16 then finds the correct regulator by consulting a machine specific lookup table.24 Consumers can be supplied by more than one regulator e.g. codec consumer with37 A consumer can enable its power supply by calling:-43 previously enabled by bootloader or kernel board initialization code.45 A consumer can determine if a regulator is enabled by calling :-52 A consumer can disable its supply when no longer needed by calling :-75 Consumers can control their supply voltage by calling :-87 The regulators configured voltage output can be found by calling :-105 Consumers can control their supply current limit by calling :-[all …]
4 Note that normally these interfaces are used only by the utilities in7 nfsd is controlled mainly by pseudofiles under the "nfsd" filesystem,10 The server is always started by the first write of a nonzero value to13 Before doing that, NFSD can be told which sockets to listen on by26 nfsd is shut down by a write of 0 to nfsd/threads. All locks and state30 or down by additional writes to nfsd/threads or by writes to
8 - dma-channels: Number of channels supported by hardware.9 - snps,dma-masters: Number of AXI masters supported by the hardware.10 - snps,data-width: Maximum AXI data width supported by hardware.15 - snps,block-size: Maximum block size supported by the controller channel.19 - snps,axi-max-burst-len: Restrict master AXI burst length by value specified21 supported by DMAC is used. [1:256]
