mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Neil Armstrong <neil.armstrong@linaro.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Petr Hodina <petr.hodina@protonmail.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH] needsreview! arm64: dts: qcom: sdm845: Add missing MDSS reset
Date: Tue, 13 Jan 2026 13:30:59 +0100	[thread overview]
Message-ID: <d2cd85cd-2df9-4738-a575-03b86f792067@ixit.cz> (raw)
In-Reply-To: <bfe55d1b-1b45-4187-84fe-9475cb90b00a@linaro.org>

On 13/01/2026 10:48, Neil Armstrong wrote:
> On 1/12/26 13:33, David Heidelberg via B4 Relay wrote:
>> From: David Heidelberg <david@ixit.cz>
>>
>> If the OS does not support recovering the state left by the
>> bootloader it needs a way to reset display hardware, so that it can
>> start from a clean state. Add a reference to the relevant reset.
>>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>> It efficiently fixes nothing for us (at least what we're aware), so I
>> assume the state left by bootloader is good enough
> 
> In fact it does even more, perhaps in your usecase you're not affected but
> it permits resetting the MDSS while switching the IOMMU from bypass to 
> translated.
> 
> In the current IOMMU implementation, there's no current way to keep the 
> IOMMU setup
> for an SID without a cut, leading to fatal IOMMU errors.
> 
> With the hypervisor enabled, some IOMMU entries are left to fallback in 
> bypass
> when switching, but in EL2 there's no fallback and the ARM SMMUv2 
> doesn't support
> mapping _before_ attaching to a device leading to:
> https://elixir.bootlin.com/linux/v6.18.4/source/drivers/iommu/iommu.c#L3046
>      /*
>       * Drivers are supposed to allow mappings to be installed in a domain
>       * before device attachment, but some don't. Hack around this 
> defect by
>       * trying again after attaching. If this happens it means the device
>       * will not continuously have the IOMMU_RESV_DIRECT map.
>       */
> 
> Sorry for the digression!
> 
> Neil
> 

Thank you, that's good to know! :)

David

[...]

      reply	other threads:[~2026-01-13 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 12:33 David Heidelberg via B4 Relay
2026-01-12 12:36 ` David Heidelberg
2026-01-13  9:27 ` Konrad Dybcio
2026-01-13  9:48 ` Neil Armstrong
2026-01-13 12:30   ` David Heidelberg [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=d2cd85cd-2df9-4738-a575-03b86f792067@ixit.cz \
    --to=david@ixit.cz \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=petr.hodina@protonmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®