Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757481Ab3ENSIx (ORCPT ); Tue, 14 May 2013 14:08:53 -0400 Received: from mail-wg0-f43.google.com ([74.125.82.43]:58264 "EHLO mail-wg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752416Ab3ENSIv (ORCPT ); Tue, 14 May 2013 14:08:51 -0400 MIME-Version: 1.0 X-Originating-IP: [2620:0:1000:1b02:6e3b:e5ff:fe16:f1aa] In-Reply-To: <1368515328-31535-3-git-send-email-draviv@codeaurora.org> References: <1368515328-31535-1-git-send-email-draviv@codeaurora.org> <1368515328-31535-3-git-send-email-draviv@codeaurora.org> Date: Tue, 14 May 2013 11:08:49 -0700 Message-ID: Subject: Re: [PATCH V2 2/9] Documentation: devicetree: Add DT bindings for UFS host controller From: Olof Johansson To: Dolev Raviv Cc: linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org, Sujit Reddy Thumma , "moderated list:OPEN FIRMWARE AND..." , "open list:DOCUMENTATION" , open list Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1509 Lines: 40 On Tue, May 14, 2013 at 12:08 AM, Dolev Raviv wrote: > Compatible list is used in commit 03b1781 but is not documented. > Add necessary device tree bindings to describe on-chip UFS host > controllers. > > Signed-off-by: Sujit Reddy Thumma > > diff --git a/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt b/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt > new file mode 100644 > index 0000000..20468b2 > --- /dev/null > +++ b/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt > @@ -0,0 +1,16 @@ > +* Universal Flash Storage (UFS) Host Controller > + > +UFSHC nodes are defined to describe on-chip UFS host controllers. > +Each UFS controller instance should have its own node. > + > +Required properties: > +- compatible : compatible list, contains "jedec,ufs-1.1" > +- interrupts : > +- reg : > + > +Example: > + ufshc@0xfc598000 { > + compatible = "jedec,ufs-1.1"; Hmm. Does jedec really specify the programming interface of this type of device, register layout and meaning? It seems to be more about the command set and electrical/connectivity specifications, no? -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/