From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Rosen Penev <rosenp@gmail.com>, linux-pm@vger.kernel.org
Cc: Georgi Djakov <djakov@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
"open list:ARM/QUALCOMM MAILING LIST"
<linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] interconnect: qcom: fix endian annotations of BCM aux data
Date: Wed, 23 Sep 2026 10:52:29 +0200 [thread overview]
Message-ID: <cacaa28b-28ef-4f69-b002-2757aac2a50b@oss.qualcomm.com> (raw)
In-Reply-To: <20260922182711.25176-1-rosenp@gmail.com>
On 9/22/26 8:27 PM, Rosen Penev wrote:
> struct qcom_icc_bcm::aux_data stores the values parsed from the command
> db, converted to native byte order, but is typed as the raw little-endian
> struct bcm_db. Sparse therefore complains when the converted values are
> assigned to the __le32/__le16 fields and when those restricted fields
> are used in bandwidth calculations.
This should be fixed by using cpu_to_leXX()/leXX_to_cpu() when
accessing these fields instead
Konrad
prev parent reply other threads:[~2026-09-23 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:27 Rosen Penev
2026-09-23 8:52 ` Konrad Dybcio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cacaa28b-28ef-4f69-b002-2757aac2a50b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rosenp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®