From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938897AbcIFR4V (ORCPT ); Tue, 6 Sep 2016 13:56:21 -0400 Received: from mail-pf0-f182.google.com ([209.85.192.182]:33264 "EHLO mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751221AbcIFR4T (ORCPT ); Tue, 6 Sep 2016 13:56:19 -0400 From: Kevin Hilman To: Jassi Brar Cc: Linux Kernel Mailing List , "open list\:ARM\/Amlogic Meson..." , "linux-arm-kernel\@lists.infradead.org" , Neil Armstrong Subject: Re: [PATCH v2 0/3] Add Platform MHU mailbox driver for Amlogic GXBB Organization: BayLibre References: <1471515027-3543-1-git-send-email-narmstrong@baylibre.com> Date: Tue, 06 Sep 2016 10:56:18 -0700 In-Reply-To: (Jassi Brar's message of "Sun, 4 Sep 2016 11:05:44 +0530") Message-ID: <7hpoogzzct.fsf@baylibre.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jassi Brar writes: > On Sun, Sep 4, 2016 at 2:15 AM, Kevin Hilman wrote: >> On Fri, Sep 2, 2016 at 10:33 PM, Jassi Brar wrote: >>> On Sat, Sep 3, 2016 at 5:04 AM, Kevin Hilman wrote: >>>> Hi Jassi, >>>> >>>> Neil Armstrong writes: >>>> >>>>> In order to support Mailbox links for the Amlogic GXBB SoC, add a generic >>>>> platform MHU driver based on arm_mhu.c. >>>>> >>>>> This patchset follows a RFC thread along the GXBB SCPI support at : >>>>> http://lkml.kernel.org/r/1466503374-28841-1-git-send-email-narmstrong@baylibre.com >>>>> And specific MHU discussions at : >>>>> http://lkml.kernel.org/r/CABb+yY3HqJG2+GMWCWF9PomxobrwWGZ=TZe5NvXPcHMDdLhkcQ@mail.gmail.com >>>>> >>>>> Changes since v1 at http://lkml.kernel.org/r/1470732737-18391-1-git-send-email-narmstrong@baylibre.com : >>>>> - Fix irq to signed to detect platform_get_irq() failures >>>>> - Introduced back the secure channel >>>>> - Fixed indexes >>>> >>>> How is this version looking to you? >>>> >>>> With your review/ack on the driver, I'd be happy to take it via the >>>> amlogic tree as there shouldn't be any conflicts with your tree. >>>> >>> I am ok with the driver, but I don't understand how it helps going via >>> amlogic tree. I would like to send a pull request every release ;) >> >> That's fine with me too. I offered tot take int just in case you had >> already sent pull requests for this cycle, and also since I'll take >> the DT changes through arm-soc. >> > This revision came after rc2, so it wasn't included. I will queue > patch-1 & 2 for next release, and you the patch-3. OK, sounds good. Thanks, Kevin