From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: pxa: ssp: provide platform_device_id for PXA3xx
Date: Thu, 14 Aug 2014 10:08:51 +0800 [thread overview]
Message-ID: <CAN1soZz0Fo_PNvc1dK7d9ZU49Pi0FortL4k1dwAjHEDZNcf_zg@mail.gmail.com> (raw)
In-Reply-To: <1407959959-4977-1-git-send-email-zonque@gmail.com>
On Thu, Aug 14, 2014 at 3:59 AM, Daniel Mack <zonque@gmail.com> wrote:
> Provide an explicit match string for PXA3xx SSP ports.
>
> Signed-off-by: Daniel Mack <zonque@gmail.com>
> ---
> arch/arm/plat-pxa/ssp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/plat-pxa/ssp.c b/arch/arm/plat-pxa/ssp.c
> index 3ea0290..1f5ee17 100644
> --- a/arch/arm/plat-pxa/ssp.c
> +++ b/arch/arm/plat-pxa/ssp.c
> @@ -258,6 +258,7 @@ static const struct platform_device_id ssp_id_table[] = {
> { "pxa25x-ssp", PXA25x_SSP },
> { "pxa25x-nssp", PXA25x_NSSP },
> { "pxa27x-ssp", PXA27x_SSP },
> + { "pxa3xx-ssp", PXA3xx_SSP },
> { "pxa168-ssp", PXA168_SSP },
> { "pxa910-ssp", PXA910_SSP },
> { },
> --
> 2.0.4
>
I don't agree on this. SSP1,SSP2,SSP3 on pxa3xx are same with pxa27x.
So we reuse the name.
For the new SSP4, we create pxa3xx_device_ssp4.
We just want to reuse these code.
Regards
Haojian
next prev parent reply other threads:[~2014-08-14 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 19:59 [PATCH 1/2] ARM: pxa: ssp: provide platform_device_id for PXA3xx Daniel Mack
2014-08-13 19:59 ` [PATCH 2/2] ARM: pxa3xx: provide specific platform_devices for all ssp ports Daniel Mack
2014-08-14 2:08 ` Haojian Zhuang [this message]
2014-08-14 8:35 ` [PATCH 1/2] ARM: pxa: ssp: provide platform_device_id for PXA3xx Daniel Mack
2014-08-15 8:33 ` Haojian Zhuang
2014-08-15 8:41 ` Daniel Mack
2014-08-20 8:32 ` Daniel Mack
2014-08-25 7:18 ` Haojian Zhuang
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=CAN1soZz0Fo_PNvc1dK7d9ZU49Pi0FortL4k1dwAjHEDZNcf_zg@mail.gmail.com \
--to=haojian.zhuang@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).