linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
To: Pantelis Antoniou
	<pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
Cc: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Grant Likely
	<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Matt Porter <mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>,
	Koen Kooi
	<koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org>,
	Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v2 3/4] of: overlay: Add sysfs attributes
Date: Thu, 23 Apr 2015 14:33:46 +0200	[thread overview]
Message-ID: <20150423123346.GA19166@kroah.com> (raw)
In-Reply-To: <6E391B8F-936A-4FD1-B8CC-C9B5FCE0B291-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>

On Thu, Apr 23, 2015 at 03:00:03PM +0300, Pantelis Antoniou wrote:
> Hi Rob,
> 
> > On Apr 15, 2015, at 04:27 , Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > 
> > On Tue, Apr 7, 2015 at 2:23 PM, Pantelis Antoniou
> > <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org> wrote:
> >> Implement a number of sysfs attributes for overlays.
> >> 
> >> * A throw once master enable switch to protect against any
> >> further overlay applications if the administrator desires so.
> > 
> > This one should be a separate patch.
> > 
> 
> OK.
> 
> >> * A per overlay targets sysfs attribute listing the targets of
> >> the installed overlay.
> > 
> > What are targets? "targets lists targets" does not help me. The
> > documentation doesn't help me either.
> > 
> 
> It lists the targets of the overlay that has been applied. What do
> you need in order to be helped? I mean what do you want listed?
> 
> >> * A per overlay can_remove sysfs attribute that reports whether
> >> the overlay can be removed or not due to another overlapping overlay.
> >> 
> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
> >> ---
> >> drivers/of/overlay.c | 167 ++++++++++++++++++++++++++++++++++++++++++++++++++-
> >> 1 file changed, 166 insertions(+), 1 deletion(-)
> >> 
> >> diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
> >> index f17f5ef..c54d097 100644
> >> --- a/drivers/of/overlay.c
> >> +++ b/drivers/of/overlay.c
> >> @@ -21,6 +21,7 @@
> >> #include <linux/err.h>
> >> #include <linux/idr.h>
> >> #include <linux/sysfs.h>
> >> +#include <linux/atomic.h>
> >> 
> >> #include "of_private.h"
> >> 
> >> @@ -55,8 +56,12 @@ struct of_overlay {
> >>        struct kobject kobj;
> >> };
> >> 
> >> +/* master enable switch; once set to 0 can't be re-enabled */
> >> +static atomic_t ov_enable = ATOMIC_INIT(1);
> >> +
> >> static int of_overlay_apply_one(struct of_overlay *ov,
> >>                struct device_node *target, const struct device_node *overlay);
> >> +static int overlay_removal_is_ok(struct of_overlay *ov);
> >> 
> >> static int of_overlay_apply_single_property(struct of_overlay *ov,
> >>                struct device_node *target, struct property *prop)
> >> @@ -345,6 +350,144 @@ static struct kobj_type of_overlay_ktype = {
> >> 
> >> static struct kset *ov_kset;
> >> 
> >> +static ssize_t enable_read(struct file *filp, struct kobject *kobj,
> >> +               struct bin_attribute *bin_attr, char *buf,
> >> +               loff_t offset, size_t count)
> >> +{
> >> +       char tbuf[3];
> >> +
> >> +       if (offset < 0)
> >> +               return -EINVAL;
> >> +
> >> +       if (offset >= sizeof(tbuf))
> >> +               return 0;
> >> +
> >> +       if (count > sizeof(tbuf) - offset)
> >> +               count = sizeof(tbuf) - offset;
> >> +
> >> +       /* fill in temp */
> >> +       tbuf[0] = '0' + atomic_read(&ov_enable);
> >> +       tbuf[1] = '\n';
> >> +       tbuf[2] = '\0';
> >> +
> >> +       /* copy to buffer */
> >> +       memcpy(buf, tbuf + offset, count);
> >> +
> >> +       return count;
> >> +}
> >> +
> >> +static ssize_t enable_write(struct file *filp, struct kobject *kobj,
> >> +               struct bin_attribute *bin_attr, char *buf,
> >> +               loff_t off, size_t count)
> >> +{
> >> +       unsigned int new_enable;
> >> +
> >> +       if (off != 0 || (buf[0] != '0' && buf[0] != '1'))
> >> +               return -EINVAL;
> >> +
> >> +       new_enable = (unsigned int)(buf[0] - '0');
> >> +       if (new_enable > 1)
> >> +               return -EINVAL;
> >> +
> >> +       /* NOP for same value */
> >> +       if (new_enable == atomic_read(&ov_enable))
> >> +               return count;
> >> +
> >> +       /* if we've disabled it, no going back */
> >> +       if (atomic_read(&ov_enable) == 0)
> >> +               return -EPERM;
> >> +
> >> +       atomic_set(&ov_enable, new_enable);
> >> +       return count;
> >> +}
> >> +
> >> +/* just a single char + '\n' + '\0' */
> >> +static BIN_ATTR_RW(enable, 3);
> > 
> > Why are you using bin attribute? You are complicating the
> > implementation needlessly.
> > 
> 
> It’s the same reason that the device tree core is using it.

It is doing that for "raw" device tree files, not individual attributes,
right?

> Believe it or not, this is the simplest way to do it.
> If you take a look at the sysfs attribute implementation, the binary
> implementation is the one that’s using the least amount of code.

Then something is really wrong here.

> To use a non-binary method we have to register per ktype sysfs_ops
> and duplicate the way the non-binary attribute works.

really?  Again, something must be wrong.

> For the gory details look at sysfs_add_file_mode_ns() in fs/sysfs/file.c
> 
> I can add the sysfs_ops but that’s going to be more complicated not less.

Only use binary sysfs files if you are accepting binary data directly
from userspace and using it as a "pass-through" to the kernel.

Otherwise just use a "normal" sysfs file.  I don't understand the
problem here, sysfs shouldn't be hard to use for simple attributes, that
was not the goal here at all.

thanks,

greg k-h

  parent reply	other threads:[~2015-04-23 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 19:23 [PATCH v2 0/4] of: overlay: Assorted fixes Pantelis Antoniou
2015-04-07 19:23 ` [PATCH v2 2/4] of: overlay: kobjectify overlay objects Pantelis Antoniou
     [not found] ` <1428434632-13789-1-git-send-email-pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-07 19:23   ` [PATCH v2 1/4] of: unittest: overlay: Keep track of created overlays Pantelis Antoniou
     [not found]     ` <1428434632-13789-2-git-send-email-pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-15  1:29       ` Rob Herring
2015-04-07 19:23   ` [PATCH v2 3/4] of: overlay: Add sysfs attributes Pantelis Antoniou
     [not found]     ` <1428434632-13789-4-git-send-email-pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-15  1:27       ` Rob Herring
     [not found]         ` <CAL_JsqLMVBfQpmSjg9qfOvtM3RXMY3Dm+knN8h54gDCzx513-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-23 12:00           ` Pantelis Antoniou
     [not found]             ` <6E391B8F-936A-4FD1-B8CC-C9B5FCE0B291-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-23 12:33               ` Greg KH [this message]
2015-04-23 12:39                 ` Pantelis Antoniou
     [not found]                   ` <98237E9E-04CB-4CD5-8B2F-63F070B54459-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>
2015-04-23 12:54                     ` Greg KH
     [not found]                       ` <20150423125441.GA32303-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-04-23 12:59                         ` Pantelis Antoniou
2015-04-23 13:04                           ` Greg KH
2015-04-07 19:23 ` [PATCH v2 4/4] Documentation: ABI: /sys/firmware/devicetree/overlays Pantelis Antoniou

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=20150423123346.GA19166@kroah.com \
    --to=greg-u8xffu+wg4eavxtiumwx3w@public.gmane.org \
    --cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
    --cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).