dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [next][PATCH 0/5] radeon HDMI cleaning
Date: Sun, 29 Apr 2012 14:26:00 +0200	[thread overview]
Message-ID: <4F9D3358.8060702@vodafone.de> (raw)
In-Reply-To: <1335648924-3754-1-git-send-email-zajec5@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1758 bytes --]

On 28.04.2012 23:35, Rafał Miłecki wrote:
> That's my patchset making use of gained knowledge and released regs
> names. This is generally just cleaning currect stuff, changing offsets
> to relative ones (so we can use official regs now).
>
> This patch adds temp hack for Evergreen changing offset by 0x3d0. This
> may look a little ugly, but it's safe and will be removed anyway. It's
> here just to don't add regression in Evergreen support.
>
> My plan is to make use of Alex's WIP patch and add new file/code for
> DCE4 (Evergreen). That will allow us to correctly use Evergreen regs
> and drop thet 0x3d0 trick.
>
> Patchset tested on RV620 and HD6320 (so both: R6xx and Evergreen).
>
> Rafał Miłecki (5):
>    drm/radeon/kms: move audio params to separated struct
>    drm/radeon/kms: get rid of hdmi_config_offset
>    drm/radeon/kms: get rid of r600_hdmi_find_free_block
>    drm/radeon/kms: keep HDMI state in separated variable
>    drm/radeon/kms/hdmi: use relative offsets, official regs
>
>   drivers/gpu/drm/radeon/evergreen_reg.h |    2 -
>   drivers/gpu/drm/radeon/r600.c          |   28 +++---
>   drivers/gpu/drm/radeon/r600_audio.c    |   34 ++++----
>   drivers/gpu/drm/radeon/r600_hdmi.c     |  153 +++++++++++++-------------------
>   drivers/gpu/drm/radeon/r600_reg.h      |   41 ---------
>   drivers/gpu/drm/radeon/r600d.h         |    7 +-
>   drivers/gpu/drm/radeon/radeon.h        |   19 ++--
>   drivers/gpu/drm/radeon/radeon_mode.h   |    2 +-
>   8 files changed, 109 insertions(+), 177 deletions(-)
>
Looks good to me and also just tested on my RV710.

So both:

/Tested-by: //Christian König <deathsimple@vodafone.de>/
/Reviewed-by: Christian König <deathsimple@vodafone.de>
///

[-- Attachment #1.2: Type: text/html, Size: 2250 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2012-04-29 12:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-28 21:35 [next][PATCH 0/5] radeon HDMI cleaning Rafał Miłecki
2012-04-28 21:35 ` [next][PATCH 1/5] drm/radeon/kms: move audio params to separated struct Rafał Miłecki
2012-04-28 21:35 ` [next][PATCH 2/5] drm/radeon/kms: get rid of hdmi_config_offset Rafał Miłecki
2012-04-28 21:35 ` [next][PATCH 3/5] drm/radeon/kms: get rid of r600_hdmi_find_free_block Rafał Miłecki
2012-04-28 21:35 ` [next][PATCH 4/5] drm/radeon/kms: keep HDMI state in separated variable Rafał Miłecki
2012-04-28 21:35 ` [next][PATCH 5/5] drm/radeon/kms/hdmi: use relative offsets, official regs Rafał Miłecki
2012-04-29 12:26 ` Christian König [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=4F9D3358.8060702@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zajec5@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