From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1425236AbcFHUsx (ORCPT ); Wed, 8 Jun 2016 16:48:53 -0400 Received: from mail-oi0-f48.google.com ([209.85.218.48]:36263 "EHLO mail-oi0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1424670AbcFHUsu (ORCPT ); Wed, 8 Jun 2016 16:48:50 -0400 Date: Wed, 8 Jun 2016 15:48:48 -0500 From: Rob Herring To: Shawn Lin Cc: Ulf Hansson , Jaehoon Chung , linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org, Doug Anderson , linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org Subject: Re: [RFC PATCH 1/4] Documentation: mmc: add description for new caps Message-ID: <20160608204848.GA3368@rob-hp-laptop> References: <1465373996-2485-1-git-send-email-shawn.lin@rock-chips.com> <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1465374021-2526-1-git-send-email-shawn.lin@rock-chips.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 08, 2016 at 04:20:21PM +0800, Shawn Lin wrote: > Let's add some basic description for cap-no-sdio, > cap-no-sd and cap-no-mmc. This doesn't say why. If you know what is there, then there's a better way to do this. Look at the child nodes because chances are if you have something soldered down like SDIO or eMMC, then you have a child node already for resets, regulators, etc. Rob