From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Baochen Qiang <quic_bqiang@quicinc.com>,
quic_carlv@quicinc.com, quic_thanson@quicinc.com,
manivannan.sadhasivam@linaro.org
Cc: mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
ath11k@lists.infradead.org, jjohnson@kernel.org,
Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
Subject: Re: [PATCH v2] bus: mhi: host: Allocate entire MHI control config once
Date: Mon, 12 May 2025 12:31:41 -0600 [thread overview]
Message-ID: <d97c900d-c899-4f2c-821b-53991ecfd86e@oss.qualcomm.com> (raw)
In-Reply-To: <1f2a8c11-214b-43c6-8b3a-9e44094f949a@quicinc.com>
On 4/27/2025 7:57 PM, Baochen Qiang wrote:
>
>
> On 4/26/2025 1:04 AM, Jeff Hugo wrote:
>> From: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
>> int mhi_init_mmio(struct mhi_controller *mhi_cntrl)
>> @@ -475,6 +497,7 @@ int mhi_init_mmio(struct mhi_controller *mhi_cntrl)
>> struct mhi_event *mhi_event;
>> void __iomem *base = mhi_cntrl->regs;
>> struct device *dev = &mhi_cntrl->mhi_dev->dev;
>> + dma_addr_t mhi_ctrl_limit = mhi_cntrl->ctrl_config_dma + mhi_cntrl->ctrl_config_size - 1;
>
> but the range [ctrl_config_dma, mhi_ctrl_limit] could still be possbile to cross the 4GB
> boundary, no?
Its possible, yes. From a practical standpoint, that seems to be
unlikely as the control area is not terribly large on supported platforms.
next prev parent reply other threads:[~2025-05-12 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 17:04 [PATCH v2] bus: mhi: host: Allocate entire MHI control config once Jeff Hugo
2025-04-28 1:57 ` Baochen Qiang
2025-05-12 18:31 ` Jeff Hugo [this message]
2025-05-13 1:43 ` Baochen Qiang
2025-05-16 15:09 ` Jeff Hugo
2025-05-16 23:53 ` Baochen Qiang
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=d97c900d-c899-4f2c-821b-53991ecfd86e@oss.qualcomm.com \
--to=jeff.hugo@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=quic_bqiang@quicinc.com \
--cc=quic_carlv@quicinc.com \
--cc=quic_pkanojiy@quicinc.com \
--cc=quic_thanson@quicinc.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