From: Jani Nikula <jani.nikula@linux.intel.com>
To: Animesh Manna <animesh.manna@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org,
Bharath K Veera <bharath.k.veera@intel.com>,
Ananth Krishna R <ananth.krishna.r@intel.com>
Subject: Re: [PATCH 1/5] drm/i915/bxt: Corrected the guid for bxt.
Date: Mon, 28 Nov 2016 13:24:09 +0200 [thread overview]
Message-ID: <87d1hf26g6.fsf@intel.com> (raw)
In-Reply-To: <00cc7cf9-dde0-bc3e-e5a4-da3231d02b59@intel.com>
On Mon, 28 Nov 2016, Animesh Manna <animesh.manna@intel.com> wrote:
> On 11/23/2016 10:02 PM, Chris Wilson wrote:
>> On Wed, Nov 23, 2016 at 09:48:23PM +0530, Animesh Manna wrote:
>>> Guid is changed for bxt platform, so corrected the guid for bxt.
>>>
>>> v1: Initial version as RFC.
>>>
>>> v2: Based on review comment from Jani and David,
>>> have kept guid as binary format.
>>>
>>> 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 | 20 ++++++++++++++++++--
>>> 1 file changed, 18 insertions(+), 2 deletions(-)
>>> mode change 100644 => 100755 drivers/gpu/drm/i915/intel_acpi.c
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_acpi.c b/drivers/gpu/drm/i915/intel_acpi.c
>>> old mode 100644
>>> new mode 100755
>> 3 people handled this patch and none complained about making
>> intel_acpi.c executable? What does happen when you try to execute it?
> oh, will correct it in the next patchset.
>>
>>> index eb638a1..8c878ab
>>> --- a/drivers/gpu/drm/i915/intel_acpi.c
>>> +++ b/drivers/gpu/drm/i915/intel_acpi.c
>>> @@ -15,7 +15,7 @@
>>> acpi_handle dhandle;
>>> } intel_dsm_priv;
>>>
>>> -static const u8 intel_dsm_guid[] = {
>>> +static u8 intel_dsm_guid[] = {
>> Why drop the const?
> intel_dsm_guid is not updated anywhere, it used to assign it to a common
> pointer based on platform check in my current implementation.
> we can explicitly typecast to avoid compilation warning to a normal
> pointer which will be used during dsm probe. Hope it will be fine.
> Please let me know for any concern/suggestion.
Doh, you use 'const u8 *guid', of course. The acpi_check_dsm uuid
parameter is also const u8 *.
BR,
Jani.
>
>>
>>> 0xd3, 0x73, 0xd8, 0x7e,
>>> 0xd0, 0xc2,
>>> 0x4f, 0x4e,
>>> @@ -23,6 +23,14 @@
>>> 0x0f, 0x13, 0x17, 0xb0, 0x1c, 0x2c
>>> };
>>>
>>> +static u8 intel_dsm_guid_bxt[] = {
>> Missing const.
> Explained above.
>>
>>> + 0xc6, 0x41, 0x5b, 0x3e,
>>> + 0x1d, 0xeb,
>>> + 0x60, 0x42,
>>> + 0x9d, 0x15,
>>> + 0xc7, 0x1f, 0xba, 0xda, 0xe4, 0x14
>>> +};
>>> +
>>> static char *intel_dsm_port_name(u8 id)
>>> {
>>> switch (id) {
>>> @@ -113,12 +121,20 @@ static void intel_dsm_platform_mux_info(void)
>>> static bool intel_dsm_pci_probe(struct pci_dev *pdev)
>>> {
>>> acpi_handle dhandle;
>>> + struct drm_device *dev = pci_get_drvdata(pdev);
>>> + struct drm_i915_private *dev_priv = dev->dev_private;
>> dev == dev_priv, just a rose by another name. Use to_i915();
>>
>>> + u8 *guid;
>> Missing const.
> Explained above.
>>
>>>
>>> dhandle = ACPI_HANDLE(&pdev->dev);
>>> if (!dhandle)
>>> return false;
>>>
>>> - if (!acpi_check_dsm(dhandle, intel_dsm_guid, INTEL_DSM_REVISION_ID,
>>> + if (IS_BROXTON(dev_priv))
>>> + guid = intel_dsm_guid_bxt;
>>> + else
>>> + guid = intel_dsm_guid;
>>> +
>>> + if (!acpi_check_dsm(dhandle, guid, INTEL_DSM_REVISION_ID,
>>> 1 << INTEL_DSM_FN_PLATFORM_MUX_INFO)) {
>>> DRM_DEBUG_KMS("no _DSM method for intel device\n");
>>> return false;
>>> --
>>> 1.9.1
>>>
>>> _______________________________________________
>>> Intel-gfx mailing list
>>> Intel-gfx@lists.freedesktop.org
>>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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-11-28 11:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 16:18 [PATCH 0/5] HPD support during suspend for BXT/APL Animesh Manna
2016-11-23 16:18 ` [PATCH 1/5] drm/i915/bxt: Corrected the guid for bxt Animesh Manna
2016-11-23 16:32 ` Chris Wilson
2016-11-28 10:56 ` Animesh Manna
2016-11-28 11:24 ` Jani Nikula [this message]
2016-11-28 16:21 ` Animesh Manna
2016-11-23 16:18 ` [PATCH 2/5] drm/i915/bxt: VBT changes for hpd as wakeup feature Animesh Manna
2016-11-24 14:27 ` Jani Nikula
2016-11-23 16:18 ` [PATCH 3/5] drm/i915/bxt: Added _DSM call to set HPD_CTL Animesh Manna
2016-11-23 18:17 ` Ville Syrjälä
2016-11-28 16:06 ` Animesh Manna
2016-11-28 16:27 ` Ville Syrjälä
2016-11-24 14:22 ` Jani Nikula
2016-11-23 16:18 ` [PATCH 4/5] drm/i915/bxt: Block D3 during suspend Animesh Manna
2016-11-23 16:18 ` [PATCH 5/5] drm/i915: Enable HPD interrupts with master ctl interrupt Animesh Manna
2016-11-23 17:01 ` Imre Deak
2016-11-28 13:39 ` Animesh Manna
2016-11-28 14:41 ` Imre Deak
2016-11-23 17:10 ` Ville Syrjälä
2016-11-28 15:49 ` Animesh Manna
2016-11-28 16:02 ` Ville Syrjälä
2016-11-23 17:46 ` ✗ Fi.CI.BAT: warning for HPD support during suspend for BXT/APL Patchwork
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=87d1hf26g6.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=chris@chris-wilson.co.uk \
--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