Re: [PATCH] Add sysfs support for fbdefio delay
flat view
From: Rick L. Vinyard, Jr. <hidden>
Date: 2010-02-25 22:41:36
Also in:
lkml
Bruno Prémont wrote:
On Thu, 25 February 2010 "Rick L. Vinyard Jr." [off-list ref] wrote:quoted
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....quoted
@@ -503,6 +584,12 @@ static struct device_attribute device_attrs[] = { #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. -- Rick