public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Ben Dai <ben.dai9703@gmail.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/gic-v3: Allow 'dma-noncoherent' property for ITS
Date: Sun, 12 Feb 2023 11:48:13 +0000	[thread overview]
Message-ID: <87mt5jksua.wl-maz@kernel.org> (raw)
In-Reply-To: <20230212093505.5754-1-ben.dai9703@gmail.com>

On Sun, 12 Feb 2023 09:35:05 +0000,
Ben Dai <ben.dai9703@gmail.com> wrote:
> 
> Currently the ITS driver expects the hardware to report whether it is
> shareable, but according to the description of the GITS_CBASER register
> in the GICv3 architecture specification:
>  > It is IMPLEMENTATION DEFINED whether this field has a fixed value or
>  > can be programmed by software. Implementing this field with a fixed
>  > value is deprecated.
> 
> It means that the hardware may expect the software to correctly configure
> the access attributes of the ITS. In order to support those designs where
> ITS and CPU are not in a coherent domain, allow 'dma-noncoherent' property
> for ITS.

No. This is an integration bug, most likely a Rockchip quality
design. I have repeatedly explained how to deal with this, and I'm not
going to do that again. Please search the list archives.

I will not be taking this sort of patch.

	M.

-- 
Without deviation from the norm, progress is not possible.

      reply	other threads:[~2023-02-12 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12  9:35 [PATCH] irqchip/gic-v3: Allow 'dma-noncoherent' property for ITS Ben Dai
2023-02-12 11:48 ` Marc Zyngier [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=87mt5jksua.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=ben.dai9703@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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