linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: Rob Clark <robdclark@gmail.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Joerg Roedel <joro@8bytes.org>,
	iommu@lists.linux.dev, linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu-qcom: Add X1E80100 MDSS compatible
Date: Wed, 21 Feb 2024 13:10:29 +0200	[thread overview]
Message-ID: <ZdXaJQ5AfOiki1l5@linaro.org> (raw)
In-Reply-To: <20240213131952.GB28926@willie-the-truck>

On 24-02-13 13:19:52, Will Deacon wrote:
> On Wed, Jan 31, 2024 at 02:35:16PM +0200, Abel Vesa wrote:
> > Add the X1E80100 MDSS compatible to clients compatible list, as it also
> > needs the workarounds.
> > 
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > ---
> >  drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > index 8b04ece00420..5c7cfc51b57c 100644
> > --- a/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > +++ b/drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c
> > @@ -260,6 +260,7 @@ static const struct of_device_id qcom_smmu_client_of_match[] __maybe_unused = {
> >  	{ .compatible = "qcom,sm6375-mdss" },
> >  	{ .compatible = "qcom,sm8150-mdss" },
> >  	{ .compatible = "qcom,sm8250-mdss" },
> > +	{ .compatible = "qcom,x1e80100-mdss" },
> 
> I think this needs adding to the bindings Documentation first.

It is documented here (once it gets merged):
https://lore.kernel.org/all/20240220-x1e80100-display-v4-2-971afd9de861@linaro.org/

> 
> Will

  reply	other threads:[~2024-02-21 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 12:35 [PATCH] iommu/arm-smmu-qcom: Add X1E80100 MDSS compatible Abel Vesa
2024-02-13 13:19 ` Will Deacon
2024-02-21 11:10   ` Abel Vesa [this message]
2024-02-22 18:06 ` 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=ZdXaJQ5AfOiki1l5@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).