From: Konrad Dybcio <konradybcio@gmail.com>
To: Will Deacon <will@kernel.org>
Cc: skrzynka@konradybcio.pl, Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org,
DTML <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
jcrouse@codeaurora.org, john.stultz@linaro.org
Subject: Re: [PATCH 1/1] iommu/arm-smmu: Implement qcom,skip-init
Date: Sat, 4 Jul 2020 15:20:04 +0200 [thread overview]
Message-ID: <CAMS8qEU7owyk0ELmfE7f6Q_C0RT0cy3N=WtP0DzEUhV6KPnDhQ@mail.gmail.com> (raw)
In-Reply-To: <20200704130922.GB21333@willie-the-truck>
> It would probably be better to know _which_ context banks we shouldn't
> touch, no? Otherwise what happens to the others?
> Do we not need to worry about the SMRs as well?
This was mimicked from CAF (think [1]) and the SMMUs don't make the
hypervisor angry anymore, so I wouldn't be too picky on that if it works..
[1] https://github.com/sonyxperiadev/kernel/blob/aosp/LA.UM.7.1.r1/drivers/iommu/arm-smmu.c#L4104-L4109
Regards
Konrad
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Dybcio <konradybcio@gmail.com>
To: Will Deacon <will@kernel.org>
Cc: DTML <devicetree@vger.kernel.org>,
skrzynka@konradybcio.pl,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
john.stultz@linaro.org, Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] iommu/arm-smmu: Implement qcom,skip-init
Date: Sat, 4 Jul 2020 15:20:04 +0200 [thread overview]
Message-ID: <CAMS8qEU7owyk0ELmfE7f6Q_C0RT0cy3N=WtP0DzEUhV6KPnDhQ@mail.gmail.com> (raw)
In-Reply-To: <20200704130922.GB21333@willie-the-truck>
> It would probably be better to know _which_ context banks we shouldn't
> touch, no? Otherwise what happens to the others?
> Do we not need to worry about the SMRs as well?
This was mimicked from CAF (think [1]) and the SMMUs don't make the
hypervisor angry anymore, so I wouldn't be too picky on that if it works..
[1] https://github.com/sonyxperiadev/kernel/blob/aosp/LA.UM.7.1.r1/drivers/iommu/arm-smmu.c#L4104-L4109
Regards
Konrad
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Dybcio <konradybcio@gmail.com>
To: Will Deacon <will@kernel.org>
Cc: DTML <devicetree@vger.kernel.org>,
jcrouse@codeaurora.org, skrzynka@konradybcio.pl,
Joerg Roedel <joro@8bytes.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
john.stultz@linaro.org, Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] iommu/arm-smmu: Implement qcom,skip-init
Date: Sat, 4 Jul 2020 15:20:04 +0200 [thread overview]
Message-ID: <CAMS8qEU7owyk0ELmfE7f6Q_C0RT0cy3N=WtP0DzEUhV6KPnDhQ@mail.gmail.com> (raw)
In-Reply-To: <20200704130922.GB21333@willie-the-truck>
> It would probably be better to know _which_ context banks we shouldn't
> touch, no? Otherwise what happens to the others?
> Do we not need to worry about the SMRs as well?
This was mimicked from CAF (think [1]) and the SMMUs don't make the
hypervisor angry anymore, so I wouldn't be too picky on that if it works..
[1] https://github.com/sonyxperiadev/kernel/blob/aosp/LA.UM.7.1.r1/drivers/iommu/arm-smmu.c#L4104-L4109
Regards
Konrad
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-04 13:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 12:28 [PATCH 1/1] iommu/arm-smmu: Implement qcom,skip-init Konrad Dybcio
2020-07-04 12:28 ` Konrad Dybcio
2020-07-04 12:28 ` Konrad Dybcio
2020-07-04 13:09 ` Will Deacon
2020-07-04 13:09 ` Will Deacon
2020-07-04 13:09 ` Will Deacon
2020-07-04 13:20 ` Konrad Dybcio [this message]
2020-07-04 13:20 ` Konrad Dybcio
2020-07-04 13:20 ` Konrad Dybcio
2020-07-05 3:35 ` Bjorn Andersson
2020-07-05 3:35 ` Bjorn Andersson
2020-07-05 3:35 ` Bjorn Andersson
2020-07-21 15:04 ` Konrad Dybcio
2020-07-21 15:04 ` Konrad Dybcio
2020-07-21 15:04 ` Konrad Dybcio
2020-07-21 15:44 ` Jordan Crouse
2020-07-21 15:44 ` Jordan Crouse
2020-07-21 15:44 ` Jordan Crouse
2020-07-21 16:20 ` Konrad Dybcio
2020-07-21 16:20 ` Konrad Dybcio
2020-07-21 16:20 ` Konrad Dybcio
2020-07-21 23:56 ` Bjorn Andersson
2020-07-21 23:56 ` Bjorn Andersson
2020-07-21 23:56 ` Bjorn Andersson
2020-07-22 20:11 ` Konrad Dybcio
2020-07-22 20:11 ` Konrad Dybcio
2020-07-22 20:11 ` Konrad Dybcio
2020-07-31 5:48 ` Bjorn Andersson
2020-07-31 5:48 ` Bjorn Andersson
2020-07-31 5:48 ` Bjorn Andersson
2020-08-03 23:57 ` Konrad Dybcio
2020-08-03 23:57 ` Konrad Dybcio
2020-08-03 23:57 ` Konrad Dybcio
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='CAMS8qEU7owyk0ELmfE7f6Q_C0RT0cy3N=WtP0DzEUhV6KPnDhQ@mail.gmail.com' \
--to=konradybcio@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=john.stultz@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=skrzynka@konradybcio.pl \
--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.