RDKCOM-5505: RDKBDEV-3354 IPQ: Bug fixes for QCOM Platform #58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
All contributors have signed the CLA ✍️ ✅ |
VedhaLoganathan
changed the title
pradeeptakdas
changed the title
Signed-off-by: Vedhavalli Loganathan <vedhaval@qti.qualcomm.com>
pradeeptakdas
force-pushed
the
ipq_upstream3
branch
from
ce18dac to
98f6c4a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Increased g_uMaxParamInResponse value for IPQ devices
Reason:
On 6G enablement, IPQ devices were experiencing timeout responses due to the default limit on parameters in the response. To resolve this, the g_uMaxParamInResponse value has been increased in the common library to ensure proper handling.