linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	airlied@gmail.com, dri-devel@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>,
	Zhang Rui <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH] drm/radeon: add new AMD ACPI header and update relevant code
Date: Fri, 27 Jul 2012 12:46:50 +0800	[thread overview]
Message-ID: <1343364410.8142.42.camel@linux-s257.site> (raw)
In-Reply-To: <CADnq5_Mz5cjyYZ=1gjq+iaGtizhckKBL23gLaNJQFAPXHGF4TQ@mail.gmail.com>

於 四,2012-07-26 於 23:31 -0400,Alex Deucher 提到:
> On Thu, Jul 26, 2012 at 10:50 PM, joeyli <jlee@suse.com> wrote:
> > 於 四,2012-07-26 於 14:58 +0200,Luca Tettamanti 提到:
> >> - again ACPI video module gets the nodification (in this case
> >>   ACPI_VIDEO_NOTIFY_PROBE), re-enumerated and send KEY_SWITCHVIDEOMODE
> >> - KDE seems this and muck with the screen configuration :(
> >> - meanwhile the brightness notification is propagated, the
> >> hypothetical
> >>   radeon driver does its magic to adjust the screen.
> >>
> >> My first idea would be to make ACPI_VIDEO_NOTIFY_PROBE also call to
> >> the
> >> acpi notifier chain, and allow the handlers to veto the key press
> >> (like
> >> it's done for ACPI_VIDEO_NOTIFY_SWITCH).
> >
> > I welcome this approach!
> >
> > On some ATI machine's DSDT also issue ACPI_VIDEO_NOTIFY_PROBE when
> > AC-power unplug, because BIOS want to nodify video driver do some power
> > saving stuff.
> > It causes KEY_SWITCHVIDEOMODE issued by acpi/video driver when AC-power
> > unplug.
> >
> > At least acpi/video driver need to know this 0x81 event is filed by BIOS
> > to radeon-acpi for notify but not do video mode switch. That means the
> > radeon drm need take the video switch responsibility.
> 
> Probably we'd just want the radeon acpi handler to just forward the
> events to userspace so that the user can choose what to do with it
> (xrandr command, etc.), otherwise we'll need to define policy in the
> driver.
> 
> Alex
> 

Any kernel module can issue KEY_SWITCHVIDEOMODE to user space, then
gnome-settings-daemon(on Gnome) and  krandr(on KDE) will call xrandr
library to switch video mode.


The 0x81 ACPI event for acpi/video driver is ACPI_VIDEO_NOTIFY_PROBE,
means need issue KEY_SWITCHVIDEOMODE. But, 0x81 for radeon is a general
notification event.
I didn't see probe state in GET_SYSTEM_BIOS_REQUESTS, how can we
distinguish this 0x81 is a ACPI_VIDEO_NOTIFY_PROBE or a ATI general
notification event?

+ * flags
+ * bits 1:0:
+ * 0 - Notify(VGA, 0x81) is not used for notification
+ * 1 - Notify(VGA, 0x81) is used for notification

Per the above flags, when we detect bit set to 1, means 0x81 used for radeon-acpi
to be a general notification event. My question is: what's the event number for
ACPI_VIDEO_NOTIFY_PROBE on this AMD/ATI machine when 0x81 not available for acpi/video?


Thanks a lot!
Joey Lee

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-07-27  4:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1343237889-5220-1-git-send-email-alexdeucher@gmail.com>
2012-07-26 12:58 ` [PATCH] drm/radeon: add new AMD ACPI header and update relevant code Luca Tettamanti
2012-07-26 15:35   ` Alex Deucher
2012-07-26 19:33     ` Luca Tettamanti
2012-07-26 19:42       ` Alex Deucher
2012-07-26 19:58         ` Alex Deucher
2012-07-28 14:39     ` Pali Rohár
2012-07-27  2:50   ` joeyli
2012-07-27  3:31     ` Alex Deucher
2012-07-27  4:46       ` joeyli [this message]
2012-07-27  9:02         ` Luca Tettamanti
2012-07-27 13:21         ` Alex Deucher
2012-07-27 15:32           ` joeyli
2012-07-27 15:36             ` joeyli
2012-07-27 16:31             ` Alex Deucher

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=1343364410.8142.42.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kronos.it@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).