android/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
cba97f251a
android_kernel_xiaomi_sm8450/include/uapi/linux/msm_ion_ids.h

35 lines
1.1 KiB
C
Raw Normal View History

ion: msm: Define heap IDs as constants in their own file The ION heap IDs are also needed by the device-tree to provide the kernel with the heap ID for the heap that a device-tree entry describes. Currently, these IDs are hard-coded, which can be error-prone when updating the heap IDs. Thus, create a header that can also be accessed by the device-tree and userspace, and move the heap IDs to that header. This makes it so that the device-tree can now use the constants defined in the header, instead of hard-coded IDs, making updates significantly easier. Change-Id: I58b1aae9924504f2b20e159b9be8da7a2ee8d248 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-05 02:57:57 +09:00
/* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
/*
ion: msm: Add support for the Trusted UI(TUI) dynamic carveout heap Add support to allow usage of memory from the TUI dynamic carveout heap. Change-Id: I585b68215f2f5e8ab114f1c83c19b3bc77a65845 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2020-02-05 09:03:24 +09:00
* Copyright (c) 2019-2020, The Linux Foundation. All rights reserved.
ion: msm: Define heap IDs as constants in their own file The ION heap IDs are also needed by the device-tree to provide the kernel with the heap ID for the heap that a device-tree entry describes. Currently, these IDs are hard-coded, which can be error-prone when updating the heap IDs. Thus, create a header that can also be accessed by the device-tree and userspace, and move the heap IDs to that header. This makes it so that the device-tree can now use the constants defined in the header, instead of hard-coded IDs, making updates significantly easier. Change-Id: I58b1aae9924504f2b20e159b9be8da7a2ee8d248 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-05 02:57:57 +09:00
*/
#ifndef _MSM_ION_IDS_H
#define _MSM_ION_IDS_H
ion: msm: Update the heap IDs as per the ION core standards Update the heap IDs as per the standard imposed by the ION core (i.e.): SYSTEM_HEAP: (1 << 0) SYSTEM_CONTIG_HEAP: (1 << 1) CARVEOUT_HEAPS: [(1 << 2), (1 << 6)] CHUNK_HEAP: (1 << 7) CMA_HEAPS: [(1 << 8), (1 << 15)] VENDOR_HEAPS: [(1 << 16), (1 << 31)] Since the heap IDs are now bitmasks, as opposed to offsets within a bitmask, update the userspace ION_HEAP() macro/as well as the heap ID treatment in the kernel to account for this as well. Change-Id: I6b7ca1caf89dda03dfb499a362db863168c2753c Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-20 02:29:28 +09:00
#define ION_BIT(nr) (1U << (nr))
ion: msm: Define heap IDs as constants in their own file The ION heap IDs are also needed by the device-tree to provide the kernel with the heap ID for the heap that a device-tree entry describes. Currently, these IDs are hard-coded, which can be error-prone when updating the heap IDs. Thus, create a header that can also be accessed by the device-tree and userspace, and move the heap IDs to that header. This makes it so that the device-tree can now use the constants defined in the header, instead of hard-coded IDs, making updates significantly easier. Change-Id: I58b1aae9924504f2b20e159b9be8da7a2ee8d248 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-05 02:57:57 +09:00
/**
* These are the only ids that should be used for Ion heap ids.
* The ids listed are the order in which allocation will be attempted
* if specified. Don't swap the order of heap ids unless you know what
* you are doing!
* Id's are spaced by purpose to allow new Id's to be inserted in-between (for
* possible fallbacks)
*/
ion: msm: Update the heap IDs as per the ION core standards Update the heap IDs as per the standard imposed by the ION core (i.e.): SYSTEM_HEAP: (1 << 0) SYSTEM_CONTIG_HEAP: (1 << 1) CARVEOUT_HEAPS: [(1 << 2), (1 << 6)] CHUNK_HEAP: (1 << 7) CMA_HEAPS: [(1 << 8), (1 << 15)] VENDOR_HEAPS: [(1 << 16), (1 << 31)] Since the heap IDs are now bitmasks, as opposed to offsets within a bitmask, update the userspace ION_HEAP() macro/as well as the heap ID treatment in the kernel to account for this as well. Change-Id: I6b7ca1caf89dda03dfb499a362db863168c2753c Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-20 02:29:28 +09:00
#define ION_SYSTEM_HEAP_ID ION_BIT(0)
ion: msm: Add support for the Trusted UI(TUI) dynamic carveout heap Add support to allow usage of memory from the TUI dynamic carveout heap. Change-Id: I585b68215f2f5e8ab114f1c83c19b3bc77a65845 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2020-02-05 09:03:24 +09:00
#define ION_TUI_CARVEOUT_HEAP_ID ION_BIT(2)
ion: msm: Update the heap IDs as per the ION core standards Update the heap IDs as per the standard imposed by the ION core (i.e.): SYSTEM_HEAP: (1 << 0) SYSTEM_CONTIG_HEAP: (1 << 1) CARVEOUT_HEAPS: [(1 << 2), (1 << 6)] CHUNK_HEAP: (1 << 7) CMA_HEAPS: [(1 << 8), (1 << 15)] VENDOR_HEAPS: [(1 << 16), (1 << 31)] Since the heap IDs are now bitmasks, as opposed to offsets within a bitmask, update the userspace ION_HEAP() macro/as well as the heap ID treatment in the kernel to account for this as well. Change-Id: I6b7ca1caf89dda03dfb499a362db863168c2753c Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-20 02:29:28 +09:00
#define ION_QSECOM_TA_HEAP_ID ION_BIT(8)
#define ION_CAMERA_HEAP_ID ION_BIT(9)
#define ION_ADSP_HEAP_ID ION_BIT(11)
#define ION_USER_CONTIG_HEAP_ID ION_BIT(13)
#define ION_QSECOM_HEAP_ID ION_BIT(14)
#define ION_AUDIO_HEAP_ID ION_BIT(15)
#define ION_CP_MM_HEAP_ID ION_BIT(16)
#define ION_SECURE_HEAP_ID ION_BIT(17)
#define ION_SECURE_DISPLAY_HEAP_ID ION_BIT(18)
#define ION_SPSS_HEAP_ID ION_BIT(21)
#define ION_SECURE_CARVEOUT_HEAP_ID ION_BIT(22)
#define ION_HEAP_ID_RESERVED ION_BIT(31)
ion: msm: Define heap IDs as constants in their own file The ION heap IDs are also needed by the device-tree to provide the kernel with the heap ID for the heap that a device-tree entry describes. Currently, these IDs are hard-coded, which can be error-prone when updating the heap IDs. Thus, create a header that can also be accessed by the device-tree and userspace, and move the heap IDs to that header. This makes it so that the device-tree can now use the constants defined in the header, instead of hard-coded IDs, making updates significantly easier. Change-Id: I58b1aae9924504f2b20e159b9be8da7a2ee8d248 Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
2019-09-05 02:57:57 +09:00
#endif /* _MSM_ION_IDS_H */
Reference in New Issue Copy Permalink