From: Marek Vasut <marex@denx.de>
To: Raviteja Narayanam <raviteja.narayanam@xilinx.com>,
linux-i2c@vger.kernel.org, michal.simek@xilinx.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, git@xilinx.com
Subject: Re: [PATCH 02/10] i2c: xiic: Add standard mode support for > 255 byte read transfers
Date: Wed, 2 Jun 2021 13:17:10 +0200 [thread overview]
Message-ID: <0f167c21-6bc7-0806-a536-55658a199a5b@denx.de> (raw)
In-Reply-To: <20210531131948.19477-3-raviteja.narayanam@xilinx.com>
On 5/31/21 3:19 PM, Raviteja Narayanam wrote:
[...]
> + if (i2c->dynamic) {
> + u8 bytes;
> + u16 val;
> +
> + /* Clear and enable Rx full interrupt. */
> + xiic_irq_clr_en(i2c, XIIC_INTR_RX_FULL_MASK |
> + XIIC_INTR_TX_ERROR_MASK);
> +
> + /*
> + * We want to get all but last byte, because the TX_ERROR IRQ
> + * is used to indicate error ACK on the address, and
> + * negative ack on the last received byte, so to not mix
> + * them receive all but last.
> + * In the case where there is only one byte to receive
> + * we can check if ERROR and RX full is set at the same time
> + */
> + rx_watermark = msg->len;
> + bytes = min_t(u8, rx_watermark, IIC_RX_FIFO_DEPTH);
> + bytes--;
> +
> + xiic_setreg8(i2c, XIIC_RFD_REG_OFFSET, bytes);
> +
> + local_irq_save(flags);
> + if (!(msg->flags & I2C_M_NOSTART))
> + /* write the address */
> + xiic_setreg16(i2c, XIIC_DTR_REG_OFFSET,
> + i2c_8bit_addr_from_msg(msg) |
> + XIIC_TX_DYN_START_MASK);
> +
> + xiic_irq_clr_en(i2c, XIIC_INTR_BNB_MASK);
> +
> + /* If last message, include dynamic stop bit with length */
> + val = (i2c->nmsgs == 1) ? XIIC_TX_DYN_STOP_MASK : 0;
> + val |= msg->len;
> +
> + xiic_setreg16(i2c, XIIC_DTR_REG_OFFSET, val);
> + local_irq_restore(flags);
Is local_irq_save()/local_irq_restore() used here to prevent concurrent
access to the XIIC ?
[...]
next prev parent reply other threads:[~2021-06-02 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 13:19 [PATCH 00/10] i2c: xiic: Add features, bug fixes Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 01/10] i2c: xiic: Fix Tx Interrupt path for grouped messages Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 02/10] i2c: xiic: Add standard mode support for > 255 byte read transfers Raviteja Narayanam
2021-06-02 11:17 ` Marek Vasut [this message]
2021-06-03 5:33 ` Raviteja Narayanam
2021-06-03 9:57 ` Marek Vasut
2021-06-08 9:46 ` Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 03/10] i2c: xiic: Fix coding style issues Raviteja Narayanam
2021-05-31 15:49 ` Joe Perches
2021-05-31 13:19 ` [PATCH 04/10] i2c: xiic: Add smbus_block_read functionality Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 05/10] i2c: xiic: Return value of xiic_reinit Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 06/10] i2c: xiic: Fix the type check for xiic_wakeup Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 07/10] i2c: xiic: Switch to Xiic standard mode for i2c-read Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 08/10] i2c: xiic: Remove interrupt enable/disable in Rx path Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 09/10] dt-bindings: i2c: xiic: Add 'xlnx,axi-iic-2.1' to compatible Raviteja Narayanam
2021-05-31 13:19 ` [PATCH 10/10] i2c: xiic: Update compatible with new IP version Raviteja Narayanam
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=0f167c21-6bc7-0806-a536-55658a199a5b@denx.de \
--to=marex@denx.de \
--cc=git@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=raviteja.narayanam@xilinx.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
all inboxes | Powered by JetHome®