From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>,
Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] i2c-stub: Remember the number of emulated chips
Date: Thu, 10 Jul 2014 05:14:39 -0700 [thread overview]
Message-ID: <53BE83AF.9060006@roeck-us.net> (raw)
In-Reply-To: <20140710124511.05108894-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On 07/10/2014 03:45 AM, Jean Delvare wrote:
> This makes initialization, cleanup and look-up easier.
>
> Signed-off-by: Jean Delvare <jdelvare-l3A5Bk7waGM@public.gmane.org>
> Cc: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
> ---
> This applies on top of Guenter's patch "i2c: stub: Add support for
> SMBus block commands", v2.
Looks good.
Reviewed-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
>
> drivers/i2c/i2c-stub.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> --- linux-3.16-rc3.orig/drivers/i2c/i2c-stub.c 2014-07-09 12:57:46.383772594 +0200
> +++ linux-3.16-rc3/drivers/i2c/i2c-stub.c 2014-07-09 13:09:42.982241933 +0200
> @@ -62,6 +62,7 @@ struct stub_chip {
> };
>
> static struct stub_chip *stub_chips;
> +static int stub_chips_nr;
>
> static struct smbus_block_data *stub_find_block(struct device *dev,
> struct stub_chip *chip,
> @@ -95,7 +96,7 @@ static s32 stub_xfer(struct i2c_adapter
> struct smbus_block_data *b;
>
> /* Search for the right chip */
> - for (i = 0; i < MAX_CHIPS && chip_addr[i]; i++) {
> + for (i = 0; i < stub_chips_nr; i++) {
> if (addr == chip_addr[i]) {
> chip = stub_chips + i;
> break;
> @@ -281,12 +282,14 @@ static int __init i2c_stub_init(void)
> }
>
> /* Allocate memory for all chips at once */
> - stub_chips = kzalloc(i * sizeof(struct stub_chip), GFP_KERNEL);
> + stub_chips_nr = i;
> + stub_chips = kcalloc(stub_chips_nr, sizeof(struct stub_chip),
> + GFP_KERNEL);
At some point can use devm_kcalloc ...
> if (!stub_chips) {
> pr_err("i2c-stub: Out of memory\n");
and get rid of this message.
> return -ENOMEM;
> }
> - for (i--; i >= 0; i--)
> + for (i = 0; i < stub_chips_nr; i++)
> INIT_LIST_HEAD(&stub_chips[i].smbus_blocks);
>
> ret = i2c_add_adapter(&stub_adapter);
>
>
next prev parent reply other threads:[~2014-07-10 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 10:45 [PATCH 1/2] i2c-stub: Remember the number of emulated chips Jean Delvare
[not found] ` <20140710124511.05108894-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-07-10 10:56 ` [PATCH 2/2] i2c-stub: Add support for banked register ranges Jean Delvare
[not found] ` <20140710125659.015f1517-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-07-10 18:40 ` Guenter Roeck
[not found] ` <20140710184036.GA6950-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2014-07-10 21:30 ` Jean Delvare
[not found] ` <20140710233040.59d1dfea-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2014-07-10 22:18 ` Guenter Roeck
2014-07-11 4:27 ` Guenter Roeck
2014-07-17 17:18 ` Wolfram Sang
2014-07-10 12:14 ` Guenter Roeck [this message]
2014-07-17 17:15 ` [PATCH 1/2] i2c-stub: Remember the number of emulated chips Wolfram Sang
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=53BE83AF.9060006@roeck-us.net \
--to=linux-0h96xk9xttrk1umjsbkqmq@public.gmane.org \
--cc=jdelvare-l3A5Bk7waGM@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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).