From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932096AbdASUcF (ORCPT ); Thu, 19 Jan 2017 15:32:05 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:34362 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754290AbdASUac (ORCPT ); Thu, 19 Jan 2017 15:30:32 -0500 MIME-Version: 1.0 In-Reply-To: <87efzyhkup.fsf@purkki.adurom.net> References: <20170113052937.12538-1-matt@ranostay.consulting> <20170113052937.12538-3-matt@ranostay.consulting> <87efzyhkup.fsf@purkki.adurom.net> From: Ulf Hansson Date: Thu, 19 Jan 2017 21:30:29 +0100 Message-ID: Subject: Re: [PATCH v3 2/2] mmc: pwrseq: add support for Marvell SD8787 chip To: Kalle Valo Cc: Matt Ranostay , "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mmc@vger.kernel.org" , "devicetree@vger.kernel.org" , Tony Lindgren , Shawn Lin 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 19 January 2017 at 21:10, Kalle Valo wrote: > Ulf Hansson writes: > >> Twisting my head around how this could be integrated smoothly into >> pwrseq simple. No, I just can find a good way forward without messing >> up pwrseq simple itself. >> >> So, for now I decided (once more :-), that let's keep this as separate driver! >> >> Perhaps, following device specific mmc pwrseq drivers will needs >> something similar, but in such case we can look into that then. >> Thinking about cw1200 for example. >> >> Let's get Rob's ack for the DT bindings, seems almost there, then I >> will queue this. > > Just to confirm, you will take the whole set (including the bindings > patch)? Yes, correct. Kind regards Uffe