From: Stephen Boyd <firstname.lastname@example.org> To: Vivek Gautam <email@example.com> Cc: Bjorn Andersson <firstname.lastname@example.org>, Andy Gross <email@example.com>, open list <firstname.lastname@example.org>, linux-arm-msm <email@example.com>, Sibi Sankar <firstname.lastname@example.org> Subject: Re: [PATCH] arm64: dts: sdm845: Add iommus property to qup1 Date: Wed, 05 Jun 2019 13:56:14 -0700 Message-ID: <email@example.com> (raw) In-Reply-To: <CAFp+6iHZeawnz7Vfk3=Oox-GN_y6c-E9wMwc-qdp1bTOXgqjFQ@mail.gmail.com> Quoting Vivek Gautam (2019-06-04 21:55:26) > On Wed, Jun 5, 2019 at 4:16 AM Stephen Boyd <firstname.lastname@example.org> wrote: > > > > Quoting Bjorn Andersson (2019-06-04 15:37:00) > > > On Tue 04 Jun 15:29 PDT 2019, Stephen Boyd wrote: > > > > > > > The SMMU that sits in front of the QUP needs to be programmed properly > > > > so that the i2c geni driver can allocate DMA descriptors. Failure to do > > > > this leads to faults when using devices such as an i2c touchscreen where > > > > the transaction is larger than 32 bytes and we use a DMA buffer. > > > > > > > > > > I'm pretty sure I've run into this problem, but before we marked the > > > smmu bypass_disable and as such didn't get the fault, thanks. > > > > > > > arm-smmu 15000000.iommu: Unexpected global fault, this could be serious > > > > arm-smmu 15000000.iommu: GFSR 0x00000002, GFSYNR0 0x00000002, GFSYNR1 0x000006c0, GFSYNR2 0x00000000 > > > > > > > > Add the right SID and mask so this works. > > > > > > > > Cc: Sibi Sankar <email@example.com> > > > > Signed-off-by: Stephen Boyd <firstname.lastname@example.org> > > > > --- > > > > arch/arm64/boot/dts/qcom/sdm845.dtsi | 1 + > > > > 1 file changed, 1 insertion(+) > > > > > > > > diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi > > > > index fcb93300ca62..2e57e861e17c 100644 > > > > --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi > > > > +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi > > > > @@ -900,6 +900,7 @@ > > > > #address-cells = <2>; > > > > #size-cells = <2>; > > > > ranges; > > > > + iommus = <&apps_smmu 0x6c0 0x3>; > > > > > > According to the docs this stream belongs to TZ, the HLOS stream should > > > be 0x6c3. > > > > Aye, I saw this line in the downstream kernel but it doesn't work for > > me. If I specify <&apps_smmu 0x6c3 0x0> it still blows up. I wonder if > > my firmware perhaps is missing some initialization here to make the QUP > > operate in HLOS mode? Otherwise, I thought that the 0x3 at the end was > > the mask and so it should be split off to the second cell in the DT > > specifier but that seemed a little weird. > > Two things here - > 0x6c0 - TZ SID. Do you see above fault on MTP sdm845 devices? No. I see the above fault on Cheza. > 0x6c3/0x6c6 - HLOS SIDs. Why are there two? I see some mentions of GSI mode near these SIDs so maybe GSI has to be used for DMA here to get the above two SIDs at the IOMMU? Otherwise if we do the non-GSI mode of DMA we're going to use the "TZ" SID? > > Cheza will throw faults for anything that is programmed with TZ on mtp > as all of that should be handled in HLOS. The firmwares of all these > peripherals assume that the SID reservation is done (whether in TZ or HLOS). > > I am inclined to moving the iommus property for all 'TZ' to board dts files. > MTP wouldn't need those SIDs. So, the SOC level dtsi will have just the > HLOS SIDs. So you're saying you'd like to have the SID be <&apps_smmu 0x6c3 0x0> in the sdm845.dtsi file and then override this on Cheza because our SID is different (possibly because we don't use GSI)? Why can't we program the SID in Cheza firmware to match the "HLOS" SID of 0x6c3? > > P.S. > As you rightly said, the second cell in iommus property is the mask so that > the iommu is able to reserve all that SIDs that are covered with the > starting SID > and the mask. > Well if 0x6c6 is another possibility maybe it should be <&apps_smmu 0x6c0 0x7> to cover the 0x6c3 and 0x6c6 SIDs?
next prev parent reply index Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-04 22:29 Stephen Boyd 2019-06-04 22:37 ` Bjorn Andersson 2019-06-04 22:46 ` Stephen Boyd 2019-06-04 22:59 ` Bjorn Andersson 2019-06-05 4:55 ` Vivek Gautam 2019-06-05 20:56 ` Stephen Boyd [this message] 2019-06-06 11:17 ` Vivek Gautam 2019-06-06 14:12 ` Marc Gonzalez 2019-06-10 23:21 ` Stephen Boyd 2019-06-12 9:26 ` Vivek Gautam 2019-07-16 23:47 ` Stephen Boyd 2019-06-04 22:48 ` Doug Anderson 2019-06-04 22:56 ` Bjorn Andersson
Reply instructions: You may reply publically 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
LKML Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \ email@example.com firstname.lastname@example.org public-inbox-index lkml Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel AGPL code for this site: git clone https://public-inbox.org/ public-inbox