From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH 5/10] dt: bindings: Add bindings for Marvell Xenon SD Host Controller Date: Thu, 24 Nov 2016 10:34:27 +0100 Message-ID: <28082657.RK5ubAe11Q@wuerfel> References: <4031579.CBE32NHUoW@wuerfel> <877f7tmduw.fsf@free-electrons.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <877f7tmduw.fsf@free-electrons.com> Sender: linux-mmc-owner@vger.kernel.org To: linux-arm-kernel@lists.infradead.org Cc: Gregory CLEMENT , Jimmy Xu , Andrew Lunn , Ulf Hansson , Romain Perier , Liuliu Zhao , Peng Zhu , "linux-kernel@vger.kernel.org" , Nadav Haklai , Ziji Hu , Victor Gu , Doug Jones , Jisheng Zhang , Yehuda Yitschak , Marcin Wojtas , Xueping Liu , Hilbert Zhang , Shiwu Zhang , Yu Cao , Sebastian Hesselbarth d List-Id: devicetree@vger.kernel.org On Thursday, November 24, 2016 10:22:31 AM CET Gregory CLEMENT wrote: > > I don't have an option for mmc in general, but using child node do not > fit at all the xenon controller. > > For this controller each slot has its own set of register, so there is > no common ressource to share so no advantage to use it. Using child node > in our case will just make the code more complex for no benefit. If every slot has its own registers, what is it that makes up the 'controller'? It sounds to me that you just have to adjust the terminology and talk about multiple controllers then, with one slot per controller. Arnd