linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>,
	Jaya Kumar <jayakumar.lkml@gmail.com>,
	linux-kernel@vger.kernel.org, felipe.balbi@nokia.com,
	linux-usb@vger.kernel.org, oliver@neukum.org,
	linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
	npavel@ituner.com, tomi.valkeinen@nokia.com, tony@atomide.com,
	florianschandinat@gmx.de, krzysztof.h1@wp.pl,
	akpm@linux-foundation.org, linux-fbdev@vger.kernel.org,
	jkosina@suse.cz, bonbons@linux-vserver.org
Subject: Re: [PATCH] hid Logitech G13 Driver 0.0.5
Date: Sat, 19 Jun 2010 17:57:21 +0200	[thread overview]
Message-ID: <201006191757.22035.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100303051311.GA4651@elf.ucw.cz>

Dne St 3. března 2010 06:13:12 Pavel Machek napsal(a):
> Hi!
> 
> > >> +/*
> > >> + * This is a default logo to be loaded upon driver initialization
> > >> + * replacing the default Logitech G13 image loaded on device
> > >> + * initialization. This is to provide the user a cue that the
> > >> + * Linux driver is loaded and ready.
> > >> + *
> > >> + * This logo contains the text G13 in the center with two penguins
> > >> + * on each side of the text. The penguins are a 33x40 rendition of
> > >> + * the default framebuffer 80x80 monochrome image scaled down and
> > >> + * cleaned up to retain something that looks a little better than
> > >> + * a simple scaling.
> > >> + *
> > >> + * This logo is a simple xbm image created in GIMP and exported.
> > >> + * To view the image copy the following two #defines plus the
> > >> + * g13_lcd_bits to an ASCII text file and save with extension
> > >> + * .xbm, then open with GIMP or any other graphical editor
> > >> + * such as eog that recognizes the .xbm format.
> > >> + */
> > > 
> > > ...
> > > 
> > >> +static unsigned char g13_lcd_bits[] = {
> > >> + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> > >> 0x00,
> > > 
> > > I think you'll agree above is not an elegant solution.
> > 
> > I could make it a config option.
> 
> You get about 10 complains already, but you are not willing to solve
> it. No, config option does not help.
> 
> If you want to, make it separate patch so we can reject it separately.
> 
> > >> +static DEVICE_ATTR(rgb, 0666, g13_rgb_show, g13_rgb_store);
> > > 
> > > Reading above code, it looks like this new userspace sysfs attribute
> > > is for backlight control. Could that be better exposed using the
> > > existing backlight class?
> > 
> > I looked at the backlight class and it didn't seem to be a very good fit.
> > 
> > /* This structure defines all the properties of a backlight */
> > struct backlight_properties {
> > 
> > 	/* Current User requested brightness (0 - max_brightness) */
> > 	int brightness;
> > 	/* Maximal value for brightness (read-only) */
> > 	int max_brightness;
> > 	/* Current FB Power mode (0: full on, 1..3: power saving
> > 	
> > 	   modes; 4: full off), see FB_BLANK_XXX */
> > 	
> > 	int power;
> > 	/* FB Blanking active? (values as for power) */
> > 	/* Due to be removed, please use (state & BL_CORE_FBBLANK) */
> > 	int fb_blank;
> > 	/* Flags used to signal drivers of state changes */
> > 	/* Upper 4 bits are reserved for driver internal use */
> > 	unsigned int state;
> > 
> > };
> > 
> > The g13's backlight doesn't support any of these properties. All you can
> > set is an rgb value on the g13; no power modes, no brightness, etc. I
> > could add a brightness attribute by scaling the rgb values, but I would
> > prefer to do that from userspace rather than the driver since it's not
> > supported in the device itself.
> > 
> > And, we'd still have to have the rgb attribute since the backlight class
> > doesn't have color.
> 
> Or you could pretend you have 3 different backlights? ....which is
> actually what you have...?
> 									Pavel

Any updates on this?

btw. it'd be good if we could use the g13fb on G15 ... would that be possible?
Cheers!

  reply	other threads:[~2010-06-19 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 18:48 [PATCH] hid Logitech G13 Driver 0.0.5 Rick L. Vinyard Jr.
     [not found] ` <201003021848.o22ImLSS004394-wBm1UmGkUFOpxMv/W9li2JVzexx5G7lz@public.gmane.org>
2010-03-02 23:23   ` Jaya Kumar
2010-03-02 23:46     ` Rick L. Vinyard, Jr.
     [not found]       ` <24ab70ff629c48b6d10ce0cf6dc5d64b.squirrel-2xSMGd46i5akveL4JqN78fZ8FUJU4vz8@public.gmane.org>
2010-03-03  5:13         ` Pavel Machek
2010-06-19 15:57           ` Marek Vasut [this message]
2010-06-21 12:43             ` Jiri Kosina
2010-06-22 18:34               ` Rick L. Vinyard, Jr.
2010-06-23 10:23                 ` Bruno Prémont
2010-06-23 10:30                   ` Jiri Kosina
     [not found]                   ` <20100623122344.372e5f75-hY15tx4IgV39zxVx7UNMDg@public.gmane.org>
2010-06-23 13:51                     ` Rick L. Vinyard, Jr.

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=201006191757.22035.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=felipe.balbi@nokia.com \
    --cc=florianschandinat@gmx.de \
    --cc=jayakumar.lkml@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=krzysztof.h1@wp.pl \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=npavel@ituner.com \
    --cc=oliver@neukum.org \
    --cc=pavel@ucw.cz \
    --cc=rvinyard@cs.nmsu.edu \
    --cc=tomi.valkeinen@nokia.com \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).