From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752767AbaFBIPk (ORCPT ); Mon, 2 Jun 2014 04:15:40 -0400 Received: from ns.mm-sol.com ([37.157.136.199]:38438 "EHLO extserv.mm-sol.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751708AbaFBIPh (ORCPT ); Mon, 2 Jun 2014 04:15:37 -0400 Message-ID: <538C329C.8060009@mm-sol.com> Date: Mon, 02 Jun 2014 11:15:24 +0300 From: Stanimir Varbanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: Bjorn Andersson CC: Kumar Gala , Bjorn Andersson , Samuel Ortiz , Lee Jones , Liam Girdwood , Mark Brown , Josh Cartwright , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-arm-msm Subject: Re: [PATCH 0/3] Qualcomm Resource Power Manager driver References: <1401211721-19712-1-git-send-email-bjorn.andersson@sonymobile.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Bjorn, Thanks for the patches. > Lately I've been working on rpm, rpm-smd, smem, smd, smsm, smp2p > patches for mainline. > It could be argued that smd is a bus and should go in drivers/bus, but > for the rest I fear that we just created drivers/soc/qcom as another > dumping ground for things; a "Qualcomm specific drivers/mfd". Do we have some obstacles to not use a "common mailbox framework" for this IPC (shared memory) communication. It looks that it fits very well with our needs for this rpm-regulator and future submitting of smd driver? -- regards, Stan