From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rick L. Vinyard, Jr." Date: Thu, 25 Feb 2010 22:41:21 +0000 Subject: Re: [PATCH] Add sysfs support for fbdefio delay Message-Id: <49e34e8ba40c44c622171868798f9919.squirrel@intranet.cs.nmsu.edu> List-Id: References: <201002252215.o1PMFnoP011425@mustang.cs.nmsu.edu> <20100225233250.241e7d6d@neptune.home> In-Reply-To: <20100225233250.241e7d6d@neptune.home> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: Bruno =?iso-8859-1?Q?Pr=C3=A9mont?= Cc: linux-kernel@vger.kernel.org, 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 Bruno Pr=C3=A9mont wrote: > On Thu, 25 February 2010 "Rick L. Vinyard Jr." > wrote: >> This patch adds support for examining and modifying the fbdefio delay >> parameter through sysfs. It also adds two driver definable minimum >> and maximum bounds. >> >> The default behavior is to not permit modifications if delay_max is 0, >> thus preventing modification of the delay if the driver does not >> explicitly permit modification. >> > > ... > >> @@ -503,6 +584,12 @@ static struct device_attribute device_attrs[] =3D { >> #ifdef CONFIG_FB_BACKLIGHT >> __ATTR(bl_curve, S_IRUGO|S_IWUSR, show_bl_curve, store_bl_curve), >> #endif >> +#ifdef CONFIG_FB_DEFERRED_IO >> + __ATTR(defio_delay, S_IRUGO|S_IWUSR, >> + show_defio_delay, store_defio_delay), >> + __ATTR(defio_delay_min, S_IRUGO, show_defio_delay_min, NULL), >> + __ATTR(defio_delay_max, S_IRUGO, show_defio_delay_max, NULL), >> +#endif >> }; >> >> int fb_init_device(struct fb_info *fb_info) > > Would it be reasonable to add these attributes in > fb_deferred_io_init() and remove them in fb_deferred_io_cleanup()? > This would also make it possible to add write permission to delay > attribute only when it effectively can be modified. > > IMHO having only attributes pertinent to the features supported by the > framebuffer is better than having all the possible ones and those of > unsupported features returning -ENODEV. > > Bruno > I looked at that, but it seems like all the sysfs stuff has been co-located in fbsysfs.c, so I tried to just follow the pattern of the backlight code which takes the same approach. --=20 Rick