linux-kernel - Re: [PATCH] Devicetree binding for omap3-serial & bcm2048 combination

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]

Date:	Wed, 28 Jan 2015 23:35:10 +0100
From:	Sebastian Reichel <sre@...nel.org>
To:	Pavel Machek <pavel@....cz>
Cc:	robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	marcel@...tmann.org
Subject: Re: [PATCH] Devicetree binding for omap3-serial & bcm2048 combination

Hi,

On Wed, Jan 28, 2015 at 10:35:01AM +0100, Pavel Machek wrote:
> Nokia N900 contains bluetooth module connected on serial
> port. Unfortunately, serial and bluetooth are rather closely coupled,
> so standard serial driver can not be used, and we really don't want
> /dev/ttyS1 to be published for internal port of bluetooth
> stack... Hence solution below.

Actually that's not true. If one takes a deeper look into Nokia's
bcm2048 driver one can see, that it's using more or less the same
protocol as other bluetooth modules (H4) with some custom
extensions. The only special thing are two additional GPIOs, which
are enabled before sending data, so that the bluetooth chip and the
omap can wakeup each other. I don't think one can speak of "closely
coupled" for this.

The only reason you needed this hacked DT binding is, that you do
not want to properly fix the bcm2048 driver, so that it can use the
omap-serial driver.

-- Sebastian

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)