mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: pancho horrillo <pancho@pancho.name>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix a bug on appledisplay.c regarding signedness
Date: Wed, 2 Dec 2009 20:31:04 +0100	[thread overview]
Message-ID: <20091202193104.GB7362@pancho.name> (raw)
In-Reply-To: <20091202191942.GA7362@pancho.name>

Hi!

bug description:  If the brightness level on the apple display is 128 or
higher, the driver will complain on startup:

"Error while getting initial brightness: -128"

Actual                  Driver
Brightness level        Reported value
0                       0
...                     ...
126                     126
127                     127
128                     -128 (aha! :-)
129                     -127
...                     ...
255                     -1

Also, the reported brightness via /sys interface will present the same
inconsistency.

I realized that this was simply because the monitor transmits its data
as an unsigned char (uint8_t), and in the code it is treated as a signed
char.

I consulted Caskey L. Dickson's acdctl sources to ascertain this.  He
used uint8_t there.   I also checked the usb_* functions definitions to be
sure that I was not second-guessing them.  Yep, they accept (void *) in
the relevant parameters, so it's up to us to decide the type of the
payload.

I've tested it and works like a charm now.

I have emailed the author of the driver, Michael Hanselmann, and he said:
On Wed, Dec 02, 2009 at 05:14:26PM +0000, Michael Hanselmann wrote:
[...]
> If I remember correctly, Linux on PowerPC uses unsigned chars by
> default. I never tested the driver on a non-PowerPC platform and hence
> may never have seen this.


Please, review and push the patch, if you deem it adequate.

Thanks a bunch!

Signed-off-by: pancho horrillo <pancho@pancho.name>

diff -purN a/drivers/usb/misc/appledisplay.c b/drivers/usb/misc/appledisplay.c
--- a/drivers/usb/misc/appledisplay.c	2009-11-10 01:32:31.000000000 +0100
+++ b/drivers/usb/misc/appledisplay.c	2009-12-02 20:05:00.000000000 +0100
@@ -72,8 +72,8 @@ struct appledisplay {
 	struct usb_device *udev;	/* usb device */
 	struct urb *urb;		/* usb request block */
 	struct backlight_device *bd;	/* backlight device */
-	char *urbdata;			/* interrupt URB data buffer */
-	char *msgdata;			/* control message data buffer */
+	uint8_t *urbdata;		/* interrupt URB data buffer */
+	uint8_t *msgdata;		/* control message data buffer */
 
 	struct delayed_work work;
 	int button_pressed;

-- 
pancho horrillo

To be conscious that
you are ignorant is a great step
to knowledge.

		Benjamin Disraeli

  reply	other threads:[~2009-12-02 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 19:19 [PATCH 1/2] Add USB device ID for Apple Cinema Display 23in 2007 pancho horrillo
2009-12-02 19:31 ` pancho horrillo [this message]
2009-12-02 19:38   ` [PATCH 2/2] Fix a bug on appledisplay.c regarding signedness Sergei Shtylyov
2009-12-02 20:44     ` pancho horrillo
2009-12-03  3:20       ` Greg KH
2009-12-22 19:29       ` Greg KH
2009-12-23 10:09         ` pancho horrillo

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=20091202193104.GB7362@pancho.name \
    --to=pancho@pancho.name \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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®