linux-kernel - Re: [PATCHv3] ASoC: Add support for BCM2835

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:	Mon, 18 Nov 2013 15:25:26 +0100
From:	Florian Meier <florian.meier@...lo.de>
To:	Mark Rutland <mark.rutland@....com>
CC:	Liam Girdwood <lgirdwood@...il.com>,
	Mark Brown <broonie@...nel.org>,
	Stephen Warren <swarren@...dotorg.org>,
	Lars-Peter Clausen <lars@...afoo.de>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	linux-rpi-kernel <linux-rpi-kernel@...ts.infradead.org>,
	devicetree <devicetree@...r.kernel.org>,
	dmaengine <dmaengine@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCHv3] ASoC: Add support for BCM2835

Thank you!

>> diff --git a/Documentation/devicetree/bindings/sound/bcm2835-i2s.txt b/Documentation/devicetree/bindings/sound/bcm2835-i2s.txt
>> new file mode 100644
>> index 0000000..7bf1d04
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/sound/bcm2835-i2s.txt
>> @@ -0,0 +1,22 @@
>> +* Broadcom BCM2835 SoC I2S/PCM module
>> +
>> +Required properties:
>> +- compatible: "brcm,bcm2835-i2s"
>> +- reg: Register location and size
>> +       <PCM base address, size
>> +        PCM clock base address, size>;
> 
> []
> 
> Are the clocks actually a sub-block, or are they actually a separate
> unit that just happens to feed this one?

Sorry, but I don't get your point. It is a clock module that is
dedicated to the PCM module.
--
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/