Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: quic_carlv@quicinc.com, quic_thanson@quicinc.com,
	mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
	Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
Subject: Re: [PATCH] bus: mhi: host: Allocate entire MHI control config once
Date: Fri, 25 Apr 2025 10:11:42 -0600	[thread overview]
Message-ID: <62f86d8d-e196-4d3a-b432-33da98bc5db7@oss.qualcomm.com> (raw)
In-Reply-To: <qjgzfuzb57etwsblgsdnek6pmw4c5ickt2yaiprqzskhjwr2zb@vwstguwle4m4>

On 4/24/2025 11:40 PM, Manivannan Sadhasivam wrote:
> On Fri, Mar 28, 2025 at 10:59:13AM -0600, Jeff Hugo wrote:
>> From: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
>>
>> MHI control configurations such as channel context, event context, command
>> context and rings, are currently allocated individually. During MHI
>> initialization MHI bus driver needs to configure the address space in
>> which this control configuration resides. Since different component of the
>> config is being allocated separately, only logical solution is to give the
>> entire RAM address space, as they could be anywhere.
>>
>> As per MHI specification the MHI control configuration address space should
>> not be more them 4GB.
> 
> Could you please add the spec limitation here as you described in your reply?

Will do.

> 
>>
>> Since the current implementation is in violation of MHI specification.
> 
> Here too.
> 
>> Allocate a single giant DMA buffer for MHI control configurations and
>> limit the configuration address space to that buffer.
>>
>> Signed-off-by: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
>> Signed-off-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
> 
> Other than that, patch looks good to me.
> 
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> 
> - Mani

      reply	other threads:[~2025-04-25 16:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 16:59 [PATCH] bus: mhi: host: Allocate entire MHI control config once Jeff Hugo
2025-04-08  7:01 ` Manivannan Sadhasivam
2025-04-08 14:56   ` Jeff Hugo
2025-04-25  5:37     ` Manivannan Sadhasivam
2025-04-25 16:10       ` Jeff Hugo
2025-04-25 16:56       ` Jeff Johnson
2025-04-28 16:04         ` Manivannan Sadhasivam
2025-04-28  1:37     ` Baochen Qiang
2025-04-28 15:09       ` Jeff Hugo
2025-04-29  1:44         ` Baochen Qiang
2025-05-12 18:33           ` Jeff Hugo
2025-04-25  5:40 ` Manivannan Sadhasivam
2025-04-25 16:11   ` Jeff Hugo [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=62f86d8d-e196-4d3a-b432-33da98bc5db7@oss.qualcomm.com \
    --to=jeff.hugo@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mhi@lists.linux.dev \
    --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