From: Jean Delvare <jdelvare@suse.de>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 WIP 3/5] i2c-parport: define ports to connect
Date: Tue, 19 May 2015 09:50:47 +0200 [thread overview]
Message-ID: <1432021847.24979.15.camel@chaos.site> (raw)
In-Reply-To: <1430907377-17147-3-git-send-email-sudipm.mukherjee@gmail.com>
Hi Sudip,
Le Wednesday 06 May 2015 à 15:46 +0530, Sudip Mukherjee a écrit :
> as of now i2c-parport was connecting to all the available parallel
> ports. Lets limit that to maximum of 4 instances and at the same time
> define which instance connects to which parallel port
A leading capital and a trailing dot would look better.
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
> drivers/i2c/busses/i2c-parport.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-parport.c b/drivers/i2c/busses/i2c-parport.c
> index a1fac5a..a9b25c3 100644
> --- a/drivers/i2c/busses/i2c-parport.c
> +++ b/drivers/i2c/busses/i2c-parport.c
> @@ -46,6 +46,9 @@ struct i2c_par {
>
> static LIST_HEAD(adapter_list);
> static DEFINE_MUTEX(adapter_list_lock);
> +#define MAX_DEVICE 4
> +static int parport[MAX_DEVICE] = {0, -1, -1, -1};
> +
>
> /* ----- Low-level parallel port access ----------------------------------- */
>
> @@ -163,6 +166,18 @@ static void i2c_parport_irq(void *data)
> static void i2c_parport_attach(struct parport *port)
> {
> struct i2c_par *adapter;
> + int i;
> +
> + for (i = 0; i < MAX_DEVICE; i++) {
> + if (parport[i] == -1)
> + continue;
> + if (port->number == parport[i])
> + break;
> + }
> + if (i == MAX_DEVICE) {
> + pr_err("port mentioned not found\n");
This error message needs to be improved. Someone seeing this in his/her
logs would have no idea where it comes from and what it means exactly.
You want to add "i2c-parport: " at the beginning, and say which port
number was specified.
> + return;
> + }
>
> adapter = kzalloc(sizeof(struct i2c_par), GFP_KERNEL);
> if (adapter == NULL) {
> @@ -298,5 +313,11 @@ MODULE_AUTHOR("Jean Delvare <jdelvare@suse.de>");
> MODULE_DESCRIPTION("I2C bus over parallel port");
> MODULE_LICENSE("GPL");
>
> +module_param_array(parport, int, NULL, 0);
> +MODULE_PARM_DESC(parport, "Atmost 4 instances are allowed.\n"
You should first say what the parameter does, before going into the
details. Please use __stringify(MAX_DEVICE) instead of hard-coding 4, so
that it doesn't need to be updated if MAX_DEVICE ever changes.
> + "Mention portnumbers in array.\n"
Missing space between "port" and "numbers". Don't mention that this is
an array here, "modinfo" already prints the parameter type. For improved
readability, please also add a leading space to the second and following
lines (as done for parameter "type" in i2c-parport.h.)
> + "If the port is not to be used mention -1.\n"
> + "Default is one instance connected to parport0\n");
Missing trailing dot.
> +
> module_init(i2c_parport_init);
> module_exit(i2c_parport_exit);
I tested this patch and it works fine.
Tested-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-05-19 7:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 10:16 [PATCH v5 WIP 1/5] parport: add device-model to parport subsystem Sudip Mukherjee
2015-05-06 10:16 ` [PATCH v5 WIP 2/5] staging: panel: use new parport device model Sudip Mukherjee
2015-05-19 11:18 ` Dan Carpenter
2015-05-20 8:23 ` Jean Delvare
2015-05-06 10:16 ` [PATCH v5 WIP 3/5] i2c-parport: define ports to connect Sudip Mukherjee
2015-05-19 7:50 ` Jean Delvare [this message]
2015-05-19 8:44 ` Sudip Mukherjee
2015-05-19 9:28 ` Jean Delvare
2015-05-19 9:58 ` Sudip Mukherjee
2015-05-19 11:23 ` Dan Carpenter
2015-05-19 12:23 ` Jean Delvare
2015-05-06 10:16 ` [PATCH v5 WIP 4/5] i2c-parport: use new parport device model Sudip Mukherjee
2015-05-20 7:57 ` Jean Delvare
2015-05-20 8:16 ` Sudip Mukherjee
2015-05-06 10:16 ` [PATCH v5 WIP 5/5] paride: " Sudip Mukherjee
2015-05-19 11:32 ` Dan Carpenter
2015-05-19 12:32 ` Sudip Mukherjee
2015-05-20 8:07 ` Jean Delvare
2015-05-20 8:33 ` Sudip Mukherjee
2015-05-19 11:08 ` [PATCH v5 WIP 1/5] parport: add device-model to parport subsystem Dan Carpenter
2015-05-19 13:18 ` Sudip Mukherjee
2015-05-20 7:54 ` Jean Delvare
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=1432021847.24979.15.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=dan.carpenter@oracle.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
/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).