public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jamie Iles <jamie@jamieiles.com>
Cc: linux-kernel@vger.kernel.org, vapier@gentoo.org
Subject: Re: [RFC PATCHv2 1/4] drivers/otp: add initial support for OTP memory
Date: Thu, 24 Mar 2011 12:20:05 -0700	[thread overview]
Message-ID: <20110324192005.GA9296@suse.de> (raw)
In-Reply-To: <1300980071-24645-2-git-send-email-jamie@jamieiles.com>

On Thu, Mar 24, 2011 at 03:21:08PM +0000, Jamie Iles wrote:
> +/*
> + * Copyright 2010-2011 Picochip LTD, Jamie Iles
> + * http://www.picochip.com
> + *
> + * This program is free software; you can redistribute it and/or
> + * modify it under the terms of the GNU General Public License
> + * as published by the Free Software Foundation; either version
> + * 2 of the License, or (at your option) any later version.

Do you _really_ mean "any later version"?  Be sure about that please.
You have that wording in all of your files you add, please be careful
about it as you might have copied from code that did not have that
wording (I'm not saying you did, just be sure about this.)

> + */
> +#define pr_fmt(fmt) "otp: " fmt
> +
> +#undef DEBUG

What is this for?

> +#include <linux/cdev.h>
> +#include <linux/delay.h>
> +#include <linux/err.h>
> +#include <linux/fs.h>
> +#include <linux/io.h>
> +#include <linux/list.h>
> +#include <linux/module.h>
> +#include <linux/otp.h>
> +#include <linux/semaphore.h>
> +#include <linux/slab.h>
> +#include <linux/sysfs.h>
> +#include <linux/uaccess.h>
> +
> +static int otp_open(struct inode *inode, struct file *filp);
> +static int otp_release(struct inode *inode, struct file *filp);
> +static ssize_t otp_write(struct file *filp, const char __user *buf,
> +			 size_t len, loff_t *offs);
> +static ssize_t otp_read(struct file *filp, char __user *buf, size_t len,
> +			loff_t *offs);
> +static loff_t otp_llseek(struct file *filp, loff_t offs, int origin);
> +
> +static const struct file_operations otp_fops = {
> +	.owner	    = THIS_MODULE,
> +	.open	    = otp_open,
> +	.release    = otp_release,
> +	.write	    = otp_write,
> +	.read	    = otp_read,
> +	.llseek	    = otp_llseek,
> +};
> +
> +static DEFINE_SEMAPHORE(otp_sem);
> +static int otp_we, otp_strict_programming;
> +static struct otp_device *otp;
> +static dev_t otp_devno;
> +
> +/*
> + * Given a device for one of the otpN devices, get the corresponding
> + * otp_region.
> + */
> +static inline struct otp_region *to_otp_region(struct device *dev)
> +{
> +	return dev ? container_of(dev, struct otp_region, dev) : NULL;
> +}
> +
> +static inline struct otp_device *to_otp_device(struct device *dev)
> +{
> +	return dev ? container_of(dev, struct otp_device, dev) : NULL;
> +}
> +
> +bool otp_strict_programming_enabled(void)
> +{
> +	return otp_strict_programming;
> +}
> +EXPORT_SYMBOL_GPL(otp_strict_programming_enabled);
> +
> +static ssize_t otp_format_show(struct device *dev,
> +			       struct device_attribute *attr, char *buf)
> +{
> +	struct otp_region *region = to_otp_region(dev);
> +	enum otp_redundancy_fmt fmt;
> +	const char *fmt_string;
> +
> +	if (down_interruptible(&otp_sem))
> +		return -ERESTARTSYS;
> +
> +	if (region->ops->get_fmt(region))
> +		fmt = region->ops->get_fmt(region);
> +	else
> +		fmt = OTP_REDUNDANCY_FMT_SINGLE_ENDED;
> +
> +	up(&otp_sem);
> +
> +	if (OTP_REDUNDANCY_FMT_SINGLE_ENDED == fmt)

While some people feel this somehow makes it harder to write bad C code,
it's not the kernel style.  Please reverse this comparison.  If you
accidentally put a '=' in there instead of '==', gcc would warn you
about it.

> +		fmt_string = "single-ended";
> +	else if (OTP_REDUNDANCY_FMT_REDUNDANT == fmt)
> +		fmt_string = "redundant";
> +	else if (OTP_REDUNDANCY_FMT_DIFFERENTIAL == fmt)
> +		fmt_string = "differential";
> +	else if (OTP_REDUNDANCY_FMT_DIFFERENTIAL_REDUNDANT == fmt)
> +		fmt_string = "differential-redundant";
> +	else
> +		fmt_string = NULL;

Just return -EINVAL here.

> +
> +	return fmt_string ? sprintf(buf, "%s\n", fmt_string) : -EINVAL;

Then you don't have to do the embedded if in this statement.

Same thing goes for your other show/store functions.

> +/**
> + * struct otp_device - a picoxcell OTP device.
> + *
> + * @ops:		The operations to use for manipulating the device.
> + * @dev:		The parent device (typically a platform_device) that
> + *			provides the OTP.
> + * @regions:		The regions registered to the device.
> + * @size:		The size of the OTP in bytes.
> + * @driver_data:	Private driver data.
> + */
> +struct otp_device {
> +	const struct otp_device_ops	*ops;
> +	struct device			dev;
> +	struct list_head		regions;
> +	size_t				size;
> +	void				*driver_data;

Why do you need this pointer, can't you use the one in struct device
that is there for this purpose?  Then provide a get/set function to
access this field so that a driver doesn't go and poke in it directly.


thanks,

greg k-h

  parent reply	other threads:[~2011-03-24 19:22 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 15:21 [RFC PATCHv2 0/4] Support for OTP memory Jamie Iles
2011-03-24 15:21 ` [RFC PATCHv2 1/4] drivers/otp: add initial support " Jamie Iles
2011-03-24 18:32   ` Mike Frysinger
2011-03-24 20:35     ` Jamie Iles
2011-03-24 21:33       ` Mike Frysinger
2011-03-25 10:08         ` Jamie Iles
2011-03-25 21:32           ` Mike Frysinger
2011-03-25 22:27             ` Jamie Iles
2011-03-25 22:36               ` Mike Frysinger
2011-03-24 19:20   ` Greg KH [this message]
2011-03-24 20:49     ` Jamie Iles
2011-03-25 20:12   ` Arnd Bergmann
2011-03-25 21:12     ` Greg KH
2011-03-25 22:01       ` Arnd Bergmann
2011-03-25 23:28         ` Greg KH
2011-03-26 11:25           ` Arnd Bergmann
2011-03-26 15:10             ` Greg KH
2011-03-28 13:11               ` Arnd Bergmann
2011-03-25 22:23     ` Jamie Iles
2011-03-25 22:35       ` Arnd Bergmann
2011-03-25 22:38         ` Mike Frysinger
2011-03-25 22:52           ` Jamie Iles
2011-03-25 23:02             ` Arnd Bergmann
2011-03-26  0:21               ` Jamie Iles
2011-03-26  2:16                 ` Mike Frysinger
2011-03-26  2:40                   ` Jamie Iles
2011-03-26 10:54                   ` Arnd Bergmann
2011-03-26 17:55                     ` Mike Frysinger
2011-03-26 20:51                       ` Arnd Bergmann
2011-03-27  3:52                         ` Mike Frysinger
2011-03-27 11:18                           ` Arnd Bergmann
2011-03-25 22:53           ` Arnd Bergmann
2011-03-24 15:21 ` [RFC PATCHv2 2/4] drivers/otp: add support for Picoxcell PC3X3 OTP Jamie Iles
2011-03-24 18:50   ` Mike Frysinger
2011-03-24 20:59     ` Jamie Iles
2011-03-24 21:40       ` Mike Frysinger
2011-03-24 15:21 ` [RFC PATCHv2 3/4] drivers/otp: allow an ioctl to be specified Jamie Iles
2011-03-24 18:35   ` Mike Frysinger
2011-03-24 20:36     ` Jamie Iles
2011-03-24 15:21 ` [RFC PATCHv2 4/4] drivers/otp: convert bfin otp to generic OTP Jamie Iles
2011-03-24 18:52   ` Mike Frysinger
2011-03-24 20:40     ` Jamie Iles
2011-03-24 17:39 ` [RFC PATCHv2 0/4] Support for OTP memory Mike Frysinger
2011-03-24 17:47   ` Jamie Iles
2011-03-24 17:56     ` Mike Frysinger
2011-03-24 18:32       ` Jamie Iles
2011-03-24 18:36         ` Mike Frysinger
2011-03-24 20:38           ` Jamie Iles
2011-03-25  0:12         ` Mark Brown

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=20110324192005.GA9296@suse.de \
    --to=gregkh@suse.de \
    --cc=jamie@jamieiles.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier@gentoo.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