From: Florian Meier <florian.meier@koalo.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
swarren@wwwdotorg.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] ASoC: Add support for BCM2708
Date: Wed, 22 May 2013 19:16:41 +0200 [thread overview]
Message-ID: <519CFD79.3050002@koalo.de> (raw)
In-Reply-To: <20130522163942.GQ1627@sirena.org.uk>
On 22.05.2013 18:39, Mark Brown wrote:
> On Wed, May 22, 2013 at 04:10:20PM +0200, Florian Meier wrote:
>
>> This driver adds support for digital audio (I2S)
>> for the BCM2708 SoC that is used by the
>> Raspberry Pi. External audio codecs can be
>> connected to the Raspberry Pi via P5 header.
>
> Split this up into a patch series, for example one per CPU side driver
> and one per machine driver. I've given the code a relatively quick run
> through here, it looks mostly sensible though DT would be nice but
> there's a few comments.
>
>> +static inline void bcm2708_i2s_write_reg(struct bcm2708_i2s_dev *dev,
>> + int reg, u32 val)
>> +{
>> + dev_dbg(dev->dev, "I2S write to register %p = %x\n",
>> + dev->clk_base + reg, val);
>> + __raw_writel(val, dev->i2s_base + reg);
>> +}
>
> This all looks like you want to use regmap-mmio.........
Thank you for your comments! I will have a look at them and send a new
patch series taking them into account.
Before that I will create a patch for the DMA engine driver.
WARNING: multiple messages have this Message-ID (diff)
From: florian.meier@koalo.de (Florian Meier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: Add support for BCM2708
Date: Wed, 22 May 2013 19:16:41 +0200 [thread overview]
Message-ID: <519CFD79.3050002@koalo.de> (raw)
In-Reply-To: <20130522163942.GQ1627@sirena.org.uk>
On 22.05.2013 18:39, Mark Brown wrote:
> On Wed, May 22, 2013 at 04:10:20PM +0200, Florian Meier wrote:
>
>> This driver adds support for digital audio (I2S)
>> for the BCM2708 SoC that is used by the
>> Raspberry Pi. External audio codecs can be
>> connected to the Raspberry Pi via P5 header.
>
> Split this up into a patch series, for example one per CPU side driver
> and one per machine driver. I've given the code a relatively quick run
> through here, it looks mostly sensible though DT would be nice but
> there's a few comments.
>
>> +static inline void bcm2708_i2s_write_reg(struct bcm2708_i2s_dev *dev,
>> + int reg, u32 val)
>> +{
>> + dev_dbg(dev->dev, "I2S write to register %p = %x\n",
>> + dev->clk_base + reg, val);
>> + __raw_writel(val, dev->i2s_base + reg);
>> +}
>
> This all looks like you want to use regmap-mmio.........
Thank you for your comments! I will have a look at them and send a new
patch series taking them into account.
Before that I will create a patch for the DMA engine driver.
next prev parent reply other threads:[~2013-05-22 17:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 14:10 [PATCH] ASoC: Add support for BCM2708 Florian Meier
2013-05-22 14:10 ` Florian Meier
2013-05-22 15:22 ` Stephen Warren
2013-05-22 15:22 ` Stephen Warren
2013-05-22 16:08 ` Florian Meier
2013-05-22 16:08 ` Florian Meier
2013-05-22 16:15 ` Stephen Warren
2013-05-22 16:15 ` Stephen Warren
2013-05-22 17:11 ` Florian Meier
2013-05-22 17:11 ` Florian Meier
2013-05-22 16:42 ` Mark Brown
2013-05-22 16:42 ` Mark Brown
2013-05-22 16:42 ` Mark Brown
2013-05-22 16:39 ` Mark Brown
2013-05-22 16:39 ` Mark Brown
2013-05-22 16:39 ` Mark Brown
2013-05-22 17:16 ` Florian Meier [this message]
2013-05-22 17:16 ` Florian Meier
2013-05-22 17:26 ` Lars-Peter Clausen
2013-05-22 17:26 ` Lars-Peter Clausen
2013-05-24 15:32 ` Florian Meier
2013-05-24 15:32 ` Florian Meier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519CFD79.3050002@koalo.de \
--to=florian.meier@koalo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=perex@perex.cz \
--cc=swarren@wwwdotorg.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.