devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Nicolin Chen <nicolinc@nvidia.com>,
	Krishna Reddy <vdumpa@nvidia.com>,
	devicetree@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 0/5] iommu: Support identity mappings of reserved-memory regions
Date: Wed, 28 Apr 2021 08:59:11 +0300	[thread overview]
Message-ID: <8032d476-8104-1218-30c6-9fd670c3e7b5@gmail.com> (raw)
In-Reply-To: <20210423163234.3651547-1-thierry.reding@gmail.com>

23.04.2021 19:32, Thierry Reding пишет:
> Note that an earlier proposal was to use the existing simple-framebuffer
> device tree bindings to transport this information. Unfortunately there
> are cases where this is not enough. On Tegra SoCs, for example, the
> bootloader will also set up a color space correction lookup table in the
> system memory that the display controller will access during boot,
> alongside the framebuffer. The simple-framebuffer DT bindings have no
> way of describing this (and I guess one could argue that this particular
> setup no longer is a "simple" framebuffer), so the above, more flexible
> proposal was implemented.

Will simple-framebuffer be able to use that reserved region
transparently? Or will it require a custom simple-framebuffer driver?

Could we make simple-framebuffer support a part of this series?

  parent reply	other threads:[~2021-04-28  5:59 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 16:32 [PATCH v2 0/5] iommu: Support identity mappings of reserved-memory regions Thierry Reding
2021-04-23 16:32 ` [PATCH v2 1/5] dt-bindings: reserved-memory: Document memory region specifier Thierry Reding
2021-05-20 22:03   ` Rob Herring
2021-05-28 16:54     ` Thierry Reding
2021-06-08 16:51       ` Thierry Reding
2021-07-01 18:14         ` Thierry Reding
2021-07-02 14:16           ` Dmitry Osipenko
2021-09-01 14:13             ` Thierry Reding
2021-09-03 13:20               ` Rob Herring
2021-09-03 13:52                 ` Thierry Reding
2021-09-03 14:36                   ` Rob Herring
2021-09-03 15:35                     ` Thierry Reding
2021-09-07 15:33                       ` Rob Herring
2021-09-07 17:44                         ` Thierry Reding
2021-09-15 15:19                           ` Thierry Reding
2022-02-06 22:27                             ` Janne Grunau
2022-02-09 16:31                               ` Thierry Reding
2022-02-10 23:15                                 ` Janne Grunau
2022-03-31 16:25                                   ` Thierry Reding
2022-04-01 17:08                                     ` Janne Grunau
2021-04-23 16:32 ` [PATCH v2 2/5] iommu: Implement of_iommu_get_resv_regions() Thierry Reding
2021-07-02 14:05   ` Dmitry Osipenko
2021-07-16 14:41     ` Rob Herring
2021-07-17 11:07       ` Dmitry Osipenko
2021-07-30 12:18         ` Will Deacon
2021-04-23 16:32 ` [PATCH v2 3/5] iommu: dma: Use of_iommu_get_resv_regions() Thierry Reding
2021-04-23 16:32 ` [PATCH v2 4/5] iommu/tegra-smmu: Add support for reserved regions Thierry Reding
2021-04-23 16:32 ` [PATCH v2 5/5] iommu/tegra-smmu: Support managed domains Thierry Reding
2021-10-11 23:25   ` Dmitry Osipenko
2021-04-24  7:26 ` [PATCH v2 0/5] iommu: Support identity mappings of reserved-memory regions Dmitry Osipenko
2021-04-27 18:30   ` Krishna Reddy
2021-04-28  5:44     ` Dmitry Osipenko
2021-04-29  5:51       ` Krishna Reddy
2021-04-29 12:43         ` Dmitry Osipenko
2021-04-28  5:51 ` Dmitry Osipenko
2021-04-28  5:57   ` Mikko Perttunen
2021-04-28  7:55     ` Dmitry Osipenko
2021-04-28  5:59 ` Dmitry Osipenko [this message]
2021-10-03  1:09 ` Dmitry Osipenko
2021-10-04 19:23   ` Thierry Reding
2021-10-04 20:32     ` Dmitry Osipenko

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=8032d476-8104-1218-30c6-9fd670c3e7b5@gmail.com \
    --to=digetx@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=thierry.reding@gmail.com \
    --cc=vdumpa@nvidia.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).