All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
Cc: andy.shevchenko@gmail.com, gabriel@tekgnowsys.com,
	gabriele.mzt@gmail.com, dvhart@infradead.org, andy@infradead.org,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mario.Limonciello@dell.com
Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
Date: Mon, 2 Oct 2017 15:15:40 +0200	[thread overview]
Message-ID: <20171002131540.GE10938@pali> (raw)
In-Reply-To: <85b11afa464948a1abcede55b7f66a25@ausx13mpc120.AMER.DELL.COM>

On Monday 02 October 2017 13:06:46 Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: Pali Rohár [mailto:pali.rohar@gmail.com]
> > Sent: Monday, October 2, 2017 6:53 AM
> > To: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Cc: Gabriel M. Elder <gabriel@tekgnowsys.com>; Gabriele Mazzotta
> > <gabriele.mzt@gmail.com>; Limonciello, Mario <Mario_Limonciello@Dell.com>;
> > Darren Hart <dvhart@infradead.org>; Andy Shevchenko <andy@infradead.org>;
> > platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
> > 
> > On Friday 29 September 2017 18:19:59 Andy Shevchenko wrote:
> > > >> FYI, latest update and info relating to
> > > >> https://bugzilla.kernel.org/show_bug.cgi?id=196913
> > >
> > > Quick solution is to apply DMI to that.
> > 
> > It is only the Dell Latitude E6410 affected?
> > 
> > Mario, do you have any information about that API from Dell?
> > 
> > --
> > Pali Rohár
> > pali.rohar@gmail.com
> 
> Pali,
> 
> I believe this particular API shouldn't have changed over generations, so it's 
> likely something that needs to be quirked for that generation.  
> I haven't had a chance to check on this yet in detail though.
> For now could you guys quirk this one and if I find out there was something
> more systemic we can undo the quirk and do something more broad.
> 
> Thanks,

Ok! Gabriel, can you provide us your DMI information about your machine?

They are included in following files:
/sys/class/dmi/id/sys_vendor
/sys/class/dmi/id/product_name

Beware that they may contain whitespace characters and it is important.

-- 
Pali Rohár
pali.rohar@gmail.com

WARNING: multiple messages have this Message-ID (diff)
From: "Pali Rohár" <pali.rohar@gmail.com>
To: gabriel@tekgnowsys.com
Cc: andy.shevchenko@gmail.com, gabriel@tekgnowsys.com,
	gabriele.mzt@gmail.com, dvhart@infradead.org, andy@infradead.org,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mario.Limonciello@dell.com
Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
Date: Mon, 2 Oct 2017 15:15:40 +0200	[thread overview]
Message-ID: <20171002131540.GE10938@pali> (raw)
In-Reply-To: <85b11afa464948a1abcede55b7f66a25@ausx13mpc120.AMER.DELL.COM>

On Monday 02 October 2017 13:06:46 Mario.Limonciello@dell.com wrote:
> > -----Original Message-----
> > From: Pali Rohár [mailto:pali.rohar@gmail.com]
> > Sent: Monday, October 2, 2017 6:53 AM
> > To: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Cc: Gabriel M. Elder <gabriel@tekgnowsys.com>; Gabriele Mazzotta
> > <gabriele.mzt@gmail.com>; Limonciello, Mario <Mario_Limonciello@Dell.com>;
> > Darren Hart <dvhart@infradead.org>; Andy Shevchenko <andy@infradead.org>;
> > platform-driver-x86@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
> > 
> > On Friday 29 September 2017 18:19:59 Andy Shevchenko wrote:
> > > >> FYI, latest update and info relating to
> > > >> https://bugzilla.kernel.org/show_bug.cgi?id=196913
> > >
> > > Quick solution is to apply DMI to that.
> > 
> > It is only the Dell Latitude E6410 affected?
> > 
> > Mario, do you have any information about that API from Dell?
> > 
> > --
> > Pali Rohár
> > pali.rohar@gmail.com
> 
> Pali,
> 
> I believe this particular API shouldn't have changed over generations, so it's 
> likely something that needs to be quirked for that generation.  
> I haven't had a chance to check on this yet in detail though.
> For now could you guys quirk this one and if I find out there was something
> more systemic we can undo the quirk and do something more broad.
> 
> Thanks,

Ok! Gabriel, can you provide us your DMI information about your machine?

They are included in following files:
/sys/class/dmi/id/sys_vendor
/sys/class/dmi/id/product_name

Beware that they may contain whitespace characters and it is important.

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2017-10-02 13:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 14:08 keyboard backlight max_brightness bug on Dell Latitude E6410 Gabriel M. Elder
2017-09-29 14:11 ` Pali Rohár
2017-09-29 15:19   ` Andy Shevchenko
2017-10-02 11:52     ` Pali Rohár
2017-10-02 13:06       ` Mario.Limonciello
2017-10-02 13:06         ` Mario.Limonciello
2017-10-02 13:15         ` Pali Rohár [this message]
2017-10-02 13:15           ` Pali Rohár
2017-10-02 13:17           ` Andy Shevchenko
  -- strict thread matches above, loose matches on Subject: below --
2017-10-02 19:10 Gabriel M. Elder
2017-09-14 14:32 Gabriel M. Elder
2017-09-14 13:35 Gabriel M. Elder
2017-09-14 13:54 ` Pali Rohár
2017-09-14 14:33   ` Gabriele Mazzotta
2017-09-14 15:25     ` Pali Rohár
2017-10-14 13:50       ` Andy Shevchenko
2017-10-14 15:24         ` Pali Rohár
     [not found] <20170911232527.669a95d04dbb6b53be537852cb8ecb8c.c30a078964.wbe@email22.secureserver.net>
2017-09-14  8:06 ` Pali Rohár
2017-09-12  6:41 Gabriel M. Elder

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=20171002131540.GE10938@pali \
    --to=pali.rohar@gmail.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=gabriel@tekgnowsys.com \
    --cc=gabriele.mzt@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.