Home
last modified time | relevance | path

Searched refs:link_order (Results 1 – 3 of 3) sorted by relevance

/OK3568_Linux_fs/kernel/drivers/media/i2c/
H A Dmax9286.c918 static const u8 link_order[] = { in max9286_setup() local
963 max9286_write(priv, 0x0b, link_order[priv->route_mask]); in max9286_setup()
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/info/
H A Dbfd.info1692 The data within a section is stored in a "link_order". These are much
1693 like the fixups in 'gas'. The link_order abstraction allows a section
1696 A link_order knows how big it is, and which is the next link_order
1700 The link_order is used by the linker to perform relaxing on final
1705 so it does it on a link_order by link_order basis.
2121 struct bfd_link_order *link_order;
7232 struct bfd_link_order *link_order,
7797 /* Do a link based on the link_order structures attached to each
9834 Each section in the output file will have a list of 'link_order'
9835 structures attached to the 'map_head.link_order' field (the 'link_order'
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/info/
H A Dbfd.info1692 The data within a section is stored in a "link_order". These are much
1693 like the fixups in 'gas'. The link_order abstraction allows a section
1696 A link_order knows how big it is, and which is the next link_order
1700 The link_order is used by the linker to perform relaxing on final
1705 so it does it on a link_order by link_order basis.
2121 struct bfd_link_order *link_order;
7232 struct bfd_link_order *link_order,
7797 /* Do a link based on the link_order structures attached to each
9834 Each section in the output file will have a list of 'link_order'
9835 structures attached to the 'map_head.link_order' field (the 'link_order'
[all …]