linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: xiechao.mail@gmail.com (Chao Xie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/8] arm: pxa: fix device id for pwm
Date: Tue, 31 Jul 2012 14:29:07 +0800	[thread overview]
Message-ID: <1343716148-3899-7-git-send-email-xiechao.mail@gmail.com> (raw)
In-Reply-To: <1343716148-3899-1-git-send-email-xiechao.mail@gmail.com>

From: Chao Xie <chao.xie@marvell.com>

pxa910 has same pwm as pxa168. pxa910-pwm is not needed.
pxa168-pwm does not have depended secondary pwm.

Signed-off-by: Chao Xie <xiechao.mail@gmail.com>
---
 arch/arm/plat-pxa/pwm.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/arm/plat-pxa/pwm.c b/arch/arm/plat-pxa/pwm.c
index ef32686..45f039e 100644
--- a/arch/arm/plat-pxa/pwm.c
+++ b/arch/arm/plat-pxa/pwm.c
@@ -30,7 +30,6 @@ static const struct platform_device_id pwm_id_table[] = {
 	{ "pxa25x-pwm", 0 },
 	{ "pxa27x-pwm", 0 | HAS_SECONDARY_PWM },
 	{ "pxa168-pwm", 1 },
-	{ "pxa910-pwm", 1 },
 	{ },
 };
 MODULE_DEVICE_TABLE(platform, pwm_id_table);
-- 
1.7.0.4

  parent reply	other threads:[~2012-07-31  6:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  6:29 [PATCH 1/8] arm: mmp: add APBCP register definition Chao Xie
2012-07-31  6:29 ` [PATCH 2/8] arm: mmp: make private clock definition exclude from common clock Chao Xie
2012-07-31  6:29 ` [PATCH 3/8] arm: mmp: move pxa168 clock definition to separated file Chao Xie
2012-07-31  6:29 ` [PATCH 4/8] arm: mmp: move pxa910 " Chao Xie
2012-07-31  6:29 ` [PATCH 5/8] arm: mmp: move mmp2 " Chao Xie
2012-07-31  6:29 ` [PATCH 6/8] arm: mmp: remove unused definition in regs-apbc and regs-apmu Chao Xie
2012-07-31  6:29 ` Chao Xie [this message]
2012-07-31  6:29 ` [PATCH 8/8] arm: mmp: change pwm id for pxa910 Chao Xie

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=1343716148-3899-7-git-send-email-xiechao.mail@gmail.com \
    --to=xiechao.mail@gmail.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).