From: Jani Nikula <jani.nikula@intel.com>
To: imre.deak@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH RESEND 2/2] drm/i915: don't register invalid gmbus pins for skl
Date: Tue, 12 May 2015 15:24:49 +0300 [thread overview]
Message-ID: <874mni3rvy.fsf@intel.com> (raw)
In-Reply-To: <1431431532.2729.1.camel@intel.com>
On Tue, 12 May 2015, Imre Deak <imre.deak@intel.com> wrote:
> On ke, 2015-05-06 at 15:33 +0300, Jani Nikula wrote:
>> Do no expose invalid gmbus pins as i2c devices to userspace.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Looks ok, on both 1/2 and 2/2:
> Reviewed-by: Imre Deak <imre.deak@intel.com>
Daniel, please fix 's/Do no/Do not/' in commit messages while applying.
Thanks,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/intel_i2c.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_i2c.c b/drivers/gpu/drm/i915/intel_i2c.c
>> index 76070c4e76b3..92072f56e418 100644
>> --- a/drivers/gpu/drm/i915/intel_i2c.c
>> +++ b/drivers/gpu/drm/i915/intel_i2c.c
>> @@ -56,6 +56,12 @@ static const struct gmbus_pin gmbus_pins_bdw[] = {
>> [GMBUS_PIN_DPD] = { "dpd", GPIOF },
>> };
>>
>> +static const struct gmbus_pin gmbus_pins_skl[] = {
>> + [GMBUS_PIN_DPC] = { "dpc", GPIOD },
>> + [GMBUS_PIN_DPB] = { "dpb", GPIOE },
>> + [GMBUS_PIN_DPD] = { "dpd", GPIOF },
>> +};
>> +
>> static const struct gmbus_pin gmbus_pins_bxt[] = {
>> [GMBUS_PIN_1_BXT] = { "dpb", PCH_GPIOB },
>> [GMBUS_PIN_2_BXT] = { "dpc", PCH_GPIOC },
>> @@ -68,6 +74,8 @@ static const struct gmbus_pin *get_gmbus_pin(struct drm_i915_private *dev_priv,
>> {
>> if (IS_BROXTON(dev_priv))
>> return &gmbus_pins_bxt[pin];
>> + else if (IS_SKYLAKE(dev_priv))
>> + return &gmbus_pins_skl[pin];
>> else if (IS_BROADWELL(dev_priv))
>> return &gmbus_pins_bdw[pin];
>> else
>> @@ -81,6 +89,8 @@ bool intel_gmbus_is_valid_pin(struct drm_i915_private *dev_priv,
>>
>> if (IS_BROXTON(dev_priv))
>> size = ARRAY_SIZE(gmbus_pins_bxt);
>> + else if (IS_SKYLAKE(dev_priv))
>> + size = ARRAY_SIZE(gmbus_pins_skl);
>> else if (IS_BROADWELL(dev_priv))
>> size = ARRAY_SIZE(gmbus_pins_bdw);
>> else
>
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-05-12 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 12:33 [PATCH RESEND 1/2] drm/i915: don't register invalid gmbus pins for bdw Jani Nikula
2015-05-06 12:33 ` [PATCH RESEND 2/2] drm/i915: don't register invalid gmbus pins for skl Jani Nikula
2015-05-11 10:42 ` David Weinehall
2015-05-11 11:13 ` Jani Nikula
2015-05-12 11:52 ` Imre Deak
2015-05-12 12:24 ` Jani Nikula [this message]
2015-05-12 13:09 ` Daniel Vetter
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=874mni3rvy.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=imre.deak@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