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>
23 * struct hl_special_block_info - stores address details of a particular type of
26 * @block_type: block type as described in every ASIC's block_types enum.
32 * @major_offset: address gap between 2 consecutive major blocks of particular type,
33 * e.g., offset between NIC0_UMR0_0 and NIC1_UMR0_0 is 0x80000.
34 * @minor_offset: address gap between 2 consecutive minor blocks of particular type,
35 * e.g., offset between NIC0_UMR0_0 and NIC0_UMR1_0 is 0x20000.
36 * @sub_minor_offset: address gap between 2 consecutive sub_minor blocks of particular
37 * type, e.g., offset between NIC0_UMR0_0 and NIC0_UMR0_1 is 0x1000.
39 * e.g., in Gaudi2, NIC_UMR blocks can be interpreted as:
41 * In other words, for each of 12 major numbers (i.e 0 to 11) there are
47 * Struct's formatted data is located in the SOL-based auto-generated protbits headers.
61 * struct hl_automated_pb_cfg - represents configurations of a particular type
64 * @addr: address details as described in hl_automation_pb_addr struct.
68 * This bit is meaningful if same bit in data_map is 0, otherwise ignored.
71 * configuration reg is to be written with a value in array pointed
79 * offset 0xE80). '1' in 'data_map' means protection configuration to be done
80 * using configuration in data array. '0' in 'data_map" means protection
81 * configuration to be done as per the value of corresponding bit in 'prot_map'.
82 * '1' in 'prot_map' means the register to be programmed with 0xFFFFFFFF
83 * (all non-protected). '0' in 'prot_map' means the register to be programmed
100 /* struct hl_special_blocks_cfg - holds special blocks cfg data.
120 /* struct hl_skip_blocks_cfg - holds arrays of block types & block ranges to be
140 * struct iterate_special_ctx - HW module special block iterator