On Sat, Jul 19, 2014 at 10:26:56AM -0400, Benjamin Romer wrote:
> The installer entry in /proc/visorchipset/installer was composed of three
> separate fields as one entry. This patch removes the proc entry and associated
> functions, and creates new fields with distinct entries under sysfs in the
> visorchipset/install directory. The fields are:
> 
>       textid: used to send the ID of a string that should be displayed on
>               s-Par's automatic installation progress screen. Setting this
>               field when not in installation mode (boottotool was set on
>               the previous guest boot) has no effect.
> 
>       remaining_steps: used to set the value of the progress bar on the
>               s-Par automatic installation progress screen. This field has
>               no effect if not in installation mode.
> 
>       error: used to send the ID of a string that should be displayed on
>               s-Par's automatic installation progress screen when an error
>               is encountered during installation. This field has no effect
>               if not in installation mode.
> 
> Signed-off-by: Benjamin Romer <benjamin.ro...@unisys.com>
> ---
>  .../unisys/visorchipset/visorchipset_main.c        | 261 
> +++++++++++----------
>  1 file changed, 134 insertions(+), 127 deletions(-)
> 
> diff --git a/drivers/staging/unisys/visorchipset/visorchipset_main.c 
> b/drivers/staging/unisys/visorchipset/visorchipset_main.c
> index 6036bf5..b13343d 100644
> --- a/drivers/staging/unisys/visorchipset/visorchipset_main.c
> +++ b/drivers/staging/unisys/visorchipset/visorchipset_main.c
> @@ -144,16 +144,6 @@ static VISORCHANNEL *ControlVm_channel;
>  static ssize_t visorchipset_proc_read_writeonly(struct file *file,
>                                               char __user *buf,
>                                               size_t len, loff_t *offset);
> -static ssize_t proc_read_installer(struct file *file, char __user *buf,
> -                                size_t len, loff_t *offset);
> -static ssize_t proc_write_installer(struct file *file,
> -                                 const char __user *buffer,
> -                                 size_t count, loff_t *ppos);
> -
> -static const struct file_operations proc_installer_fops = {
> -     .read = proc_read_installer,
> -     .write = proc_write_installer,
> -};
>  
>  typedef struct {
>       U8 __iomem *ptr;        /* pointer to base address of payload pool */
> @@ -315,15 +305,43 @@ static ssize_t show_boottotool(struct device *dev,
>  static ssize_t store_boottotool(struct device *dev,
>       struct device_attribute *attr, const char *buf, size_t count);
>  
> +static ssize_t show_error(struct device *dev, struct device_attribute *attr,
> +     char *buf);
> +
> +static ssize_t store_error(struct device *dev, struct device_attribute *attr,
> +     const char *buf, size_t count);
> +
> +static ssize_t show_textid(struct device *dev, struct device_attribute *attr,
> +     char *buf);
> +
> +static ssize_t store_textid(struct device *dev,      struct device_attribute 
> *attr,
> +     const char *buf, size_t count);
> +
> +static ssize_t show_remaining_steps(struct device *dev,
> +     struct device_attribute *attr, char *buf);
> +
> +static ssize_t store_remaining_steps(struct device *dev,
> +     struct device_attribute *attr, const char *buf, size_t count);
> +
>  static DEVICE_ATTR(toolaction, S_IRUSR | S_IWUSR, show_toolaction,
>       store_toolaction);
>  
>  static DEVICE_ATTR(boottotool, S_IRUSR | S_IWUSR, show_boottotool,
>       store_boottotool);
>  
> +static DEVICE_ATTR(error, S_IRUSR | S_IWUSR, show_error, store_error);
> +
> +static DEVICE_ATTR(textid, S_IRUSR | S_IWUSR, show_textid, store_textid);
> +
> +static DEVICE_ATTR(remaining_steps, S_IRUSR | S_IWUSR, show_remaining_steps,
> +     store_remaining_steps);

DEVICE_ATTR_RW() for all of these please.

thanks,

greg k-h
_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to