From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/7] ARM: S3C64XX: Reduce output of s3c64xx_dma_init1()
Date: Thu, 3 Mar 2011 14:58:33 +0000 [thread overview]
Message-ID: <1299164315-22246-5-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110303145710.GA32234@opensource.wolfsonmicro.com>
From: Ben Dooks <ben-linux@fluff.org>
Reduce the logging output of s3c64xx_dma_init1() as it is not useful
for normal bootup (and we get an overall indication of the registration
of the PL180 DMA block).
This removes the following output from the log:
s3c64xx_dma_init1: registering DMA 0 (e0808100)
s3c64xx_dma_init1: registering DMA 1 (e0808120)
s3c64xx_dma_init1: registering DMA 2 (e0808140)
s3c64xx_dma_init1: registering DMA 3 (e0808160)
s3c64xx_dma_init1: registering DMA 4 (e0808180)
s3c64xx_dma_init1: registering DMA 5 (e08081a0)
s3c64xx_dma_init1: registering DMA 6 (e08081c0)
s3c64xx_dma_init1: registering DMA 7 (e08081e0)
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
arch/arm/mach-s3c64xx/dma.c | 11 ++++++-----
1 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/arch/arm/mach-s3c64xx/dma.c b/arch/arm/mach-s3c64xx/dma.c
index 135db1b..c35585c 100644
--- a/arch/arm/mach-s3c64xx/dma.c
+++ b/arch/arm/mach-s3c64xx/dma.c
@@ -690,12 +690,12 @@ static int s3c64xx_dma_init1(int chno, enum dma_ch chbase,
regptr = regs + PL080_Cx_BASE(0);
- for (ch = 0; ch < 8; ch++, chno++, chptr++) {
- printk(KERN_INFO "%s: registering DMA %d (%p)\n",
- __func__, chno, regptr);
+ for (ch = 0; ch < 8; ch++, chptr++) {
+ pr_debug("%s: registering DMA %d (%p)\n",
+ __func__, chno + ch, regptr);
chptr->bit = 1 << ch;
- chptr->number = chno;
+ chptr->number = chno + ch;
chptr->dmac = dmac;
chptr->regs = regptr;
regptr += PL080_Cx_STRIDE;
@@ -704,7 +704,8 @@ static int s3c64xx_dma_init1(int chno, enum dma_ch chbase,
/* for the moment, permanently enable the controller */
writel(PL080_CONFIG_ENABLE, regs + PL080_CONFIG);
- printk(KERN_INFO "PL080: IRQ %d, at %p\n", irq, regs);
+ printk(KERN_INFO "PL080: IRQ %d, at %p, channels %d..%d\n",
+ irq, regs, chno, chno+8);
return 0;
--
1.7.2.3
next prev parent reply other threads:[~2011-03-03 14:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 14:57 [PATCH 0/7] Various Samsung updates Mark Brown
2011-03-03 14:58 ` [PATCH 1/7] ARM: SAMSUNG: Include devs.h in dev-uart.c to prototype devices Mark Brown
2011-03-03 14:58 ` [PATCH 2/7] ARM: S3C64XX: Staticise non-exported GPIO to interrupt functions Mark Brown
2011-03-03 14:58 ` [PATCH 3/7] ARM: S3C64XX: Add clock for i2c1 Mark Brown
2011-03-03 14:58 ` [PATCH 4/7] ARM: S3C64XX: Tone down SDHCI debugging Mark Brown
2011-03-03 14:58 ` Mark Brown [this message]
2011-03-03 14:58 ` [PATCH 6/7] ARM: SMDK6410: Fix build with WM1190 disabled and WM1192 enabled Mark Brown
2011-03-03 14:58 ` [PATCH 7/7] ARM: SMDK6410: Update regulator names for debugfs compatiblity Mark Brown
2011-03-04 1:39 ` Kukjin Kim
2011-03-04 11:33 ` Mark Brown
2011-03-03 14:59 ` [PATCH 0/7] Various Samsung updates Ben Dooks
2011-03-04 1:33 ` Kukjin Kim
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=1299164315-22246-5-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).