Home
last modified time | relevance | path

Searched full:sg (Results 1 – 25 of 43) sorted by relevance

12

/Documentation/scsi/
Dscsi-generic.rst4 SCSI Generic (sg) driver
11 The SCSI Generic driver (sg) is one of the four "high level" SCSI device
12 drivers along with sd, st and sr (disk, tape and CD-ROM respectively). Sg
15 Thus sg is used for scanners, CD writers and reading audio CDs digitally
23 Major versions of the sg driver
25 There are three major versions of sg found in the Linux kernel (lk):
26 - sg version 1 (original) from 1992 to early 1999 (lk 2.2.5) .
28 - sg version 2 from lk 2.2.6 in the 2.2 series. It is based on
30 - sg version 3 found in the lk 2.4 series (and the lk 2.5 series).
34 Sg driver documentation
[all …]
Dscsi.rst30 tape driver [1]_ (st.o) and SCSI generics driver (sg.o) represent the upper
DChangeLog.arcmsr48 ** 64 bits sg entry would be incorrectly calculated
84 ** 1.check if the sg list member number
Ddpti.rst58 - Added calculation of resid for sg layer
/Documentation/crypto/
Dapi-samples.rst19 struct scatterlist sg;
73 sg_init_one(&sg, data, datasize);
77 skcipher_request_set_crypt(req, &sg, &sg, datasize, iv);
Dapi-intro.rst58 struct scatterlist sg[2];
74 ahash_request_set_crypt(req, sg, result, 2);
/Documentation/core-api/
Ddma-attributes.rst49 By default dma_map_{single,page,sg} functions family transfer a given
53 performed by calling dma_map_{single,page,sg} function more than once
59 dma_map_{single,page,sg}() for other devices will perform exactly the
66 dma_unmap_{single,page,sg} functions family to force buffer to stay in
Ddma-api.rst376 dma_map_sg(struct device *dev, struct scatterlist *sg,
384 Please note that the sg cannot be mapped again if it has been mapped once.
385 The mapping process is allowed to destroy information in the sg.
396 struct scatterlist *sg;
398 for_each_sg(sglist, sg, count, i) {
399 hw_address[i] = sg_dma_address(sg);
400 hw_len[i] = sg_dma_len(sg);
407 physically contiguous) and returns the actual number of sg entries it
412 accessed sg->address and sg->length as shown above.
417 dma_unmap_sg(struct device *dev, struct scatterlist *sg,
[all …]
Ddma-api-howto.rst589 struct scatterlist *sg;
591 for_each_sg(sglist, sg, count, i) {
592 hw_address[i] = sg_dma_address(sg);
593 hw_len[i] = sg_dma_len(sg);
604 of sg entries it mapped them to. On failure 0 is returned.
608 accessed sg->address and sg->length as shown above.
623 Every dma_map_{single,sg}() call should have its dma_unmap_{single,sg}()
632 So, firstly, just map it with dma_map_{single,sg}(), and after each DMA
663 dma_unmap_{single,sg}(). If you don't touch the data from the first
/Documentation/driver-api/media/drivers/
Dpxa_camera.rst110 | desc-sg[0] | ... | desc-sg[last] | finisher/linker |
116 - desc-sg[i]: i-th descriptor, transferring the i-th sg
119 - linker: has ddadr= desc-sg[0] of next video buffer, dcmd=0
121 For the next schema, let's assume d0=desc-sg[0] .. dN=desc-sg[N],
/Documentation/driver-api/dmaengine/
Dpxa_dma.rst51 | desc-sg[0] | ... | desc-sg[last] | status updater | finisher/linker |
57 - desc-sg[i]: i-th descriptor, transferring the i-th sg
68 - linker: has ddadr= desc-sg[0] of next transfer, dcmd=0
/Documentation/driver-api/virtio/
Dwriting_virtio_drivers.rst152 struct scatterlist sg[1];
153 sg_init_one(sg, buffer, BUFLEN);
154 virtqueue_add_inbuf(dev->vq, sg, 1, buffer, GFP_ATOMIC);
/Documentation/driver-api/
Dscsi.rst74 sg (SCSI Generic)
77 sg (sg.o)
330 For documentation see http://sg.danny.cz/sg/scsi_debug.html
/Documentation/devicetree/bindings/leds/
Dleds-sgm3140.yaml17 http://www.sg-micro.com/uploads/soft/20190626/1561535688.pdf
/Documentation/devicetree/bindings/dma/xilinx/
Dxilinx_dma.txt48 - xlnx,sg-length-width: Should be set to the width in bits of the length
57 1 timeout interval = 125 * clock period of SG clock.
/Documentation/translations/zh_CN/process/
Dvolatile-considered-harmful.rst15 中文版校译者: 张汉辉 Eugene Teo <eugeneteo@kernel.sg>
/Documentation/translations/zh_TW/process/
Dvolatile-considered-harmful.rst17 中文版校譯者: 張漢輝 Eugene Teo <eugeneteo@kernel.sg>
/Documentation/devicetree/bindings/clock/
Dsocionext,uniphier-clock.yaml51 - socionext,uniphier-pro4-sg-clock
/Documentation/driver-api/crypto/iaa/
Diaa-crypto.rst498 …p_sg, src_addr 223925c000, nr_sgs 1, req->src 00000000ee7cb5e6, req->slen 4096, sg_dma_len(sg) 4096
499 …p_sg, dst_addr 21dadf8000, nr_sgs 1, req->dst 000000008d6acea8, req->dlen 4096, sg_dma_len(sg) 8192
650 …p_sg, src_addr 223925c000, nr_sgs 1, req->src 00000000ee7cb5e6, req->slen 4096, sg_dma_len(sg) 4096
651 …p_sg, dst_addr 21dadf8000, nr_sgs 1, req->dst 000000008d6acea8, req->dlen 4096, sg_dma_len(sg) 8192
654 …map_sg, src_addr 21ddd8b100, nr_sgs 1, req->src 0000000084adab64, req->slen 228, sg_dma_len(sg) 228
655 …p_sg, dst_addr 21ee3dc000, nr_sgs 1, req->dst 000000004e2990d0, req->dlen 4096, sg_dma_len(sg) 4096
657 …map_sg, src_addr 21ddd8b100, nr_sgs 1, req->src 0000000084adab64, req->slen 228, sg_dma_len(sg) 228
658 …p_sg, dst_addr 21f1551000, nr_sgs 1, req->dst 000000004e2990d0, req->dlen 4096, sg_dma_len(sg) 4096
/Documentation/devicetree/bindings/soc/socionext/
Dsocionext,uniphier-soc-glue.yaml111 compatible = "socionext,uniphier-pro4-sg-clock";
/Documentation/arch/arm/stm32/
Dstm32-dma-mdma-chaining.rst245 /* Create sg table for STM32 DMA channel */
248 dev_err(dev, "DMA sg table alloc failed\n");
263 /* Create sg table for STM32 MDMA channel */
379 it. STM32 MDMA channel will be stopped by HW in case of sg transfer, but not
393 "removed" from the sg or the cyclic transfer.
/Documentation/fb/
Ddeferred_io.rst36 whether to coalesce and issue SG DMA or to do memory bursts.
/Documentation/devicetree/bindings/arm/
Darm,coresight-tmc.yaml75 Indicates that the TMC-ETR can safely use the SG mode on this system.
/Documentation/arch/x86/x86_64/
Dboot-options.rst265 Do scatter-gather (SG) merging. Implies "force" (experimental).
267 Don't do scatter-gather (SG) merging.
/Documentation/driver-api/mmc/
Dmmc-test.rst204 | 23 | Best-case read performance | Performs 512K sequential read (non sg) |
208 | 25 | Best-case read performance | Same using sg |
242 | 41 | Write performance | Blocking req 1 to 512 sg elems |
244 | 42 | Write performance | Non-blocking req 1 to 512 sg elems |
246 | 43 | Read performance | Blocking req 1 to 512 sg elems |
248 | 44 | Read performance | Non-blocking req 1 to 512 sg elems |

12