lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAK7LNATzgOZp542rd-92YXDxux2DrAOH_mkzk8NjimQ3afrCCg@mail.gmail.com> Date: Fri, 16 Oct 2015 14:24:30 +0900 From: Masahiro Yamada <yamada.masahiro@...ionext.com> To: Arnd Bergmann <arnd@...db.de> Cc: linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, arm@...nel.org, Russell King <linux@....linux.org.uk>, devicetree@...r.kernel.org, Kumar Gala <galak@...eaurora.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Ian Campbell <ijc+devicetree@...lion.org.uk>, Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>, Mark Rutland <mark.rutland@....com> Subject: Re: [PATCH 2/3] ARM: dts: uniphier: add ProXstream2 Vodka board support Hi Arnd, 2015-10-16 0:17 GMT+09:00 Arnd Bergmann <arnd@...db.de>: > On Thursday 15 October 2015 18:05:33 Masahiro Yamada wrote: >> + aliases { >> + serial0 = &serial0; >> + serial1 = &serial1; >> + serial2 = &serial2; >> + i2c0 = &i2c0; >> + i2c4 = &i2c4; >> + i2c5 = &i2c5; >> + i2c6 = &i2c6; >> > > This looks like a typo, you probably mean > > i2c0 = &i2c0; > i2c1 = &i2c4; > i2c2 = &i2c5; > i2c3 = &i2c6; > > Can you re-send this? > No, it is not a typo, but intentional. i2c0 - i2c3 are connected to the pads of the SoC package. On the other hand, i2c-4 - i2c-6 are connected to internal devices inside the SoC package. i2c-4 - i2c-6 are always connected to the same hardware devices and always used for the same purpose. My expected scenario is: [1] i2c0 - i2c3 are connected to the on-board devices depending on board variants. On some boards, their status is "okay" and on some boards, their status is "disabled". [2] i2c4 - i2c6 are always used to communicate with in-package devices. The status is always "okay". [3] Some user-land applications may want to have access through the same character devices, /dev/i2c4, /dev/i2c5, /dev/i2c6 If your way is adopted, the real hardware "i2c4" might be aligned to /dev/i2c1 on some boards, and /dev/i2c2 on others, etc. -- Best Regards Masahiro Yamada -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists