From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: "Jeffrey Hugo" <quic_jhugo@quicinc.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Jeff Johnson" <jjohnson@kernel.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, mhi@lists.linux.dev,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
qiang.yu@oss.qualcomm.com, quic_vbadigan@quicinc.com,
quic_vpernami@quicinc.com, quic_mrana@quicinc.com,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Subject: Re: [PATCH v3 07/11] bus: mhi: host: Add support to read MHI capabilities
Date: Wed, 21 May 2025 20:36:54 +0530 [thread overview]
Message-ID: <8bb9acff-b2cf-edb0-bd55-251cf4a93f5b@oss.qualcomm.com> (raw)
In-Reply-To: <aa45ff83-bc8f-4cef-a82c-9a868396d19d@quicinc.com>
On 5/21/2025 8:22 PM, Jeffrey Hugo wrote:
> On 5/19/2025 3:42 AM, Krishna Chaitanya Chundru wrote:
>> From: Vivek Pernamitta <quic_vpernami@quicinc.com>
>>
>> As per MHI spec v1.2,sec 6.6, MHI has capability registers which are
>> located after the ERDB array. The location of this group of registers is
>> indicated by the MISCOFF register. Each capability has a capability ID to
>> determine which functionality is supported and each capability will point
>> to the next capability supported.
>>
>> Add a basic function to read those capabilities offsets.
>>
>> Signed-off-by: Vivek Pernamitta <quic_vpernami@quicinc.com>
>> Signed-off-by: Krishna Chaitanya Chundru
>> <krishna.chundru@oss.qualcomm.com>
>> ---
>> drivers/bus/mhi/common.h | 4 ++++
>> drivers/bus/mhi/host/init.c | 29 +++++++++++++++++++++++++++++
>> 2 files changed, 33 insertions(+)
>>
>> diff --git a/drivers/bus/mhi/common.h b/drivers/bus/mhi/common.h
>> index
>> dda340aaed95a5573a2ec776ca712e11a1ed0b52..eedac801b80021e44f7c65d33cd50760e06c02f2 100644
>> --- a/drivers/bus/mhi/common.h
>> +++ b/drivers/bus/mhi/common.h
>> @@ -16,6 +16,7 @@
>> #define MHICFG 0x10
>> #define CHDBOFF 0x18
>> #define ERDBOFF 0x20
>> +#define MISCOFF 0x24
>> #define BHIOFF 0x28
>> #define BHIEOFF 0x2c
>> #define DEBUGOFF 0x30
>> @@ -113,6 +114,9 @@
>> #define MHISTATUS_MHISTATE_MASK GENMASK(15, 8)
>> #define MHISTATUS_SYSERR_MASK BIT(2)
>> #define MHISTATUS_READY_MASK BIT(0)
>> +#define MISC_CAP_MASK GENMASK(31, 0)
>> +#define CAP_CAPID_MASK GENMASK(31, 24)
>> +#define CAP_NEXT_CAP_MASK GENMASK(23, 12)
>> /* Command Ring Element macros */
>> /* No operation command */
>> diff --git a/drivers/bus/mhi/host/init.c b/drivers/bus/mhi/host/init.c
>> index
>> 13e7a55f54ff45b83b3f18b97e2cdd83d4836fe3..a7137a040bdce1c58c98fe9c2340aae4cc4387d1 100644
>> --- a/drivers/bus/mhi/host/init.c
>> +++ b/drivers/bus/mhi/host/init.c
>> @@ -467,6 +467,35 @@ int mhi_init_dev_ctxt(struct mhi_controller
>> *mhi_cntrl)
>> return ret;
>> }
>> +static int mhi_find_capability(struct mhi_controller *mhi_cntrl, u32
>> capability, u32 *offset)
>> +{
>> + u32 val, cur_cap, next_offset;
>> + int ret;
>> +
>> + /* Get the 1st supported capability offset */
>
> "first"? Does not seem like you are short on space here.
>
Misc register will have the offest of the 1st capability register
from there capabilities will have linked list format.
>> + ret = mhi_read_reg_field(mhi_cntrl, mhi_cntrl->regs, MISCOFF,
>> + MISC_CAP_MASK, offset);
>
> This fits on one line.
>
>> + if (ret)
>> + return ret;
>
> Blank line here would be nice.
>
>> + do {
>> + if (*offset >= mhi_cntrl->reg_len)
>> + return -ENXIO;
>> +
>> + ret = mhi_read_reg(mhi_cntrl, mhi_cntrl->regs, *offset, &val);
>> + if (ret)
>> + return ret;
>
>
> There is no sanity checking we can do on val? We've had plenty of
> issues blindly trusting the device. I would like to avoid having more.
>
we can check if val is not all F's as sanity other than that we can't
check any other things as we don't know if the value is valid or not.
Let me know if you have any taught on this.
> Also looks like if we find the capability we are looking for, we return
> the offset without validating it.
>
For offset I can have a check to make sure the offset is not crossing
mhi reg len like above.
- Krishna Chaitanya.
>> +
>> + cur_cap = FIELD_GET(CAP_CAPID_MASK, val);
>> + next_offset = FIELD_GET(CAP_NEXT_CAP_MASK, val);
>> + if (cur_cap == capability)
>> + return 0;
>> +
>> + *offset = next_offset;
>> + } while (next_offset);
>> +
>> + return -ENXIO;
>> +}
>> +
>> int mhi_init_mmio(struct mhi_controller *mhi_cntrl)
>> {
>> u32 val;
>>
>
next prev parent reply other threads:[~2025-05-21 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 9:42 [PATCH v3 00/11] bus: mhi: host: Add support for mhi bus bw Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 01/11] PCI: Update current bus speed as part of pci_pwrctrl_notify() Krishna Chaitanya Chundru
2025-05-19 13:09 ` Ilpo Järvinen
2025-05-20 4:05 ` Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 02/11] PCI/bwctrl: Add support to scale bandwidth before & after link re-training Krishna Chaitanya Chundru
2025-05-19 13:41 ` Ilpo Järvinen
2025-05-20 4:06 ` Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 03/11] PCI/ASPM: Return enabled ASPM states as part of pcie_aspm_enabled() Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 04/11] PCI/ASPM: Clear aspm_disable as part of __pci_enable_link_state() Krishna Chaitanya Chundru
2025-05-19 13:21 ` Ilpo Järvinen
2025-05-20 4:12 ` Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 05/11] PCI: qcom: Extract core logic from qcom_pcie_icc_opp_update() Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 06/11] PCI: qcom: Add support for PCIe bus bw scaling Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 07/11] bus: mhi: host: Add support to read MHI capabilities Krishna Chaitanya Chundru
2025-05-21 14:52 ` Jeffrey Hugo
2025-05-21 15:06 ` Krishna Chaitanya Chundru [this message]
2025-05-21 15:32 ` Jeffrey Hugo
2025-05-19 9:42 ` [PATCH v3 08/11] bus: mhi: host: Add support for Bandwidth scale Krishna Chaitanya Chundru
2025-05-19 13:48 ` Ilpo Järvinen
2025-05-19 9:42 ` [PATCH v3 09/11] PCI: Export pci_set_target_speed() Krishna Chaitanya Chundru
2025-05-19 13:30 ` Ilpo Järvinen
2025-05-19 9:42 ` [PATCH v3 10/11] PCI: Add function to convert lnkctl2speed to pci_bus_speed Krishna Chaitanya Chundru
2025-05-19 9:42 ` [PATCH v3 11/11] wifi: ath11k: Add support for MHI bandwidth scaling Krishna Chaitanya Chundru
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=8bb9acff-b2cf-edb0-bd55-251cf4a93f5b@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jingoohan1@gmail.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=qiang.yu@oss.qualcomm.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=quic_vpernami@quicinc.com \
--cc=robh@kernel.org \
/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