mirror of
git://nv-tegra.nvidia.com/linux-nv-oot.git
synced 2025-12-22 09:11:26 +03:00
d8a3d29fed
Method to configure the struct queue_limits has changed from kernel v6.11. The following API's are removed from v6.11 [1] blk_queue_max_secure_erase_sectors [2] blk_queue_max_discard_sectors [3] blk_queue_write_cache [4] blk_queue_logical_block_size [5] blk_queue_physical_block_size [6] blk_queue_max_hw_sectors [7] The semantics of the flag QUEUE_FLAG_NONROT is set as default value for queues, so this flag is removed in v6.11. [8] The flag BLK_MQ_F_SHOULD_MERGE is not valid in v6.14 The above API's are replaced by direct assignment to the queue_limits and use the new API queue_limits_set. This API takes the incoming values, validates, populates the other members of the struct accordingly and assigns the provided queue_limits to the corresponding queue. The change contains: [1] Addition of new approach that is compatible with v6.11 [2] Addition of a macro (NV_BLOCK_USE_QUEUE_LIMITS_SET) for backward compatibility [3] This is a special case where both the variable and the function needs to be present for the macro to be enabled. The changes were made accordingly. [4] The flag BLK_MQ_F_SHOULD_MERGE is protected by macro Bug 4311184 Signed-off-by: gokull <gokull@nvidia.com> Change-Id: Ida2c12de0977f6405e7cc7dec946cf0f64413c97 Reviewed-on: https://git-master.nvidia.com/r/c/linux-nv-oot/+/3303900 Reviewed-by: Jon Hunter <jonathanh@nvidia.com> Reviewed-by: svcacv <svcacv@nvidia.com> GVS: buildbot_gerritrpt <buildbot_gerritrpt@nvidia.com>