All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Hugo Villeneuve <hvilleneuve@dimonoff.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp-evk: add support for I2C5
Date: Mon, 21 Feb 2022 11:20:46 +0800	[thread overview]
Message-ID: <20220221032046.GG2249@dragon> (raw)
In-Reply-To: <20220211153843.3721618-1-hugo@hugovil.com>

On Fri, Feb 11, 2022 at 10:38:43AM -0500, Hugo Villeneuve wrote:
> From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> 
> Add support for i2c5, which is used to access the
> external I2C bus on connector J22 of the imx8mp-evk.
> 
> Limit the speed to 100kHz since this is an external I2C bus.
> 
> Disabled by default, since it is shared with the CAN1 bus.
> 
> To enable i2c5, you need to disable the CAN1 function, enable the i2c5
> function and also configure the CAN1/I2C5_SEL GPIO to HIGH to
> select i2c5 instead of CAN1. This can be done by defining a gpio-hog
> inside the pca6416 node, in your board device tree, like in this example:
> 
> &flexcan1 {
> 	status = "disabled";
> };
> 
> &i2c5 {
> 	status = "okay";
> };
> 
> &pca6416 {
> 	can1-i2c5-sel-hog {
> 		gpio-hog;
> 		gpios = <2 GPIO_ACTIVE_HIGH>;
> 		output-high;
> 		line-name = "can1-i2c5-sel";
> 	};
> };
> 
> Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>

Applied, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Hugo Villeneuve <hugo@hugovil.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Hugo Villeneuve <hvilleneuve@dimonoff.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8mp-evk: add support for I2C5
Date: Mon, 21 Feb 2022 11:20:46 +0800	[thread overview]
Message-ID: <20220221032046.GG2249@dragon> (raw)
In-Reply-To: <20220211153843.3721618-1-hugo@hugovil.com>

On Fri, Feb 11, 2022 at 10:38:43AM -0500, Hugo Villeneuve wrote:
> From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> 
> Add support for i2c5, which is used to access the
> external I2C bus on connector J22 of the imx8mp-evk.
> 
> Limit the speed to 100kHz since this is an external I2C bus.
> 
> Disabled by default, since it is shared with the CAN1 bus.
> 
> To enable i2c5, you need to disable the CAN1 function, enable the i2c5
> function and also configure the CAN1/I2C5_SEL GPIO to HIGH to
> select i2c5 instead of CAN1. This can be done by defining a gpio-hog
> inside the pca6416 node, in your board device tree, like in this example:
> 
> &flexcan1 {
> 	status = "disabled";
> };
> 
> &i2c5 {
> 	status = "okay";
> };
> 
> &pca6416 {
> 	can1-i2c5-sel-hog {
> 		gpio-hog;
> 		gpios = <2 GPIO_ACTIVE_HIGH>;
> 		output-high;
> 		line-name = "can1-i2c5-sel";
> 	};
> };
> 
> Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>

Applied, thanks!

  reply	other threads:[~2022-02-21  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 15:38 [PATCH] arm64: dts: imx8mp-evk: add support for I2C5 Hugo Villeneuve
2022-02-11 15:38 ` Hugo Villeneuve
2022-02-21  3:20 ` Shawn Guo [this message]
2022-02-21  3:20   ` Shawn Guo

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=20220221032046.GG2249@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=hugo@hugovil.com \
    --cc=hvilleneuve@dimonoff.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.