LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Eddie James <eajames@linux.vnet.ibm.com> To: Wolfram Sang <wsa@the-dreams.de> Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, benh@kernel.crashing.org, joel@jms.id.au, mark.rutland@arm.com, gregkh@linuxfoundation.org, rdunlap@infradead.org, andy.shevchenko@gmail.com, peda@axentia.se Subject: Re: [PATCH v10 5/7] i2c: fsi: Add transfer implementation Date: Thu, 5 Jul 2018 13:52:13 -0500 [thread overview] Message-ID: <ab5a5b9c-931e-e8ca-d064-92a917e00a3b@linux.vnet.ibm.com> (raw) In-Reply-To: <20180702182434.5wxxszpgpf6wergl@ninjato> On 07/02/2018 01:24 PM, Wolfram Sang wrote: >>>> + if (msg->flags & I2C_M_RD) >>>> + cmd |= I2C_CMD_READ; >>> Since you support MANGLING, I'd think you can easily support >>> I2C_M_REV_DIR_ADDR here, too? >> Hm, I don't really understand the purpose of that flag. From the docs: >> >> This toggles the Rd/Wr flag. That is, if you want to do a write, but >> need to emit an Rd instead of a Wr, or vice versa, you set this >> flag. For example: >> S Addr Rd [A] Data [A] Data [A] ... [A] Data [A] P >> >> I don't think our hardware supports this type of operation. > I'd think something like this should do: > > if (msg->flags & I2C_M_REV_DIR_ADDR) > cmd ^= I2C_CMD_READ; I meant that the hardware cannot interpret this, it would be a meaningless command unfortunately. >
next prev parent reply other threads:[~2018-07-05 18:53 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-13 19:36 [PATCH v10 0/7] i2c: Add FSI-attached I2C master algorithm Eddie James 2018-06-13 19:36 ` [PATCH v10 1/7] dt-bindings: i2c: Add FSI-attached I2C master dt binding documentation Eddie James 2018-06-26 2:39 ` Wolfram Sang 2018-06-13 19:36 ` [PATCH v10 2/7] i2c: Add FSI-attached I2C master algorithm Eddie James 2018-06-13 19:36 ` [PATCH v10 3/7] i2c: fsi: Add port structures Eddie James 2018-06-20 3:34 ` Benjamin Herrenschmidt 2018-06-20 3:59 ` Joel Stanley 2018-06-13 19:36 ` [PATCH v10 4/7] i2c: fsi: Add abort and hardware reset procedures Eddie James 2018-06-26 2:38 ` Wolfram Sang 2018-06-27 13:48 ` Eddie James 2018-07-02 18:15 ` Wolfram Sang 2018-07-05 18:50 ` Eddie James 2018-07-05 22:06 ` Wolfram Sang 2018-06-13 19:36 ` [PATCH v10 5/7] i2c: fsi: Add transfer implementation Eddie James 2018-06-26 2:38 ` Wolfram Sang 2018-06-27 13:21 ` Eddie James 2018-07-02 18:24 ` Wolfram Sang 2018-07-05 18:52 ` Eddie James [this message] 2018-07-05 21:59 ` Wolfram Sang 2018-06-13 19:36 ` [PATCH v10 6/7] i2c: fsi: Add I2C master locking Eddie James 2018-06-13 19:36 ` [PATCH v10 7/7] i2c: fsi: Add bus recovery Eddie James 2018-06-26 2:38 ` Wolfram Sang 2018-06-27 13:32 ` Eddie James 2018-07-02 18:16 ` Wolfram Sang 2018-06-14 9:05 ` [PATCH v10 0/7] i2c: Add FSI-attached I2C master algorithm Andy Shevchenko 2018-06-18 4:53 ` Joel Stanley 2018-06-26 2:39 ` Wolfram Sang 2018-06-27 13:53 ` Eddie James
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=ab5a5b9c-931e-e8ca-d064-92a917e00a3b@linux.vnet.ibm.com \ --to=eajames@linux.vnet.ibm.com \ --cc=andy.shevchenko@gmail.com \ --cc=benh@kernel.crashing.org \ --cc=devicetree@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=joel@jms.id.au \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=peda@axentia.se \ --cc=rdunlap@infradead.org \ --cc=robh+dt@kernel.org \ --cc=wsa@the-dreams.de \ /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: linkBe 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).