From: Nikolaus Voss <nv@vosn.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] usb: typec: tps6598x: handle block writes separately with plain-I2C adapters
Date: Wed, 20 Feb 2019 16:18:04 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1902201616290.8597@fox.voss.local> (raw)
In-Reply-To: <be1f988c-5b2f-91cf-d210-1e28c09f106f@roeck-us.net>
On Wed, 20 Feb 2019, Guenter Roeck wrote:
> On 2/20/19 4:57 AM, Nikolaus Voss wrote:
>> Commit 1a2f474d328f handles block _reads_ separately with plain-I2C
>> adapters, but the problem described with regmap-i2c not handling
>> SMBus block transfers (i.e. read and writes) correctly also exists
>> with writes.
>>
>> As workaround, this patch adds a block write function the same way
>> 1a2f474d328f adds a block read function.
>>
>> Fixes: 1a2f474d328f ("usb: typec: tps6598x: handle block reads separately
>> with plain-I2C adapters")
>> Fixes: 0a4c005bd171 ("usb: typec: driver for TI TPS6598x USB Power Delivery
>> controllers")
>> Signed-off-by: Nikolaus Voss <nikolaus.voss@loewensteinmedical.de>
>> ---
>> v2: fix tps6598x_exec_cmd also
>> ---
>> drivers/usb/typec/tps6598x.c | 26 ++++++++++++++++++++------
>> 1 file changed, 20 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/usb/typec/tps6598x.c b/drivers/usb/typec/tps6598x.c
>> index c84c8c189e90..c54b73fb2a2f 100644
>> --- a/drivers/usb/typec/tps6598x.c
>> +++ b/drivers/usb/typec/tps6598x.c
>> @@ -110,6 +110,20 @@ tps6598x_block_read(struct tps6598x *tps, u8 reg, void
>> *val, size_t len)
>> return 0;
>> }
>> +static int tps6598x_block_write(struct tps6598x *tps, u8 reg,
>> + void *val, size_t len)
>> +{
>> + u8 data[len + 1];
>> +
>
> You should use TPS_MAX_LEN + 1 here to avoid the variable length array.
> See upstream commit 0bb95f80a38f8 ("Makefile: Globally enable VLA warning")
> and 8d361fa2c29dc ("usb: typec: tps6598x: Remove VLA usage"). Not sure if
> the WARN_ON introduced by 8d361fa2c29dc is really needed; I dislike
> unnecessary runtime checks.
Thanks for the pointer, I fixed this...
Nikolaus
next prev parent reply other threads:[~2019-02-20 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180425142209.30745-1-heikki.krogerus@linux.intel.com>
2018-09-10 5:05 ` [PATCH] " Nikolaus Voss
2019-02-20 12:14 ` Heikki Krogerus
2019-02-20 12:56 ` Nikolaus Voss
2019-02-20 12:57 ` [PATCHv2] " Nikolaus Voss
2019-02-20 13:30 ` Heikki Krogerus
2019-02-20 13:38 ` Nikolaus Voss
2019-02-20 14:14 ` Heikki Krogerus
2019-02-20 14:30 ` Heikki Krogerus
2019-02-20 15:08 ` Nikolaus Voss
2019-02-20 14:45 ` Guenter Roeck
2019-02-20 15:18 ` Nikolaus Voss [this message]
2019-02-20 15:02 ` Greg Kroah-Hartman
2019-02-20 15:22 ` Nikolaus Voss
2019-02-20 16:22 ` Greg Kroah-Hartman
2019-02-21 8:37 ` Nikolaus Voss
2019-02-21 9:52 ` Greg Kroah-Hartman
2019-02-21 10:40 ` kbuild test robot
2019-02-20 15:11 ` [PATCHv3] " Nikolaus Voss
2019-02-20 15:35 ` Guenter Roeck
2019-02-20 15:36 ` Guenter Roeck
2019-02-21 8:41 ` Nikolaus Voss
2019-02-21 9:08 ` Heikki Krogerus
2019-02-21 9:42 ` Nikolaus Voss
2019-02-21 9:52 ` Greg Kroah-Hartman
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=alpine.DEB.2.20.1902201616290.8597@fox.voss.local \
--to=nv@vosn.de \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®