From: eddie.huang@mediatek.com (Eddie Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 3/3] I2C: mediatek: Add driver for MediaTek MT8173 I2C controller
Date: Mon, 30 Mar 2015 16:05:19 +0800 [thread overview]
Message-ID: <1427702719.26464.5.camel@mtksdaap41> (raw)
In-Reply-To: <20150323073905.GF9742@pengutronix.de>
Hi Sascha,
On Mon, 2015-03-23 at 08:39 +0100, Sascha Hauer wrote:
> On Sat, Mar 21, 2015 at 02:05:22PM +0800, Eddie Huang wrote:
> > Add mediatek MT8173 I2C controller driver. Compare to I2C controller
> > of earlier mediatek SoC, MT8173 fix write-then-read limitation, and
> > also increase message size to 64kb.
> >
>
> [...]
>
> > +static const struct i2c_adapter_quirks mt8173_i2c_quirks = {
> > + .max_num_msgs = MAX_MSG_NUM_MT8173,
> > + .max_write_len = MAX_DMA_TRANS_SIZE_MT8173,
> > + .max_read_len = MAX_DMA_TRANS_SIZE_MT8173,
> > + .max_comb_1st_msg_len = MAX_DMA_TRANS_SIZE_MT8173,
> > + .max_comb_2nd_msg_len = MAX_WRRD_TRANS_SIZE_MT8173,
> > +};
> > +
> > static int mtk_i2c_probe(struct platform_device *pdev)
> > {
> > int ret = 0;
> > @@ -587,7 +626,8 @@ static int mtk_i2c_probe(struct platform_device *pdev)
> > return -EINVAL;
> >
> > i2c->platform_compat = mtk_get_device_prop(pdev);
> > - if (i2c->have_pmic && (i2c->platform_compat & COMPAT_MT6577))
> > + if (i2c->have_pmic && (i2c->platform_compat &
> > + (COMPAT_MT6577 | COMPAT_MT8173)))
> > return -EINVAL;
> >
> > res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > @@ -613,7 +653,10 @@ static int mtk_i2c_probe(struct platform_device *pdev)
> > i2c->adap.dev.parent = &pdev->dev;
> > i2c->adap.owner = THIS_MODULE;
> > i2c->adap.algo = &mtk_i2c_algorithm;
> > - i2c->adap.quirks = &mt6577_i2c_quirks;
> > + if (i2c->platform_compat & COMPAT_MT8173)
> > + i2c->adap.quirks = &mt8173_i2c_quirks;
> > + else
> > + i2c->adap.quirks = &mt6577_i2c_quirks;
>
> Instead of putting an integer into struct of_device_id you should
> introduce a
>
> struct mtk_i2c_data {
> struct i2c_adapter_quirks quirks;
> int compat;
> /* Additional SoC specific data */
> };
>
> and put a pointer to this directly into the of_device_id. This way you
> need less casting and can put newly discovered differences diretly into
> some data struct and don't have to introduce if(socxy) ... else ...
> everytime.
>
Thanks your suggestion. I will use capability struct like
struct mtk_i2c_compatible {
unsigned char pmic_i2c;
unsigned char dcm;
unsigned char auto_restart;
const struct i2c_adapter_quirks *quirks;
};
And pass in of_device_id, then remove all if(socxy).... else ... in
driver.
Eddie
prev parent reply other threads:[~2015-03-30 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 6:05 [PATCH v5 0/3] ARM: mediatek: Add driver for Mediatek I2C controller Eddie Huang
2015-03-21 6:05 ` [PATCH v5 1/3] dt-bindings: Add I2C bindings for mt65xx/mt81xx Eddie Huang
2015-03-23 8:45 ` Sascha Hauer
2015-03-21 6:05 ` [PATCH v5 2/3] I2C: mediatek: Add driver for MediaTek I2C controller Eddie Huang
2015-03-23 8:42 ` Sascha Hauer
2015-03-30 8:14 ` Eddie Huang
2015-03-30 17:23 ` Sascha Hauer
2015-03-31 7:08 ` Eddie Huang
2015-03-31 11:50 ` Eddie Huang
2015-03-31 17:52 ` Sascha Hauer
2015-04-01 2:11 ` Eddie Huang
2015-03-21 6:05 ` [PATCH v5 3/3] I2C: mediatek: Add driver for MediaTek MT8173 " Eddie Huang
2015-03-23 7:39 ` Sascha Hauer
2015-03-30 8:05 ` Eddie Huang [this message]
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=1427702719.26464.5.camel@mtksdaap41 \
--to=eddie.huang@mediatek.com \
--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