linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Liguo Zhang <liguo.zhang@mediatek.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
	Xudong Chen <xudong.chen@mediatek.com>,
	srv_heupstream@mediatek.com,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	linux-i2c@vger.kernel.org,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Eddie Huang <eddie.huang@mediatek.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] i2c: mt8173: add 4GB mode support in i2c driver.
Date: Fri, 29 Jan 2016 17:50:53 +0800	[thread overview]
Message-ID: <1454061053.17366.4.camel@mtksdaap41> (raw)
In-Reply-To: <1454031331-9107-1-git-send-email-liguo.zhang@mediatek.com>

On Fri, 2016-01-29 at 09:35 +0800, Liguo Zhang wrote:
> If 4GB mode is enable, we should add 4gb mode support in i2c driver.

nit: enabled
However, after looking at it longer, the commit message doesn't make
much sense to me.

> Set 4GB mode register to support 4GB mode.
> 
> Signed-off-by: Liguo Zhang <liguo.zhang@mediatek.com>
> ---
> change in v3:
> Only inline the computation of reg_4g_mode in mtk_i2c_set_4g_mode().
> change in v2:
> Define a static inline funtion mtk_i2c_set_4g_mode() for support 4g mode.
> ---
>  drivers/i2c/busses/i2c-mt65xx.c | 42 +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 42 insertions(+)
> 
> diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drivers/i2c/busses/i2c-mt65xx.c
> index aec8e6c..3c484f0 100644
> --- a/drivers/i2c/busses/i2c-mt65xx.c
> +++ b/drivers/i2c/busses/i2c-mt65xx.c
> @@ -60,6 +60,7 @@
>  #define I2C_DMA_INT_FLAG_NONE		0x0000
>  #define I2C_DMA_CLR_FLAG		0x0000
>  #define I2C_DMA_HARD_RST		0x0002
> +#define I2C_DMA_4G_MODE			0x0001
>  
>  #define I2C_DEFAULT_SPEED		100000	/* hz */
>  #define MAX_FS_MODE_SPEED		400000
> @@ -88,6 +89,8 @@ enum DMA_REGS_OFFSET {
>  	OFFSET_RX_MEM_ADDR = 0x20,
>  	OFFSET_TX_LEN = 0x24,
>  	OFFSET_RX_LEN = 0x28,
> +	OFFSET_TX_4G_MODE = 0x54,
> +	OFFSET_RX_4G_MODE = 0x58,
>  };
>  
>  enum i2c_trans_st_rs {
> @@ -133,6 +136,7 @@ struct mtk_i2c_compatible {
>  	unsigned char dcm: 1;
>  	unsigned char auto_restart: 1;
>  	unsigned char aux_len_reg: 1;
> +	unsigned char support_33bits: 1;
>  };
>  
>  struct mtk_i2c {
> @@ -182,6 +186,7 @@ static const struct mtk_i2c_compatible mt6577_compat = {
>  	.dcm = 1,
>  	.auto_restart = 0,
>  	.aux_len_reg = 0,
> +	.support_33bits = 0,
>  };
>  
>  static const struct mtk_i2c_compatible mt6589_compat = {
> @@ -190,6 +195,7 @@ static const struct mtk_i2c_compatible mt6589_compat = {
>  	.dcm = 0,
>  	.auto_restart = 0,
>  	.aux_len_reg = 0,
> +	.support_33bits = 0,
>  };
>  
>  static const struct mtk_i2c_compatible mt8173_compat = {
> @@ -198,6 +204,7 @@ static const struct mtk_i2c_compatible mt8173_compat = {
>  	.dcm = 1,
>  	.auto_restart = 1,
>  	.aux_len_reg = 1,
> +	.support_33bits = 1,
>  };
>  
>  static const struct of_device_id mtk_i2c_of_match[] = {
> @@ -366,6 +373,11 @@ static int mtk_i2c_set_speed(struct mtk_i2c *i2c, unsigned int parent_clk,
>  	return 0;
>  }
>  
> +static inline u32 mtk_i2c_set_4g_mode(dma_addr_t addr)
> +{
> +	return (addr & BIT(32)) ? I2C_DMA_4G_MODE : I2C_DMA_CLR_FLAG;
> +}
> +

#define BIT(nr)			(1UL << (nr))
#define BIT_ULL(nr)		(1ULL << (nr))

#define DMA_BIT_MASK(n)	(((n) == 64) ? ~0ULL : ((1ULL<<(n))-1))


I think you should use BIT_ULL.


>  static int mtk_i2c_do_transfer(struct mtk_i2c *i2c, struct i2c_msg *msgs,
>  			       int num, int left_num)
>  {
> @@ -373,6 +385,7 @@ static int mtk_i2c_do_transfer(struct mtk_i2c *i2c, struct i2c_msg *msgs,
>  	u16 start_reg;
>  	u16 control_reg;
>  	u16 restart_flag = 0;
> +	u32 reg_4g_mode = 0;


unnecessary init.

Joe.C

  parent reply	other threads:[~2016-01-29  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  1:35 [PATCH v3] i2c: mt8173: add 4GB mode support in i2c driver Liguo Zhang
2016-01-29  9:48 ` Daniel Kurtz
2016-01-29  9:50 ` Yingjoe Chen [this message]
2016-01-29  9:58 ` kbuild test robot
2016-01-29 10:23 ` kbuild test robot

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=1454061053.17366.4.camel@mtksdaap41 \
    --to=yingjoe.chen@mediatek.com \
    --cc=eddie.huang@mediatek.com \
    --cc=liguo.zhang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=s.hauer@pengutronix.de \
    --cc=srv_heupstream@mediatek.com \
    --cc=wsa@the-dreams.de \
    --cc=xudong.chen@mediatek.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).