From: Jonathan Woithe <jwoithe@just42.net>
To: Micha?? K??pie?? <kernel@kempniu.pl>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] fujitsu_init() cleanup
Date: Sat, 4 Mar 2017 12:17:23 +1030 [thread overview]
Message-ID: <20170304014723.GA7944@marvin.atrad.com.au> (raw)
In-Reply-To: <20170301081044.12141-1-kernel@kempniu.pl>
Hi Michael
On Wed, Mar 01, 2017 at 09:10:40AM +0100, Micha?? K??pie?? wrote:
> These patches should make fujitsu_init() a bit more palatable. No
> changes are made to platform device code yet, for clarity these will be
> posted in a separate series after this one gets applied.
I have a preliminary report. The backlight functionality remains functional
on an S7020 across all four of the patches in this series and with the
additional 2-patch cleanup series applied.
With regard to patch 2/4 you wrote:
> Jonathan, this *really* needs testing on relevant hardware. After
> applying this patch, you should be able to turn LCD backlight on and off
> using /sys/class/backlight/fujitsu-laptop/bl_power. Also, the value
> returned by that attribute upon read should be in sync with actual
> backlight state even right after loading the module (i.e. before writing
> anything to bl_power). Please let me know if any of the above is not
> true and the module works correctly without this patch applied.
With patch 2/4 applied:
* It is possible to read bl_power
* It is possible to write a value to bl_power and read that value back
* Writing values to bl_power does not appear to affect the LCD panel in
any way. That is, the backlight remains unchanged regardless of the
value written.
* Behaviour is the same both under X and from the terminal.
Backing out patch 2/4 but with all others still in place, resulted in no
change in behaviour. So while bl_power had no effect with patch 2/4 in
place, it seems that patch 2/4 is *not* the cause of this.
I shall run some more bl_power tests and complete a review of the code later
this weekend.
Regards
jonathan
next prev parent reply other threads:[~2017-03-04 2:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 8:10 Michał Kępień
2017-03-01 8:10 ` [PATCH v2 1/4] platform/x86: fujitsu-laptop: register backlight device in a separate function Michał Kępień
2017-03-01 8:10 ` [PATCH v2 2/4] platform/x86: fujitsu-laptop: do not use call_fext_func() for LCD blanking Michał Kępień
2017-03-01 8:10 ` [PATCH v2 3/4] platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present Michał Kępień
2017-03-01 8:10 ` [PATCH v2 4/4] platform/x86: fujitsu-laptop: cleanup error labels in fujitsu_init() Michał Kępień
[not found] ` <20170301223912.GF28335@marvin.atrad.com.au>
2017-03-01 23:26 ` [PATCH v2 0/4] fujitsu_init() cleanup [resend due to vger error] Jonathan Woithe
2017-03-02 7:19 ` [PATCH v2 0/4] fujitsu_init() cleanup Michał Kępień
2017-03-03 12:39 ` Jonathan Woithe
2017-03-04 1:47 ` Jonathan Woithe [this message]
2017-03-05 23:48 ` Jonathan Woithe
2017-03-06 4:49 ` Michał Kępień
2017-03-06 5:01 ` Jonathan Woithe
2017-03-06 8:10 ` Jonathan Woithe
2017-03-06 9:33 ` Michał Kępień
2017-03-06 18:47 ` Michał Kępień
2017-03-07 3:50 ` Jonathan Woithe
2017-03-07 8:08 ` Michał Kępień
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=20170304014723.GA7944@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=kernel@kempniu.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®