From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] sh: Add initial support for SH7734 CPU subtype
Date: Thu, 12 Apr 2012 00:11:12 +0000 [thread overview]
Message-ID: <20120412001112.GB7368@linux-sh.org> (raw)
In-Reply-To: <1334188415-14427-1-git-send-email-nobuhiro.iwamatsu.yj@renesas.com>
On Thu, Apr 12, 2012 at 08:53:34AM +0900, Nobuhiro Iwamatsu wrote:
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> ---
>
> V2: Fix build clock framework on 3.4-rc2
>
If you are adding a new CPU then you at least need some changelog
outlining some basic information about it, what you are supporting, etc.
> +struct clk *clks[] = {
> + &sh7734_ifs_clk,
> + &sh7734_sfs_clk,
> + &sh7734_bfs_clk,
> + &sh7734_mfs_clk,
> + &sh7734_s1fs_clk,
> + &sh7734_pfs_clk,
> +};
> +
These are all div4 clocks, use the div4 clock API.
> +#include <linux/usb/ehci-sh.h>
I don't see this in mainline or my tree. If you are going to send me
patches that you know won't build or have a dependency that hasn't been
met, you either need to state it clearly, or I'll just ignore the entire
series.
> +/* SCIF */
> +static struct plat_sci_port scif0_platform_data = {
> + .mapbase = 0xFFE40000,
> + .flags = UPF_BOOT_AUTOCONF,
> + .scscr = SCSCR_RE | SCSCR_TE | SCSCR_REIE,
> + .scbrr_algo_id = SCBRR_ALGO_2,
> + .type = PORT_SCIF,
> + .irqs = { evt2irq(0x8C0),
> + evt2irq(0x8C0),
> + evt2irq(0x8C0),
> + evt2irq(0x8C0) },
> + .regtype = SCIx_SH4_SCIF_REGTYPE,
> +};
> +
You can use SCIx_IRQ_MUXED() for these.
next prev parent reply other threads:[~2012-04-12 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 23:53 [PATCH 1/2 v2] sh: Add initial support for SH7734 CPU subtype Nobuhiro Iwamatsu
2012-04-12 0:11 ` Paul Mundt [this message]
2012-04-12 6:39 ` Nobuhiro Iwamatsu
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=20120412001112.GB7368@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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