Lines Matching +full:in +full:- +full:between

1 /* SPDX-License-Identifier: GPL-2.0
3  * Copyright 2016-2022 HabanaLabs, Ltd.
11 #include <linux/io-64-nonatomic-lo-hi.h>
24  * struct hl_special_block_info - stores address details of a particular type of
27  * @block_type: block type as described in every ASIC's block_types enum.
33  * @major_offset: address gap between 2 consecutive major blocks of particular type,
34  *                e.g., offset between NIC0_UMR0_0 and NIC1_UMR0_0 is 0x80000.
35  * @minor_offset: address gap between 2 consecutive minor blocks of particular type,
36  *                e.g., offset between NIC0_UMR0_0 and NIC0_UMR1_0 is 0x20000.
37  * @sub_minor_offset: address gap between 2 consecutive sub_minor blocks of particular
38  *                    type, e.g., offset between NIC0_UMR0_0 and NIC0_UMR0_1 is 0x1000.
40  * e.g., in Gaudi2, NIC_UMR blocks can be interpreted as:
42  * In other words, for each of 12 major numbers (i.e 0 to 11) there are
48  * Struct's formatted data is located in the SOL-based auto-generated protbits headers.
62  * struct hl_automated_pb_cfg - represents configurations of a particular type
65  * @addr: address details as described in hl_automation_pb_addr struct.
69  *            This bit is meaningful if same bit in data_map is 0, otherwise ignored.
72  *            configuration reg is to be written with a value in array pointed
80  * offset 0xE80). '1' in 'data_map' means protection configuration to be done
81  * using configuration in data array. '0' in 'data_map" means protection
82  * configuration to be done as per the value of corresponding bit in 'prot_map'.
83  * '1' in 'prot_map' means the register to be programmed with 0xFFFFFFFF
84  * (all non-protected). '0' in 'prot_map' means the register to be programmed
101 /* struct hl_special_blocks_cfg - holds special blocks cfg data.
121 /* struct hl_skip_blocks_cfg - holds arrays of block types & block ranges to be
141  * struct iterate_special_ctx - HW module special block iterator