mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Courbot <acourbot@nvidia.com>
To: <kusmabite@gmail.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	David Airlie <airlied@linux.ie>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Alexandre Courbot <gnurou@gmail.com>
Subject: Re: [PATCH] drm/tegra: add tiling FB modifiers
Date: Tue, 8 Nov 2016 18:19:01 +0900	[thread overview]
Message-ID: <b7026c2a-c5a0-c896-42fc-04510b9cf2df@nvidia.com> (raw)
In-Reply-To: <CABPQNSYdZiaWrwbkzjc-bGzkbdiOu6FQNMXRtDmxHHGdvzDh6w@mail.gmail.com>

On 11/08/2016 06:07 PM, Erik Faye-Lund wrote:
> On Tue, Nov 8, 2016 at 8:50 AM, Alexandre Courbot <acourbot@nvidia.com> wrote:
>> Add FB modifiers to allow user-space to specify that a surface is in one
>> of the two tiling formats supported by Tegra chips, and add support in
>> the tegradrm driver to handle them properly. This is necessary for the
>> display controller to directly display buffers generated by the GPU.
>>
>> This feature is intended to replace the dedicated IOCTL enabled
>> by TEGRA_STAGING and to provide a non-staging alternative to that
>> solution.
>>
>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>> ---
>>  drivers/gpu/drm/tegra/drm.c   |  2 ++
>>  drivers/gpu/drm/tegra/fb.c    | 23 +++++++++++++++++++---
>>  include/uapi/drm/drm_fourcc.h | 45 +++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 67 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/tegra/drm.c b/drivers/gpu/drm/tegra/drm.c
>> index a9630c2d6cb3..36b4b30a5164 100644
>> --- a/drivers/gpu/drm/tegra/drm.c
>> +++ b/drivers/gpu/drm/tegra/drm.c
>> @@ -161,6 +161,8 @@ static int tegra_drm_load(struct drm_device *drm, unsigned long flags)
>>         drm->mode_config.max_width = 4096;
>>         drm->mode_config.max_height = 4096;
>>
>> +       drm->mode_config.allow_fb_modifiers = true;
>> +
>>         drm->mode_config.funcs = &tegra_drm_mode_funcs;
>>
>>         err = tegra_drm_fb_prepare(drm);
>> diff --git a/drivers/gpu/drm/tegra/fb.c b/drivers/gpu/drm/tegra/fb.c
>> index e6d71fa4028e..2fded58b2ca5 100644
>> --- a/drivers/gpu/drm/tegra/fb.c
>> +++ b/drivers/gpu/drm/tegra/fb.c
>> @@ -52,9 +52,26 @@ int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer,
>>                         struct tegra_bo_tiling *tiling)
>>  {
>>         struct tegra_fb *fb = to_tegra_fb(framebuffer);
>> -
>> -       /* TODO: handle YUV formats? */
>> -       *tiling = fb->planes[0]->tiling;
>> +       uint64_t modifier = fb->base.modifier[0];
>> +
>> +       switch (fourcc_mod_tegra_mod(modifier)) {
>> +       case NV_FORMAT_MOD_TEGRA_TILED:
>> +               tiling->mode = TEGRA_BO_TILING_MODE_TILED;
>> +               tiling->value = 0;
>> +               break;
>> +
>> +       case NV_FORMAT_MOD_TEGRA_16BX2_BLOCK(0):
>> +               tiling->mode = TEGRA_BO_TILING_MODE_BLOCK;
>> +               tiling->value = fourcc_mod_tegra_param(modifier);
>> +               if (tiling->value > 5)
>> +                       return -EINVAL;
> 
> Shouldn't this contain some hardware-check for the support? AFAIK, not
> all Tegras support all block-heights (if even this mode at all?)...

tegra_dc_setup_window does that check later (check the test on
dc->soc->supports_block_linear). At the moment no error message is
displayed though (and it seems like we are writing a stale value in
DC_WIN_BUFFER_ADDR_MODE if the SoC doesn't support block linear and the
tiling mode is TEGRA_BO_TILING_MODE_BLOCK?)

  reply	other threads:[~2016-11-08  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  7:50 Alexandre Courbot
2016-11-08  9:07 ` Erik Faye-Lund
2016-11-08  9:19   ` Alexandre Courbot [this message]
2017-03-20 17:26     ` Thierry Reding
2016-11-08 10:34 ` Daniel Vetter
2017-03-20 17:26 ` Thierry Reding

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=b7026c2a-c5a0-c896-42fc-04510b9cf2df@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gnurou@gmail.com \
    --cc=kusmabite@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    /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

Powered by JetHome