From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Bhaumik Bhatt <bbhatt@codeaurora.org>,
<manivannan.sadhasivam@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <hemantk@codeaurora.org>,
<linux-kernel@vger.kernel.org>, <loic.poulain@linaro.org>,
<linux-wireless@vger.kernel.org>, <kvalo@codeaurora.org>,
<ath11k@lists.infradead.org>
Subject: Re: [PATCH v2 3/6] bus: mhi: Add MMIO region length to controller structure
Date: Wed, 5 May 2021 08:37:32 -0600 [thread overview]
Message-ID: <ee188cdb-3edf-816a-c0b2-88a14fd037f3@quicinc.com> (raw)
In-Reply-To: <1620171478-35679-4-git-send-email-bbhatt@codeaurora.org>
On 5/4/2021 5:37 PM, Bhaumik Bhatt wrote:
> Make controller driver specify the MMIO register region length
> for range checking of BHI or BHIe space. This can help validate
> that offsets are in acceptable memory region or not and avoid any
> boot-up issues due to BHI or BHIe memory accesses.
>
> Signed-off-by: Bhaumik Bhatt <bbhatt@codeaurora.org>
> ---
> include/linux/mhi.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/mhi.h b/include/linux/mhi.h
> index 944aa3a..f6901db 100644
> --- a/include/linux/mhi.h
> +++ b/include/linux/mhi.h
> @@ -293,6 +293,7 @@ struct mhi_controller_config {
> * @mhi_dev: MHI device instance for the controller
> * @debugfs_dentry: MHI controller debugfs directory
> * @regs: Base address of MHI MMIO register space (required)
> + * @reg_len: Length of the MHI MMIO region (required)
I believe this should be moved so that it matches the ordering of the
struct fields below.
With the adjustment, you can add my reviewed tag to this.
> * @bhi: Points to base of MHI BHI register space
> * @bhie: Points to base of MHI BHIe register space
> * @wake_db: MHI WAKE doorbell register address
> @@ -386,6 +387,7 @@ struct mhi_controller {
> size_t rddm_size;
> size_t sbl_size;
> size_t seg_len;
> + size_t reg_len;
> struct image_info *fbc_image;
> struct image_info *rddm_image;
> struct mhi_chan *mhi_chan;
>
next prev parent reply other threads:[~2021-05-05 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 23:37 [PATCH v2 0/6] BHI/BHIe improvements for MHI power purposes Bhaumik Bhatt
2021-05-04 23:37 ` [PATCH v2 1/6] bus: mhi: core: Set BHI/BHIe offsets on power up preparation Bhaumik Bhatt
2021-05-04 23:37 ` [PATCH v2 2/6] bus: mhi: core: Set BHI and BHIe pointers to NULL in clean-up Bhaumik Bhatt
2021-05-04 23:37 ` [PATCH v2 3/6] bus: mhi: Add MMIO region length to controller structure Bhaumik Bhatt
2021-05-05 14:37 ` Jeffrey Hugo [this message]
2021-05-04 23:37 ` [PATCH v2 4/6] ath11k: set register access length for MHI driver Bhaumik Bhatt
2021-05-04 23:37 ` [PATCH v2 5/6] bus: mhi: pci_generic: Set " Bhaumik Bhatt
2021-05-04 23:37 ` [PATCH v2 6/6] bus: mhi: core: Add range checks for BHI and BHIe Bhaumik Bhatt
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=ee188cdb-3edf-816a-c0b2-88a14fd037f3@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=bbhatt@codeaurora.org \
--cc=hemantk@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.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;
as well as URLs for NNTP newsgroup(s).