All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sibi Sankar <sibis@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Joerg Roedel <joro@8bytes.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Jordan Crouse <jcrouse@codeaurora.org>,
	Rob Clark <robdclark@gmail.com>,
	Stephen Boyd <swboyd@chromium.org>,
	iommu@lists.linux-foundation.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Matthias Kaehlcke <mka@chromium.org>,
	Evan Green <evgreen@chromium.org>,
	linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCHv4 4/6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Thu, 07 May 2020 19:44:01 +0530	[thread overview]
Message-ID: <f41beaa18f0ba49c3c6f7552291a0641@codeaurora.org> (raw)
In-Reply-To: <20200507130210.GB31783@willie-the-truck>

Hey WIll,

On 2020-05-07 18:32, Will Deacon wrote:
> On Tue, Apr 21, 2020 at 12:03:52AM +0530, Sai Prakash Ranjan wrote:
>> From: Sibi Sankar <sibis@codeaurora.org>
>> 
>> The Q6 modem sub-system has direct access to DDR through memnoc.
>> Also SMMU is not expected to provide access control/translation
>> for these SIDs (sandboxing of the modem is achieved through XPUs
>> engaged using SMC calls). So request direct mapping for modem on
>> platforms which don't have TrustZone.
> 
> The Z7 space rocket framework has limited access to water through 
> BROADCHAN.
> Also, this commit message really sucks. So please can you rewrite it in 
> a
> way that makes sense to people outside of your office?

lol, sure I'll re-word ^^ tday

> 
> Will

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.

WARNING: multiple messages have this Message-ID (diff)
From: Sibi Sankar <sibis@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel-owner@vger.kernel.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	Evan Green <evgreen@chromium.org>,
	linux-arm-msm@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 4/6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Thu, 07 May 2020 19:44:01 +0530	[thread overview]
Message-ID: <f41beaa18f0ba49c3c6f7552291a0641@codeaurora.org> (raw)
In-Reply-To: <20200507130210.GB31783@willie-the-truck>

Hey WIll,

On 2020-05-07 18:32, Will Deacon wrote:
> On Tue, Apr 21, 2020 at 12:03:52AM +0530, Sai Prakash Ranjan wrote:
>> From: Sibi Sankar <sibis@codeaurora.org>
>> 
>> The Q6 modem sub-system has direct access to DDR through memnoc.
>> Also SMMU is not expected to provide access control/translation
>> for these SIDs (sandboxing of the modem is achieved through XPUs
>> engaged using SMC calls). So request direct mapping for modem on
>> platforms which don't have TrustZone.
> 
> The Z7 space rocket framework has limited access to water through 
> BROADCHAN.
> Also, this commit message really sucks. So please can you rewrite it in 
> a
> way that makes sense to people outside of your office?

lol, sure I'll re-word ^^ tday

> 
> Will

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Sibi Sankar <sibis@codeaurora.org>
To: Will Deacon <will@kernel.org>
Cc: linux-kernel-owner@vger.kernel.org,
	Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
	linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
	Jordan Crouse <jcrouse@codeaurora.org>,
	iommu@lists.linux-foundation.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Clark <robdclark@gmail.com>,
	Matthias Kaehlcke <mka@chromium.org>,
	Evan Green <evgreen@chromium.org>,
	linux-arm-msm@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
	Robin Murphy <robin.murphy@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv4 4/6] iommu/arm-smmu-qcom: Request direct mapping for modem device
Date: Thu, 07 May 2020 19:44:01 +0530	[thread overview]
Message-ID: <f41beaa18f0ba49c3c6f7552291a0641@codeaurora.org> (raw)
In-Reply-To: <20200507130210.GB31783@willie-the-truck>

Hey WIll,

On 2020-05-07 18:32, Will Deacon wrote:
> On Tue, Apr 21, 2020 at 12:03:52AM +0530, Sai Prakash Ranjan wrote:
>> From: Sibi Sankar <sibis@codeaurora.org>
>> 
>> The Q6 modem sub-system has direct access to DDR through memnoc.
>> Also SMMU is not expected to provide access control/translation
>> for these SIDs (sandboxing of the modem is achieved through XPUs
>> engaged using SMC calls). So request direct mapping for modem on
>> platforms which don't have TrustZone.
> 
> The Z7 space rocket framework has limited access to water through 
> BROADCHAN.
> Also, this commit message really sucks. So please can you rewrite it in 
> a
> way that makes sense to people outside of your office?

lol, sure I'll re-word ^^ tday

> 
> Will

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-07 14:14 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 18:33 [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select identity mapping Sai Prakash Ranjan
2020-04-20 18:33 ` Sai Prakash Ranjan
2020-04-20 18:33 ` Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 1/6] iommu: arm-smmu-impl: Convert to a generic reset implementation Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 2/6] iommu/arm-smmu: Implement iommu_ops->def_domain_type call-back Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 3/6] iommu/arm-smmu: Allow client devices to select direct mapping Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 4/6] iommu/arm-smmu-qcom: Request direct mapping for modem device Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-05-07 13:02   ` Will Deacon
2020-05-07 13:02     ` Will Deacon
2020-05-07 13:02     ` Will Deacon
2020-05-07 14:14     ` Sibi Sankar [this message]
2020-05-07 14:14       ` Sibi Sankar
2020-05-07 14:14       ` Sibi Sankar
2020-05-07 14:18       ` Will Deacon
2020-05-07 14:18         ` Will Deacon
2020-05-07 14:18         ` Will Deacon
2020-04-20 18:33 ` [PATCHv4 5/6] dt-bindings: remoteproc: qcom: Add iommus property Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33 ` [PATCHv4 6/6] arm64: dts: qcom: sdm845-cheza: " Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-04-20 18:33   ` Sai Prakash Ranjan
2020-05-07 10:28 ` [PATCHv4 0/6] iommu/arm-smmu: Allow client devices to select identity mapping Sai Prakash Ranjan
2020-05-07 10:28   ` Sai Prakash Ranjan
2020-05-07 10:28   ` Sai Prakash Ranjan
2020-05-07 10:31   ` Will Deacon
2020-05-07 10:31     ` Will Deacon
2020-05-07 10:31     ` Will Deacon
2020-05-07 11:08     ` Sai Prakash Ranjan
2020-05-07 11:08       ` Sai Prakash Ranjan
2020-05-07 11:08       ` Sai Prakash Ranjan
2020-05-07 14:04 ` Will Deacon
2020-05-07 14:04   ` Will Deacon
2020-05-07 14:04   ` Will Deacon

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=f41beaa18f0ba49c3c6f7552291a0641@codeaurora.org \
    --to=sibis@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=evgreen@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jcrouse@codeaurora.org \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=saiprakash.ranjan@codeaurora.org \
    --cc=swboyd@chromium.org \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.