i2c client的adapter如何生成

先来看下i2c transfer函数，如下：

ret = i2c_transfer(client->adapter, &msg, 1);

其中重要的参数是client->adapter，今天想了解下这个adapter是在哪里生成的。

上个文章说的是设备驱动的注册过程，今天来看看i2c控制器驱动的注册过程。

首先在dts里配置

	i2c0: i2c@11007000 {
		compatible = "mediatek,mt6771-i2c";
		id = <0>;
		reg = <0 0x11007000 0 0x1000>,
			<0 0x11000080 0 0x80>;
		interrupts = <GIC_SPI 81 IRQ_TYPE_LEVEL_LOW>;
		clocks = <&infracfg_ao INFRACFG_AO_I2C0_CG>,
			 <&infracfg_ao INFRACFG_AO_AP_DMA_CG>;
		clock-names = "main", "dma";
		clock-div = <5>;
		mediatek,hs_only;
		mediatek,skip_scp_sema;
	};

	i2c1: i2c@11011000 {
		compatible = "mediatek,mt6771-i2c";
		id = <1>;
		reg = <0 0x11011000 0 0x1000>,
			<0 0x11000480 0 0x80>;
		interrupts = <GIC_SPI 85 IRQ_TYPE_LEVEL_LOW>;
		clocks = <&infracfg_ao INFRACFG_AO_I2C4_CG>,
			 <&infracfg_ao INFRACFG_AO_AP_DMA_CG>;
		clock-names = "main", "dma";
		clock-div = <5>;
		mediatek,hs_only;
		mediatek,skip_scp_sema;
	};
.....
.....
.....
.....
.....
.....
	i2c11: i2c@11016000 {
		compatible = "mediatek,mt6771-i2c";
		id = <11>;
		reg = <0 0x11016000 0 0x1000>,
			<0 0x11000500 0 0x80>;
		interrupts = <GIC_SPI 86 IRQ_TYPE_LEVEL_LOW>;
		clocks = <&infracfg_ao INFRACFG_AO_I2C5_CG>,
			 <&infracfg_ao INFRACFG_AO_AP_DMA_CG>,
			 <&infracfg_ao INFRACFG_AO_I2C5_ARBITER_CG>;
		clock-names = "main", "dma", "arb";
		clock-div = <5>;
		mediatek,hs_only;
	};

从dts里可以看到i2c控制器有12个，也就是有12路i2c，先从驱动的probe看起，

static const struct of_device_id mtk_i2c_of_match[] = {
	{ .compatible = "mediatek,mt6775-i2c", .data = &mt6775_compat },
	{ .compatible = "mediatek,mt6771-i2c", .data = &mt6771_compat },
	{ .compatible = "mediatek,mt6735-i2c", .data = &mt6735_compat },
	{ .compatible = "mediatek,mt6739-i2c", .data = &mt6739_compat },
	{ .compatible = "mediatek,mt6797-i2c", .data = &mt6797_compat },
	{ .compatible = "mediatek,mt6757-i2c", .data = &mt6757_compat },
	{ .compatible = "mediatek,mt6758-i2c", .data = &mt6758_compat },
	{ .compatible = "mediatek,mt6759-i2c", .data = &mt6759_compat },
	{ .compatible = "mediatek,mt6799-i2c", .data = &mt6799_compat },
	{ .compatible = "mediatek,mt6763-i2c", .data = &mt6763_compat },
	{ .compatible = "mediatek,elbrus-i2c", .data = &elbrus_compat },
	{},
};

MODULE_DEVICE_TABLE(of, mtk_i2c_of_match);

static struct platform_driver mt_i2c_driver = {
	.probe = mt_i2c_probe,
	.remove = mt_i2c_remove,
	.driver = {
		.name = I2C_DRV_NAME,
		.owner = THIS_MODULE,
		.pm = &mt_i2c_dev_pm_ops,
		.of_match_table = of_match_ptr(mtk_i2c_of_match),
	},
};

i2c 控制器driver作为platform_driver注册到系统中，从dts里可以看到i2c控制器一共有12路compatible name 为mediatek,mt6771-i2c的node，

那么mt_i2c_probe会调用12次来填充没路i2c的数据结构i2c_client, 

主要的code在这里其中会循环调用__driver_attach(),并最终调用设备的驱动probe，具体细节和设备driver注册过程一样， 这部分是通用的。

int bus_for_each_dev(struct bus_type *bus, struct device *start,
		     void *data, int (*fn)(struct device *, void *))
    |
    |
    |
	while ((dev = next_device(&i)) && !error)
		error = fn(dev, data);

fn = __driver_attach;

再后面就是调用设备驱动的probe，也就是上面的mt_i2c_probe，其实这部分是总线驱动的公共部分，spi i2c platform等驱动在调用设备驱动的probe函数之前都会经过这个过程。

mt_i2c_probe（）里主要填充了如下数据结构：

struct mt_i2c {
	struct i2c_adapter adap;	/* i2c host adapter */
	struct device *dev;
	wait_queue_head_t wait;		/* i2c transfer wait queue */
	/* set in i2c probe */
	void __iomem *base;		/* i2c base addr */
	void __iomem *pdmabase;		/* dma base address*/
	int irqnr;			/* i2c interrupt number */
	int id;
	struct i2c_dma_buf dma_buf;	/* memory alloc for DMA mode */
	struct clk *clk_main;		/* main clock for i2c bus */
	struct clk *clk_dma;		/* DMA clock for i2c via DMA */
	struct clk *clk_pmic;		/* PMIC clock for i2c from PMIC */
	struct clk *clk_arb;		/* Arbitrator clock for i2c */
	
	bool have_ccu;
	u32 ccu_offset;
	unsigned long main_clk;
};

其中，今天主要说的东西也在这个函数出现，

ret = i2c_add_numbered_adapter(&i2c->adap);

到这里每路i2c控制器都有自己的adapter，Device Tree中的I2C client会透过I2C host驱动的probe()函数中调用of_i2c_register_devices(&i2c_dev->adapter);被自动展开。device driver 分配i2c_client对象时，就是找对用的i2c--x 来获取对应总线上的adapter。i2c adapter 里可以找到对应的i2c具体的传输数据的接口xfer 等