Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932508AbbFRTg3 (ORCPT ); Thu, 18 Jun 2015 15:36:29 -0400 Received: from mail-ob0-f171.google.com ([209.85.214.171]:35349 "EHLO mail-ob0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932305AbbFRTgV (ORCPT ); Thu, 18 Jun 2015 15:36:21 -0400 MIME-Version: 1.0 In-Reply-To: <1434647946.861922@landley.net> References: <1434647946.861556@landley.net> <1434647946.861922@landley.net> Date: Thu, 18 Jun 2015 21:36:21 +0200 X-Google-Sender-Auth: ZBuED9Q_qgCyEarOhn9PSpdb2DU Message-ID: Subject: Re: [PATCH 2/2] Changes to existing files for 0PF FPGA board. From: Geert Uytterhoeven To: Rob Landley Cc: Greg Kroah-Hartman , Jiri Slaby , Andrew Morton , Geert Uytterhoeven , Kevin Hilman , "Rafael J. Wysocki" , Vivek Goyal , "Steven Rostedt (Red Hat)" , "Kirill A. Shutemov" , Riku Voipio , Jiri Kosina , Paul Bolle , Ingo Molnar , Peter Zijlstra , Davidlohr Bueso , Richard Weinberger , Zhigang Lu , Vineet Gupta , Richard Kuo , Max Filippov , Pranith Kumar , Linux-sh list , "linux-kernel@vger.kernel.org" , "linux-serial@vger.kernel.org" , Yoshinori Sato Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3188 Lines: 108 Hi Rob, On Thu, Jun 18, 2015 at 7:19 PM, Rob Landley 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 > #include > > +#include 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 > #include > > +#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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/