| Message ID | 20201120073533.24486-1-peter.ujfalusi@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | arm64: dts: ti: k3-j7200-som/cpb: Correct i2c bus representations | expand |
On 20/11/2020 09:35, Peter Ujfalusi wrote: > Hi, > > Changes since v1: > - Added REviewed-by from Vignesh > - Comment block to explain main_i2c1 connection to CPB > > The main_i2c0 missed the ioexpander present on the SOM itself to control muxes > to route signals to CPB connectors. > > The main_i2c1 of J7200 is _not_ connected to the i2c1 of CPB, it is connected to > i2c3, so the devices on the CPB's i2c1 bus are not avalible, but the ones on the > CPB i2c3 are available under the main_i2c1. > > Add nice line names at the same time to these. > > Regards, > Peter > --- > Peter Ujfalusi (2): > arm64: dts: ti: k3-j7200-som-p0: main_i2c0 have an ioexpander on the > SOM > arm64: dts: ti: k3-j7200-common-proc-board: Correct the name of io > expander on main_i2c1 > > .../dts/ti/k3-j7200-common-proc-board.dts | 23 ++++++++-------- > arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 26 +++++++++++++++++++ > 2 files changed, 37 insertions(+), 12 deletions(-) > Thank you. Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
On Fri, 20 Nov 2020 09:35:31 +0200, Peter Ujfalusi wrote: > Changes since v1: > - Added REviewed-by from Vignesh > - Comment block to explain main_i2c1 connection to CPB > > The main_i2c0 missed the ioexpander present on the SOM itself to control muxes > to route signals to CPB connectors. > > [...] Hi Peter Ujfalusi, I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/2] arm64: dts: ti: k3-j7200-som-p0: main_i2c0 have an ioexpander on the SOM commit: b6633d778675a58fba1d7f795169da212a76231d [2/2] arm64: dts: ti: k3-j7200-common-proc-board: Correct the name of io expander on main_i2c1 commit: 2eefbf5f862ed98a043917fa54c7a79a56ec08f6 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
Hi, Changes since v1: - Added REviewed-by from Vignesh - Comment block to explain main_i2c1 connection to CPB The main_i2c0 missed the ioexpander present on the SOM itself to control muxes to route signals to CPB connectors. The main_i2c1 of J7200 is _not_ connected to the i2c1 of CPB, it is connected to i2c3, so the devices on the CPB's i2c1 bus are not avalible, but the ones on the CPB i2c3 are available under the main_i2c1. Add nice line names at the same time to these. Regards, Peter --- Peter Ujfalusi (2): arm64: dts: ti: k3-j7200-som-p0: main_i2c0 have an ioexpander on the SOM arm64: dts: ti: k3-j7200-common-proc-board: Correct the name of io expander on main_i2c1 .../dts/ti/k3-j7200-common-proc-board.dts | 23 ++++++++-------- arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 26 +++++++++++++++++++ 2 files changed, 37 insertions(+), 12 deletions(-)