| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | inside-secure,safexcel.yaml | 4 $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel.yaml# 7 title: Inside Secure SafeXcel cryptographic engine 17 - const: inside-secure,safexcel-eip197b 22 - const: inside-secure,safexcel-eip97ies 23 - const: inside-secure,safexcel-eip197b 24 - const: inside-secure,safexcel-eip197d 25 - const: inside-secure,safexcel-eip97ies 26 - const: inside-secure,safexcel-eip197 27 description: Equivalent of inside-secure,safexcel-eip197b 29 - const: inside-secure,safexcel-eip97 [all …]
|
| H A D | inside-secure,safexcel-eip93.yaml | 4 $id: http://devicetree.org/schemas/crypto/inside-secure,safexcel-eip93.yaml# 7 title: Inside Secure SafeXcel EIP-93 cryptographic engine 13 The Inside Secure SafeXcel EIP-93 is a cryptographic engine IP block 16 developed by Inside Secure and given to license to vendors. 35 - const: inside-secure,safexcel-eip93ies 40 - inside-secure,safexcel-eip93i 41 - inside-secure,safexcel-eip93ie 42 - inside-secure,safexcel-eip93is 43 - inside-secure,safexcel-eip93iw 63 compatible = "airoha,en7581-eip93", "inside-secure,safexcel-eip93ies";
|
| /linux/Documentation/devicetree/bindings/ |
| H A D | .yamllint | 15 min-spaces-inside: 0 16 max-spaces-inside: 1 17 min-spaces-inside-empty: 0 18 max-spaces-inside-empty: 0 20 min-spaces-inside: 0 21 max-spaces-inside: 1 22 min-spaces-inside-empty: 0 23 max-spaces-inside-empty: 0
|
| /linux/Documentation/devicetree/bindings/rng/ |
| H A D | inside-secure,safexcel-eip76.yaml | 4 $id: http://devicetree.org/schemas/rng/inside-secure,safexcel-eip76.yaml# 7 title: Inside-Secure HWRNG Module 18 - inside-secure,safexcel-eip76 22 - const: inside-secure,safexcel-eip76 54 - inside-secure,safexcel-eip76 78 compatible = "inside-secure,safexcel-eip76";
|
| /linux/drivers/nfc/microread/ |
| H A D | Kconfig | 6 This module contains the main code for Inside Secure microread 11 tristate "Inside Secure Microread device support (I2C)" 16 Inside microread chipsets. Select this if your platform is using 23 tristate "Inside Secure Microread device support (MEI)" 28 Inside microread chipsets. Select this if your microread chipset
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | preempt_lock.c | 11 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 19 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 28 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 38 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 60 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 68 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg… 77 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_preempt_disable-ed reg…
|
| H A D | irq.c | 34 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 46 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 60 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 86 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 96 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 108 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi… 122 __failure __msg("BPF_EXIT instruction in main prog cannot be used inside bpf_local_irq_save-ed regi…
|
| H A D | exceptions_fail.c | 139 __failure __msg("bpf_throw cannot be used inside bpf_rcu_read_lock-ed region") 155 __failure __msg("bpf_throw cannot be used inside bpf_rcu_read_lock-ed region") 370 __failure __msg("bpf_throw cannot be used inside bpf_rcu_read_lock-ed region") 378 __failure __msg("bpf_throw cannot be used inside bpf_preempt_disable-ed region") 388 __failure __msg("bpf_throw cannot be used inside bpf_local_irq_save-ed region")
|
| /linux/rust/kernel/list/ |
| H A D | arc.rs | 19 /// a [`ListArc`] exists or not. We refer to this logic as "the tracking inside `T`". 21 /// We allow the case where the tracking inside `T` thinks that a [`ListArc`] exists, but actually, 28 /// A consequence of the above is that you may implement the tracking inside `T` by not actually 34 /// Informs the tracking inside this type that it now has a [`ListArc`] reference. 36 /// This method may be called even if the tracking inside this type thinks that a `ListArc` 44 /// Informs the tracking inside this type that there is no [`ListArc`] reference anymore. 66 /// Additionally, this call will have transitioned the tracking inside `Self` from not thinking 73 /// This macro supports a few different strategies for implementing the tracking inside the type: 143 /// relevant tracking is referred to as "the tracking inside `T`", and the [`ListArcSafe`] trait 146 /// Note that we allow the case where the tracking inside ` [all...] |
| /linux/drivers/gpu/drm/i915/ |
| H A D | i915_gem_gtt.c | 75 * @size: how much space to allocate inside the GTT, 77 * @offset: where to insert inside the GTT, 84 * i915_gem_gtt_reserve() tries to insert the @node at the exact @offset inside 159 * @size: how much space to allocate inside the GTT, 165 * @start: start of any range restriction inside GTT (0 for all), 167 * @end: end of any range restriction inside GTT (U64_MAX for all), 262 * make room inside the aperture. The eviction scan then has to walk in i915_gem_gtt_insert() 264 * it has to search for a new hole between every byte inside the memcpy, in i915_gem_gtt_insert()
|
| /linux/drivers/iio/accel/ |
| H A D | mma9551_core.c | 211 * Locking is not handled inside the function. Callers should ensure they 236 * Locking is not handled inside the function. Callers should ensure they 261 * Locking is not handled inside the function. Callers should ensure they 286 * Locking is not handled inside the function. Callers should ensure they 320 * Locking is not handled inside the function. Callers should ensure they 347 * Locking is not handled inside the function. Callers should ensure they 380 * Locking is not handled inside the function. Callers should ensure they 419 * Locking is not handled inside the function. Callers should ensure they 458 * Locking is not handled inside the function. Callers should ensure they 493 * Locking is not handled inside the function. Callers should ensure they [all …]
|
| /linux/drivers/gpu/drm/bridge/ |
| H A D | tc358775.c | 72 #define CLS_PRE 0x0180 /* Digital Counter inside of PHY IO */ 73 #define D0S_PRE 0x0184 /* Digital Counter inside of PHY IO */ 74 #define D1S_PRE 0x0188 /* Digital Counter inside of PHY IO */ 75 #define D2S_PRE 0x018C /* Digital Counter inside of PHY IO */ 76 #define D3S_PRE 0x0190 /* Digital Counter inside of PHY IO */ 77 #define CLS_PREP 0x01A0 /* Digital Counter inside of PHY IO */ 78 #define D0S_PREP 0x01A4 /* Digital Counter inside of PHY IO */ 79 #define D1S_PREP 0x01A8 /* Digital Counter inside of PHY IO */ 80 #define D2S_PREP 0x01AC /* Digital Counter inside of PHY IO */ 81 #define D3S_PREP 0x01B0 /* Digital Counter inside of PHY IO */ [all …]
|
| /linux/arch/csky/include/asm/ |
| H A D | tcm.h | 16 /* Tag functions inside TCM called from outside TCM with this */ 18 /* Tag function inside TCM called from inside TCM with this */
|
| /linux/drivers/crypto/ccree/ |
| H A D | cc_aead.h | 33 #define CCM_BLOCK_NONCE_OFFSET 1 /* Nonce offset inside B0 and CTR_COUNT */ 34 #define CCM_BLOCK_NONCE_SIZE 3 /* Nonce size inside B0 and CTR_COUNT */ 35 #define CCM_BLOCK_IV_OFFSET 4 /* IV offset inside B0 and CTR_COUNT */ 36 #define CCM_BLOCK_IV_SIZE 8 /* IV size inside B0 and CTR_COUNT */
|
| /linux/Documentation/accel/ |
| H A D | introduction.rst | 11 These devices can be either stand-alone ASICs or IP blocks inside an SoC/GPU. 20 or an IP inside a SoC (e.g. laptop web camera). These devices 24 type of device can be stand-alone or an IP inside a SoC or a GPU. It will 34 a method of scaling-up/out, i.e. connecting to other training cards inside 46 Because this type of devices can be an IP inside GPUs or have similar
|
| /linux/arch/arm/include/asm/ |
| H A D | tcm.h | 20 /* Tag functions inside TCM called from outside TCM with this */ 22 /* Tag function inside TCM called from inside TCM with this */
|
| /linux/net/netfilter/ |
| H A D | nf_nat_proto.c | 525 } *inside; in nf_nat_icmp_reply_translation() local 534 if (skb_ensure_writable(skb, hdrlen + sizeof(*inside))) in nf_nat_icmp_reply_translation() 539 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation() 540 if (inside->icmp.type == ICMP_REDIRECT) { in nf_nat_icmp_reply_translation() 559 if (!nf_nat_ipv4_manip_pkt(skb, hdrlen + sizeof(inside->icmp), in nf_nat_icmp_reply_translation() 564 /* Reloading "inside" here since manip_pkt may reallocate */ in nf_nat_icmp_reply_translation() 565 inside = (void *)skb->data + hdrlen; in nf_nat_icmp_reply_translation() 566 inside->icmp.checksum = 0; in nf_nat_icmp_reply_translation() 567 inside->icmp.checksum = in nf_nat_icmp_reply_translation() 840 } *inside; in nf_nat_icmpv6_reply_translation() local [all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | selection-api-configuration.rst | 40 active cropping area must lie completely inside the capture boundaries. 59 bounds rectangle. The composing rectangle must lie completely inside 74 be changed by the hardware. The content of pixels that lie inside the 100 must lie completely inside the crop boundaries and the driver may 111 composing rectangle must lie completely inside the bounds rectangle. The
|
| /linux/rust/syn/ |
| H A D | verbatim.rs | 22 if let Some((inside, _span, after)) = cursor.group(Delimiter::None) { in between() 24 cursor = inside; in between() 27 panic!("verbatim end must not be inside a delimited group"); in between()
|
| /linux/drivers/s390/char/ |
| H A D | sclp_ocf.c | 54 /* Find the 0x9f22 block inside the 0x9f00 block. */ in sclp_ocf_handler() 58 /* Find the 0x81 block inside the 0x9f22 block. */ in sclp_ocf_handler() 62 /* Find the 0x01 block inside the 0x81 block. */ in sclp_ocf_handler() 64 /* Find the 0x02 block inside the 0x81 block. */ in sclp_ocf_handler()
|
| /linux/drivers/block/rnbd/ |
| H A D | rnbd-srv.h | 21 /* Entry inside global sess_list */ 33 /* Entry inside global dev_list */ 47 /* Entry inside rnbd_srv_dev struct */
|
| /linux/security/apparmor/include/ |
| H A D | cred.h | 76 * of the label so it is safe to call when inside of locks. 88 * This fn will not update the tasks cred, so it is safe inside of locks 126 * safe to call inside locks 197 * safe to call inside locks 214 * Not safe to call inside locks
|
| /linux/fs/btrfs/ |
| H A D | subpage.h | 64 * Structure to trace status of each sector inside a page, attached to 82 * How many sectors inside the page is locked. 141 * the range is ensured to be inside the folio's single page. 145 * But the range still needs to be inside one single page. 148 * need to be inside the page. Those functions will truncate the range
|
| /linux/Documentation/doc-guide/ |
| H A D | kernel-doc.rst | 208 Inside a ``struct`` or ``union`` description, you can use the ``private:`` and 209 ``public:`` comment tags. Structure fields that are inside a ``private:`` 247 * @bar.st1: struct st1 inside @bar 248 * @bar.st2: struct st2 inside @bar 281 ``foo`` is named, the member ``bar`` inside it should be documented as 314 /** @bar2: Description for struct @bar2 inside @foo */ 317 * @bar2.barbar: Description for @barbar inside @foo.bar2 435 This is particularly useful if you need to use things like ``%ph`` inside 615 The output will be at ``/man`` directory inside the output directory 626 the files explicitly inside a ``Documentation/{subdir}/.../*.rst`` file.
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | stericsson,u8500-clks.yaml | 13 description: While named "U8500 clocks" these clocks are inside the 53 5, 6. The second cell indicates which clock inside the PRCC block it 67 second cell indicates which clock inside the PRCC block it wants, possible 81 5 and 6. The second cell indicates which reset line inside the PRCC block
|