From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] I2C: mediatek: Add driver for MediaTek I2C controller
Date: Wed, 21 Jan 2015 09:20:22 +0100 [thread overview]
Message-ID: <20150121082022.GT22880@pengutronix.de> (raw)
In-Reply-To: <1421810004.15468.825.camel@mtksdaap41>
Hello,
On Wed, Jan 21, 2015 at 11:13:24AM +0800, Eddie Huang wrote:
> > > + /* set when doing the transfer */
> > > + u16 irq_stat; /* interrupt status */
> > > + unsigned int speed_hz; /* The speed in transfer */
> > > + bool trans_stop; /* i2c transfer stop */
> > > + enum mtk_trans_op op;
> > > + u16 msg_len;
> > > + u8 *msg_buf; /* pointer to msg data */
> > > + u16 msg_aux_len; /* WRRD mode to set AUX_LEN register*/
> > > + u16 addr; /* 7bit slave address, without read/write bit */
> > Wouldn't it be easier to maintain a pointer to the message to be
> > transferred?
> I think use mtk_i2c pointer is more flexible than maintain a pointer to
> message.
Not sure you understood what I intended to suggest. My idea was to drop
u16 msg_len;
u8 *msg_buf;
u16 msg_aux_len; // maybe
u16 addr;
from struct mtk_i2c and add a struct i2c_msg *msg instead. Up to you to
decide.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-01-21 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 10:33 [PATCH v4 0/2] ARM: mediatek: Add driver for Mediatek I2C controller Eddie Huang
2015-01-16 10:33 ` [PATCH v4 1/2] dt-bindings: Add I2C bindings for mt65xx/mt81xx Eddie Huang
2015-01-16 10:33 ` [PATCH v4 2/2] I2C: mediatek: Add driver for MediaTek I2C controller Eddie Huang
2015-01-18 10:18 ` Uwe Kleine-König
2015-01-21 3:13 ` Eddie Huang
2015-01-21 6:30 ` Yingjoe Chen
2015-01-21 8:15 ` Uwe Kleine-König
2015-01-21 12:49 ` Yingjoe Chen
2015-01-21 15:31 ` Uwe Kleine-König
2015-01-22 1:30 ` Yingjoe Chen
2015-01-21 8:20 ` Uwe Kleine-König [this message]
2015-01-21 8:34 ` Eddie Huang
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=20150121082022.GT22880@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).