Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp4761132ybl; Wed, 22 Jan 2020 04:17:04 -0800 (PST) X-Google-Smtp-Source: APXvYqwvrwqVctT1AqmJhchrvEz6gcQhP2gVLDdMeHALJH36S196nNKuIsj1SkcmC30HjAmRQlPN X-Received: by 2002:a05:6808:208:: with SMTP id l8mr6415653oie.112.1579695423930; Wed, 22 Jan 2020 04:17:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579695423; cv=none; d=google.com; s=arc-20160816; b=nlaIcOTBcCsv3/720vbMbg5LY1efbpLg3vcjq7pMJUe2l4LK0mcQN38ul1i584u/t4 J1rhibltSvW4U6l5emAnlJgse+FZQMpiVir4/1Svs3y/Uu43M7irQeCXXV+AjuFVZ+c5 aOcToztNKOTHcC/YFX0GnDZHZ+uzxRcMO24SP7GQgdJZ5JRvbV4tMSt8BIe1LjO6LjBF lmGEh79pCYx2a1cKbzy6Yke6gck/TC1rhMq6OX/7I/FSwx8cgJvUsd2rTsCEVKUWSczX U3ifMT7XcT8qFvbjEchEcG7ghu1wvzQ5VurWqrzn3gFSEp9zvpg+Of9lMPZUL+2/CcYf gt/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=joohISb5lp7VjuWZQvy4pEgD4PwO3v6k+0ypFXNDnZw=; b=qORuAr/K24sT17Hdcgj8kvCeny0nZ+0VunQG9xFsq4DXXh1B1xX28O5dqSHqGNPOdJ RBUeIhwCx01tc37grtx2Py5kNzYTvTwrcdQXhfs8HA4aX1gAC9RFQQLUNPzyANAumwZi oBekerP1WIJbEVJmeVUAI40UTX1NbpoUdSgAO9krII2Rkx679zH5S+YJUUGBrWGUpfAq rNaJdkgsnT6EaXtiBlohXAp1bVtyBqiCd7adW/orOMLtl7BJOHaiW0rNQGsYtPZb/kWb lGdtD77qfy8VS4tHxbWKx16Hj4ZD3N2gzUEGwthGz6xTQ2H8VBAWJiQ7Q8tFKE85i3kX 6aXg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t3si21896634oig.25.2020.01.22.04.16.52; Wed, 22 Jan 2020 04:17:03 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729138AbgAVMPr (ORCPT + 99 others); Wed, 22 Jan 2020 07:15:47 -0500 Received: from foss.arm.com ([217.140.110.172]:55698 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726204AbgAVMPq (ORCPT ); Wed, 22 Jan 2020 07:15:46 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 67B90328; Wed, 22 Jan 2020 04:15:46 -0800 (PST) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 324543F52E; Wed, 22 Jan 2020 04:15:45 -0800 (PST) Date: Wed, 22 Jan 2020 12:15:38 +0000 From: Sudeep Holla To: Viresh Kumar Cc: arnd@arndb.de, jassisinghbrar@gmail.com, cristian.marussi@arm.com, peng.fan@nxp.com, peter.hilber@opensynergy.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Sudeep Holla Subject: Re: [PATCH V4] firmware: arm_scmi: Make scmi core independent of the transport type Message-ID: <20200122121538.GA31240@bogus> References: <20200121183818.GA11522@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 22, 2020 at 08:06:23AM +0530, Viresh Kumar wrote: > The SCMI specification is fairly independent of the transport protocol, > which can be a simple mailbox (already implemented) or anything else. > The current Linux implementation however is very much dependent on the > mailbox transport layer. > > This patch makes the SCMI core code (driver.c) independent of the > mailbox transport layer and moves all mailbox related code to a new > file: mailbox.c. > > We can now implement more transport protocols to transport SCMI > messages. > > The transport protocols just need to provide struct scmi_transport_ops, > with its version of the callbacks to enable exchange of SCMI messages. > > Signed-off-by: Viresh Kumar > --- > @Sudeep: It was my mistake that I didn't check if there is something > already queued for next release and you never told me as well earlier :) > No I didn't want to distract the discussion with that silly thing. > Can you please help me getting this tested, now that I have rebased it > as well :) ? > Sure, I will give it a go on my Juno. Thanks for the rebase, makes it simpler. -- Regards, Sudeep