From mboxrd@z Thu Jan 1 00:00:00 1970 From: joeyli Subject: Re: [PATCH] drm/radeon: add new AMD ACPI header and update relevant code Date: Fri, 27 Jul 2012 23:32:07 +0800 Message-ID: <1343403127.1788.26.camel@linux-s257.site> References: <1343237889-5220-1-git-send-email-alexdeucher@gmail.com> <20120726125838.GA28853@growl> <1343357441.8142.18.camel@linux-s257.site> <1343364410.8142.42.camel@linux-s257.site> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from smtp.nue.novell.com ([195.135.221.5]:42817 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751029Ab2G0Peo (ORCPT ); Fri, 27 Jul 2012 11:34:44 -0400 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Alex Deucher Cc: Luca Tettamanti , airlied@gmail.com, dri-devel@lists.freedesktop.org, Alex Deucher , Zhang Rui , linux-acpi@vger.kernel.org =E6=96=BC =E4=BA=94=EF=BC=8C2012-07-27 =E6=96=BC 09:21 -0400=EF=BC=8CAl= ex Deucher =E6=8F=90=E5=88=B0=EF=BC=9A > On Fri, Jul 27, 2012 at 12:46 AM, joeyli wrote: > > > > + * 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 f= or radeon-acpi > > to be a general notification event. My question is: what's the even= t number for > > ACPI_VIDEO_NOTIFY_PROBE on this AMD/ATI machine when 0x81 not avail= able for acpi/video? > > >=20 >=20 > +/* ARG0: ATIF_FUNCTION_GET_SYSTEM_PARAMETERS > + * ARG1: none > + * OUTPUT: > + * WORD - structure size in bytes (includes size field) > + * DWORD - valid flags mask > + * DWORD - flags > + * > + * OR > + * > + * WORD - structure size in bytes (includes size field) > + * DWORD - valid flags mask > + * DWORD - flags > + * BYTE - notify command code > + * > + * flags > + * bits 1:0: > + * 0 - Notify(VGA, 0x81) is not used for notification > + * 1 - Notify(VGA, 0x81) is used for notification > + * 2 - Notify(VGA, n) is used for notification where > + * n (0xd0-0xd9) is specified in notify command code. > + * bit 2: > + * 1 - lid changes not reported though int10 > + */ >=20 > if bits 1:0 =3D=3D 0, there is no notify event for radeon. When bits= 1:0 > =3D=3D 1, it uses 0x81; when bits 1:0 =3D=3D 2 it uses the event numb= er > specified in the following byte (notify command code) which would be > something in the 0xd0-0xd9 range. >=20 > Alex Did you mean every time we received 0x81 event in kernel module, we nee= d access GET_SYSTEM_PARAMETERS to get the flags for distinguish between ACPI_VIDEO_NOTIFY_PROBE? Or just need access ONE time when system boot? I have a machine the GET_SYSTEM_PARAMETERS looks like this: Method (AF01, 0, NotSerialized) /* ATIF_FUNCTION_GET_SY= STEM_PARAMETERS 0x1 */ { CreateWordField (ATIB, Zero, SSZE) CreateDWordField (ATIB, 0x02, VMSK) CreateDWordField (ATIB, 0x06, FLGS) /* flags bits 1:0 */ Store (0x0A, SSZE) /* structure SIZE fixed */ Store (0x03, VMSK) /* valid flags mask fixed to 0x03 */ Store (One, FLGS) /* FLAGS always set to 1 */ Return (ATIB) } Looks like just need access ONE time when system boot because those return value of AF01 fixed in DSDT. On this machine doesn't support probe event, I didn't see any event issued when I plug D-Sub. Does that means those kind of ATI/AMD machine= s do NOT support probe notify? If YES, then we can just direct disable acpi/video driver by radeon-acp= i when we detected FLAGS is 1. Thanks a lot! Joey Lee -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html