Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752442AbbKVQXF (ORCPT ); Sun, 22 Nov 2015 11:23:05 -0500 Received: from exsmtp03.microchip.com ([198.175.253.49]:54813 "EHLO email.microchip.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751711AbbKVQXE (ORCPT ); Sun, 22 Nov 2015 11:23:04 -0500 Subject: Re: [PATCH 06/14] MIPS: Add support for PIC32MZDA platform To: Alban References: <1448065205-15762-1-git-send-email-joshua.henderson@microchip.com> <1448065205-15762-7-git-send-email-joshua.henderson@microchip.com> <20151121123753.58eb6e80@tock> CC: , From: Joshua Henderson Message-ID: <5651ED63.9090101@microchip.com> Date: Sun, 22 Nov 2015 09:29:23 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151121123753.58eb6e80@tock> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1090 Lines: 30 On 11/21/2015 04:37 AM, Alban wrote: > On Fri, 20 Nov 2015 17:17:18 -0700 > Joshua Henderson wrote: > >> This adds support for the Microchip PIC32 MIPS microcontroller with >> the specific variant PIC32MZDA. PIC32MZDA is based on the MIPS m14KEc >> core and boots using device tree. >> >> This includes an early pin setup and early clock setup needed prior to >> device tree being initialized. In additon, an interface is provided to >> synchronize access to registers shared across several peripherals. >> >> Signed-off-by: Joshua Henderson >> >> [...] >> >> diff --git a/arch/mips/include/asm/mach-pic32/gpio.h >> b/arch/mips/include/asm/mach-pic32/gpio.h new file mode 100644 > > Custom GPIO header are not used anymore, this file can be dropped. > Ack. Will drop. Josh -- 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/