From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753199AbcBOMb4 (ORCPT ); Mon, 15 Feb 2016 07:31:56 -0500 Received: from mail-io0-f194.google.com ([209.85.223.194]:33636 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753173AbcBOMbz (ORCPT ); Mon, 15 Feb 2016 07:31:55 -0500 MIME-Version: 1.0 In-Reply-To: <56C1C1DA.5000207@arm.com> References: <1455210808-29395-1-git-send-email-sudeep.holla@arm.com> <56C1C1DA.5000207@arm.com> Date: Mon, 15 Feb 2016 18:01:53 +0530 Message-ID: Subject: Re: [PATCH 0/4] mailbox: mailbox-test: support single channel with separate Tx and Rx buffer From: Jassi Brar To: Sudeep Holla Cc: Lee Jones , Devicetree List , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 15, 2016 at 5:47 PM, Sudeep Holla wrote: > Hi Jassi, > > On 11/02/16 17:13, Sudeep Holla wrote: >> >> Hi Lee, Jassi, >> >> Assuming mailbox-test was designed to be generic, I am trying to extend >> it to support single channel with separate Tx and Rx buffer. With these >> changes I am able to test arm_mhu driver. However I couldn't understand >> the intention of converting buffer to ASCII hex dump in read method. >> I have a local change to remove that so that it can deal with any data >> in any format(e.g. some protocol format) and userspace can deal with the >> actual interpretation of the data. Let me know your thoughts on that. >> > > Can you review this ? It would be good to get this in for v4.6 > Seems simple enough. So once you and Lee are in sync...