From: Jani Nikula <jani.nikula@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Bharath K Veera <bharath.k.veera@intel.com>,
Ananth Krishna R <ananth.krishna.r@intel.com>
Subject: Re: [PATCH v2 3/5] drm/i915/bxt: Corrected the guid for bxt.
Date: Fri, 08 Apr 2016 12:00:22 +0300 [thread overview]
Message-ID: <87wpo8v5jt.fsf@intel.com> (raw)
In-Reply-To: <1460040732-31417-4-git-send-email-animesh.manna@intel.com>
On Thu, 07 Apr 2016, Animesh Manna <animesh.manna@intel.com> wrote:
> Guid is changed for bxt platform, so corrected the guid for bxt.
>
> Signed-off-by: Ananth Krishna R <ananth.krishna.r@intel.com>
> Signed-off-by: Bharath K Veera <bharath.k.veera@intel.com>
> Signed-off-by: Animesh Manna <animesh.manna@intel.com>
> ---
> drivers/gpu/drm/i915/intel_acpi.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_acpi.c b/drivers/gpu/drm/i915/intel_acpi.c
> index 8f3d672..8ba30b3 100644
> --- a/drivers/gpu/drm/i915/intel_acpi.c
> +++ b/drivers/gpu/drm/i915/intel_acpi.c
> @@ -17,7 +17,7 @@ static struct intel_dsm_priv {
> acpi_handle dhandle;
> } intel_dsm_priv;
>
> -static const u8 intel_dsm_guid[] = {
> +static u8 intel_dsm_guid[] = {
> 0xd3, 0x73, 0xd8, 0x7e,
> 0xd0, 0xc2,
> 0x4f, 0x4e,
> @@ -25,6 +25,9 @@ static const u8 intel_dsm_guid[] = {
> 0x0f, 0x13, 0x17, 0xb0, 0x1c, 0x2c
> };
>
> +static u8 intel_bxt_dsm_guid[] =
> + "3E5B41C6-EB1D-4260-9D15-C71FBADAE414";
> +
So I want both of these to be either in string form or in binary uuid
form, not a mixture. Having them in binary makes the code simpler, so
I'd go for that.
BR,
Jani.
> static char *intel_dsm_port_name(u8 id)
> {
> switch (id) {
> @@ -143,6 +146,9 @@ static bool intel_dsm_pci_probe(struct pci_dev *pdev)
>
> intel_dsm_priv.dhandle = dhandle;
>
> + if (IS_BROXTON(dev))
> + acpi_str_to_uuid(intel_bxt_dsm_guid, intel_dsm_guid);
> +
> if (acpi_check_dsm(dhandle, intel_dsm_guid, INTEL_DSM_REVISION_ID,
> 1 << INTEL_DSM_FN_PLATFORM_MUX_INFO))
> intel_dsm_platform_mux_info();
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-08 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 14:52 [PATCH v2 0/6] HPD support during suspend Animesh Manna
2016-04-07 14:52 ` [PATCH v2 1/5] drm/i915/bxt: VBT changes for hpd as wakeup feature Animesh Manna
2016-04-07 14:52 ` [PATCH v2 2/5] drm/i915/bxt: Added _DSM call to set HPD_CTL Animesh Manna
2016-04-07 14:52 ` [PATCH v2 3/5] drm/i915/bxt: Corrected the guid for bxt Animesh Manna
2016-04-08 9:00 ` Jani Nikula [this message]
2016-04-08 12:55 ` David Weinehall
2016-04-13 12:45 ` Animesh Manna
2016-04-07 14:52 ` [PATCH v2 4/5] drm/i915/bxt: Block D3 during suspend Animesh Manna
2016-04-08 11:46 ` David Weinehall
2016-04-07 14:52 ` [PATCH v2 5/5] drm/i915: Enable HPD interrupts with master ctl interrupt Animesh Manna
2016-04-07 16:59 ` ✗ Fi.CI.BAT: failure for HPD support during suspend. (rev2) Patchwork
2016-04-07 21:05 ` [PATCH v2 0/6] HPD support during suspend Imre Deak
2016-04-13 13:47 ` Animesh Manna
2016-04-13 14:00 ` Animesh Manna
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=87wpo8v5jt.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ananth.krishna.r@intel.com \
--cc=animesh.manna@intel.com \
--cc=bharath.k.veera@intel.com \
--cc=intel-gfx@lists.freedesktop.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).