linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Mantravadi Karthik <mkarthik@nvidia.com>,
	Shardar Mohammed <smohammed@nvidia.com>,
	Timo Alho <talho@nvidia.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: RE: [PATCH V2 2/4] i2c: tegra: Update I2C transfer using buffer
Date: Fri, 25 Jan 2019 20:20:36 +0000	[thread overview]
Message-ID: <BYAPR12MB33982FC612F99AC5CAE29EDBC29B0@BYAPR12MB3398.namprd12.prod.outlook.com> (raw)
In-Reply-To: <185da588-1080-1589-46b6-5b63dff681eb@gmail.com>



> > This patch prepares the buffer with the message bytes to be 
> > transmitted along with the packet header information and then performs 
> > i2c transfer in PIO mode.
> > 
> > Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
> > ---
> >  [V2] : DMA support changes include preparing buffer with message bytes and
> > 	and header before sending them through DMA. So splitted the whole
> > 	change into 2 seperate patches in this series.
> > 
> >  drivers/i2c/busses/i2c-tegra.c | 97 
> > +++++++++++++++++++++++++++++-------------
> >  1 file changed, 68 insertions(+), 29 deletions(-)
> > 
> > diff --git a/drivers/i2c/busses/i2c-tegra.c 
> > b/drivers/i2c/busses/i2c-tegra.c index ef854be4c837..13bce1411ddc 
> > 100644
> > --- a/drivers/i2c/busses/i2c-tegra.c
> > +++ b/drivers/i2c/busses/i2c-tegra.c
> > @@ -117,6 +117,9 @@
> >  #define I2C_MST_FIFO_STATUS_TX_MASK		0xff0000
> >  #define I2C_MST_FIFO_STATUS_TX_SHIFT		16
> >  
> > +/* Packet header size in bytes */
> > +#define I2C_PACKET_HEADER_SIZE			12
> > +
> >  /*
> >   * msg_end_type: The bus control which need to be send at end of transfer.
> >   * @MSG_END_STOP: Send stop pulse at end of transfer.
> > @@ -677,35 +680,69 @@ static irqreturn_t tegra_i2c_isr(int irq, void *dev_id)
> >  	return IRQ_HANDLED;
> >  }
> >  
> > +static int tegra_i2c_start_pio_xfer(struct tegra_i2c_dev *i2c_dev) {
> > +	u32 *buffer = (u32 *)i2c_dev->msg_buf;
> > +	unsigned long flags;
> > +	u32 int_mask;
> > +
> > +	spin_lock_irqsave(&i2c_dev->xfer_lock, flags);
> > +
> > +	int_mask = I2C_INT_NO_ACK | I2C_INT_ARBITRATION_LOST;
> > +	tegra_i2c_unmask_irq(i2c_dev, int_mask);
> > +
> > +	i2c_writel(i2c_dev, *(buffer++), I2C_TX_FIFO);
> > +	i2c_writel(i2c_dev, *(buffer++), I2C_TX_FIFO);
> > +	i2c_writel(i2c_dev, *(buffer++), I2C_TX_FIFO);
> > +
> > +	i2c_dev->msg_buf = (u8 *) buffer;
> > +
> > +	if (!i2c_dev->msg_read)
> > +		tegra_i2c_fill_tx_fifo(i2c_dev);
> > +
> > +	if (i2c_dev->hw->has_per_pkt_xfer_complete_irq)
> > +		int_mask |= I2C_INT_PACKET_XFER_COMPLETE;
> > +	if (i2c_dev->msg_read)
> > +		int_mask |= I2C_INT_RX_FIFO_DATA_REQ;
> > +	else if (i2c_dev->msg_buf_remaining)
> > +		int_mask |= I2C_INT_TX_FIFO_DATA_REQ;
> > +
> > +	tegra_i2c_unmask_irq(i2c_dev, int_mask);
> > +	spin_unlock_irqrestore(&i2c_dev->xfer_lock, flags);
> > +	dev_dbg(i2c_dev->dev, "unmasked irq: %02x\n",
> > +		i2c_readl(i2c_dev, I2C_INT_MASK));
> > +
> > +	return 0;
> > +}
> > +
> >  static int tegra_i2c_xfer_msg(struct tegra_i2c_dev *i2c_dev,
> >  	struct i2c_msg *msg, enum msg_end_type end_state)  {
> >  	u32 packet_header;
> >  	u32 int_mask;
> >  	unsigned long time_left;
> > -	unsigned long flags;
> > +	u32 *buffer;
> > +	int ret = 0;
> > +
> > +	buffer = kmalloc(ALIGN(msg->len, BYTES_PER_FIFO_WORD) +
> > +					I2C_PACKET_HEADER_SIZE, GFP_KERNEL);
> > +	if (!buffer)
> > +		return -ENOMEM;
>
> Isn't it possible to avoid "buffer" allocation / copying overhead and keep code as-is for the PIO mode?
>

Keeping PIO mode code as is and adding DMA mode will have redundant code for header generation and msg complete timeout sections.
Also in existing PIO mode implementation, TX FIFO is filled as soon as the word is ready but for DMA mode need to put all msg bytes along with header together to send thru DMA.
So created common buffer to perform PIO/DMA to reduce redundancy.

  reply	other threads:[~2019-01-25 20:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 20:51 [PATCH V2 1/4] i2c: tegra: Sort all the include headers alphabetically Sowjanya Komatineni
2019-01-24 20:51 ` [PATCH V2 2/4] i2c: tegra: Update I2C transfer using buffer Sowjanya Komatineni
2019-01-25 19:55   ` Dmitry Osipenko
2019-01-25 20:20     ` Sowjanya Komatineni [this message]
2019-01-25 21:25       ` Dmitry Osipenko
2019-01-25 23:22         ` Dmitry Osipenko
2019-01-25 23:26           ` Sowjanya Komatineni
2019-01-24 20:51 ` [PATCH V2 3/4] i2c: tegra: Add DMA Support Sowjanya Komatineni
2019-01-25 19:34   ` Dmitry Osipenko
2019-01-25 20:31     ` Sowjanya Komatineni
2019-01-25 20:40       ` Dmitry Osipenko
2019-01-25 21:11         ` Sowjanya Komatineni
2019-01-25 21:49           ` Dmitry Osipenko
2019-01-25 22:09             ` Dmitry Osipenko
2019-01-25 22:22             ` Sowjanya Komatineni
2019-01-25 23:10           ` Thierry Reding
2019-01-25 23:29             ` Sowjanya Komatineni
2019-01-25 22:03   ` Dmitry Osipenko
2019-01-25 22:35   ` Dmitry Osipenko
2019-01-26  0:28   ` Dmitry Osipenko
2019-01-26  0:49     ` Dmitry Osipenko
2019-01-26  1:51     ` Sowjanya Komatineni
2019-01-24 20:51 ` [PATCH V2 4/4] i2c: tegra: Update transfer timeout Sowjanya Komatineni
2019-01-24 21:31 ` [PATCH V2 1/4] i2c: tegra: Sort all the include headers alphabetically Dmitry Osipenko

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=BYAPR12MB33982FC612F99AC5CAE29EDBC29B0@BYAPR12MB3398.namprd12.prod.outlook.com \
    --to=skomatineni@nvidia.com \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkarthik@nvidia.com \
    --cc=smohammed@nvidia.com \
    --cc=talho@nvidia.com \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).