From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kevin Hilman <khilman@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Vivek Goyal <vgoyal@redhat.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Riku Voipio <riku.voipio@linaro.org>,
Jiri Kosina <jkosina@suse.cz>, Paul Bolle <pebolle@tiscali.nl>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Richard Weinberger <richard@nod.at>, Zhigang Lu <zlu@tilera.com>,
Vineet Gupta <vgupta@synopsys.com>,
Richard Kuo <rkuo@codeaurora.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-kernel@vger.ker
Subject: Re: [PATCH 2/2] Changes to existing files for 0PF FPGA board.
Date: Thu, 18 Jun 2015 21:36:21 +0200 [thread overview]
Message-ID: <CAMuHMdV_hNng9MDotN3jidRdG+WEUwjDwYcmTTohLPtfMEoAKg@mail.gmail.com> (raw)
In-Reply-To: <1434647946.861922@landley.net>
Hi Rob,
On Thu, Jun 18, 2015 at 7:19 PM, Rob Landley <rob@landley.net> wrote:
> Changes to existing files to add 0pf j2 board support.
Thanks for your patch!
Like Greg already said, splitting it up in logical parts and providing useful
patch descriptions would be highly appreciated.
> diff --git a/arch/sh/Makefile b/arch/sh/Makefile
> index bf5b3f5..e609157 100644
> --- a/arch/sh/Makefile
> +++ b/arch/sh/Makefile
> @@ -31,6 +33,7 @@ isa-y := $(isa-y)-up
> endif
>
> cflags-$(CONFIG_CPU_SH2) := $(call cc-option,-m2,)
> +cflags-$(CONFIG_CPU_SH2J) := $(call cc-option,-m2,)
This is superfluous, as CPU_SH2J selects CPU_SH2.
> diff --git a/arch/sh/kernel/irq.c b/arch/sh/kernel/irq.c
> index eb10ff8..7de9bcb 100644
> --- a/arch/sh/kernel/irq.c
> +++ b/arch/sh/kernel/irq.c
> @@ -20,6 +20,8 @@
> #include <asm/thread_info.h>
> #include <cpu/mmu_context.h>
>
> +#include <asm/board-0pf.h>
Board-specific inclusion in generic sh source file?
> +
> atomic_t irq_err_count;
>
> /*
> @@ -175,11 +177,24 @@ void do_softirq_own_stack(void)
> );
> }
> #else
> +#define noinline __attribute__((noinline))
> +static noinline void handle_irq_UART0(unsigned int irq) { generic_handle_irq(irq); }
> +static noinline void handle_irq_UART1(unsigned int irq) { generic_handle_irq(irq); }
> +static noinline void handle_irq_GPS(unsigned int irq) { generic_handle_irq(irq); }
> +static noinline void handle_irq_EMAC(unsigned int irq) { generic_handle_irq(irq); }
> static inline void handle_one_irq(unsigned int irq)
> {
> - generic_handle_irq(irq);
> + switch(irq) {
> + case Irq_UART0: handle_irq_UART0(irq); break;
> + case Irq_UART1: handle_irq_UART1(irq); break;
> + case Irq_GPS: handle_irq_GPS(irq); break;
> + case Irq_EMAC: handle_irq_EMAC(irq); break;
> + default:
> + generic_handle_irq(irq);
> + break;
> + }
What's the purpose of this change?
> }
> -#endif
> +#endif // CONFIG_IRQSTACKS
Please no C++-style comments (scripts/checkpatch.pl?)
> diff --git a/arch/sh/mm/cache-sh2.c b/arch/sh/mm/cache-sh2.c
> index a74259f..438eadb 100644
> --- a/arch/sh/mm/cache-sh2.c
> +++ b/arch/sh/mm/cache-sh2.c
> @@ -16,6 +17,30 @@
> #include <asm/cacheflush.h>
> #include <asm/io.h>
>
> +#if defined(CONFIG_CPU_SUBTYPE_0PF)
> +
> +// Just flush the whole thing each time
Likewise
> +static void j2_flush_icache_range(void *fwoosh)
> +{
> + __raw_writel(CCR_CACHE_RESET, CCR);
> +}
> +
> +// This should never happen, but...
Likewise.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-06-18 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1434647946.861556@landley.net>
2015-06-18 17:19 ` [PATCH 2/2] Changes to existing files for 0PF FPGA board Rob Landley
2015-06-18 17:59 ` Greg Kroah-Hartman
2015-06-18 19:02 ` Steven Rostedt
2015-06-19 21:57 ` Rob Landley
2015-06-19 22:49 ` Greg Kroah-Hartman
2015-06-18 19:36 ` Geert Uytterhoeven [this message]
2015-06-19 22:11 ` Rob Landley
2015-06-20 8:00 ` Geert Uytterhoeven
2015-06-20 20:13 ` Rob Landley
2015-06-20 20:48 ` Geert Uytterhoeven
2015-06-22 4:26 ` Yoshinori Sato
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=CAMuHMdV_hNng9MDotN3jidRdG+WEUwjDwYcmTTohLPtfMEoAKg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=davidlohr@hp.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=khilman@linaro.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.ker \
--cc=linux-sh@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pebolle@tiscali.nl \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richard@nod.at \
--cc=riku.voipio@linaro.org \
--cc=rkuo@codeaurora.org \
--cc=rob@landley.net \
--cc=rostedt@goodmis.org \
--cc=vgoyal@redhat.com \
--cc=vgupta@synopsys.com \
--cc=zlu@tilera.com \
/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).