From: Wolfram Sang <wsa@the-dreams•de>
To: Ray Jui <ray.jui@broadcom•com>
Cc: Mark Rutland <mark.rutland@arm•com>,
devicetree@vger•kernel.org,
Lori Hikichi <lori.hikichi@broadcom•com>,
Florian Fainelli <f.fainelli@gmail•com>,
Shivaraj Shetty <sshetty1@broadcom•com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom•com>,
linux-kernel@vger•kernel.org,
Icarus Chau <icarus.chau@broadcom•com>,
Rob Herring <robh+dt@kernel•org>,
bcm-kernel-feedback-list@broadcom•com, linux-i2c@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH v1 1/1] i2c: iproc: Add i2c repeated start capability
Date: Tue, 24 Sep 2019 20:57:57 +0200 [thread overview]
Message-ID: <20190924185757.GA1538@kunai> (raw)
In-Reply-To: <5ab79d0e-eb54-8fe1-1ca3-e763a17c6426@broadcom.com>
[-- Attachment #1.1: Type: text/plain, Size: 435 bytes --]
> In my opinion, it's probably better to continue to support master_xfer in
> our driver (with obvious limitations), in order to allow i2ctransfer (or any
> apps that use I2C RDWR) to continue to work.
>
> What do you think?
Yes, don't break it for users. We should have paid more attention to it
in the beginning. But, while not ideal, it is not such a big deal to
keep it like this.
Thanks for your investigations!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-24 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 4:09 [PATCH v1 1/1] i2c: iproc: Add i2c repeated start capability Rayagonda Kokatanur
2019-08-12 17:33 ` Ray Jui
2019-08-29 20:41 ` Wolfram Sang
2019-08-30 12:56 ` Wolfram Sang
2019-08-30 18:35 ` Ray Jui
2019-08-31 9:49 ` Wolfram Sang
2019-09-03 23:11 ` Ray Jui
2019-09-04 21:37 ` Wolfram Sang
2019-09-24 17:23 ` Ray Jui
2019-09-24 18:57 ` Wolfram Sang [this message]
2019-09-24 22:23 ` Ray Jui
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=20190924185757.GA1538@kunai \
--to=wsa@the-dreams$(echo .)de \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=f.fainelli@gmail$(echo .)com \
--cc=icarus.chau@broadcom$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-i2c@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=lori.hikichi@broadcom$(echo .)com \
--cc=mark.rutland@arm$(echo .)com \
--cc=ray.jui@broadcom$(echo .)com \
--cc=rayagonda.kokatanur@broadcom$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=sshetty1@broadcom$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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