linux-kernel - Re: [PATCH v5 2/2] i2c: sunxi: add P2WI (Push/Pull 2 Wire Interface) controller support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6454089.IP8IFVsofj@wuerfel>
Date:	Tue, 10 Jun 2014 15:54:56 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Boris BREZILLON <boris.brezillon@...e-electrons.com>
Cc:	Wolfram Sang <wsa@...-dreams.de>,
	Randy Dunlap <rdunlap@...radead.org>,
	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Hans de Goede <hdegoede@...hat.com>,
	Shuge <shuge@...winnertech.com>, kevin@...winnertech.com,
	devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-i2c@...r.kernel.org
Subject: Re: [PATCH v5 2/2] i2c: sunxi: add P2WI (Push/Pull 2 Wire Interface) controller support

On Tuesday 10 June 2014 15:47:16 Boris BREZILLON wrote:
> 
> +config I2C_SUN6I_P2WI
> +       tristate "Allwinner sun6i internal P2WI controller"
> +       depends on ARCH_SUNXI
> +       help
> +         If you say yes to this option, support will be included for the
> +         P2WI (Push/Pull 2 Wire Interface) controller embedded in some sunxi
> +         SOCs.
> +         The P2WI looks like an SMBus controller (which supports only byte
> +         accesses), except that it only supports one slave device.
> +         This interface is used to connect to specific PMIC devices (like the
> +         AXP221).
> +

Sorry for the stupid question, but why is this an i2c driver if the
hardware protocol is completely different?

I understand that a lot of devices can be driven using either spi or
i2c, and we have two sets of {directories,maintainers,bus_types,...}
for them. Your description sounds like this is a separate option
that isn't any closer to i2c than it is to spi.

Would it perhaps be better to expose it only as a regmap rather than
an i2c host?

	Arnd
--
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/