From: Rob Herring <robh@kernel.org>
To: Yaniv Gardi <ygardi@codeaurora.org>
Cc: robherring2@gmail.com, James.Bottomley@HansenPartnership.com,
pebolle@tiscali.nl, hch@infradead.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-arm-msm@vger.kernel.org, santoshsy@gmail.com,
linux-scsi-owner@vger.kernel.org, subhashj@codeaurora.org,
Gilad Broner <gbroner@codeaurora.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Vinayak Holikatti <vinholikatti@gmail.com>,
"James E.J. Bottomley" <JBottomley@odin.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [v4 01/14] scsi: ufs-qcom: add number of lanes per direction
Date: Mon, 8 Feb 2016 11:53:17 -0600 [thread overview]
Message-ID: <20160208175317.GA12559@rob-hp-laptop> (raw)
In-Reply-To: <1454582180-3823-2-git-send-email-ygardi@codeaurora.org>
On Thu, Feb 04, 2016 at 12:36:07PM +0200, Yaniv Gardi wrote:
> Different platform may have different number of lanes
> for the UFS link.
> Add parameter to device tree specifying how many lanes
> should be configured for the UFS link.
>
> Signed-off-by: Gilad Broner <gbroner@codeaurora.org>
> Signed-off-by: Yaniv Gardi <ygardi@codeaurora.org>
>
> ---
> .../devicetree/bindings/ufs/ufshcd-pltfrm.txt | 3 ++
> drivers/scsi/ufs/ufs-qcom.c | 39 ++++++++++++----------
> drivers/scsi/ufs/ufshcd-pltfrm.c | 19 +++++++++++
> drivers/scsi/ufs/ufshcd.c | 1 +
> drivers/scsi/ufs/ufshcd.h | 2 ++
> 5 files changed, 47 insertions(+), 17 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2016-02-08 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454582180-3823-1-git-send-email-ygardi@codeaurora.org>
2016-02-04 10:36 ` [v4 01/14] scsi: ufs-qcom: add number of lanes per direction Yaniv Gardi
2016-02-08 17:53 ` Rob Herring [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160208175317.GA12559@rob-hp-laptop \
--to=robh@kernel.org \
--cc=JBottomley@odin.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gbroner@codeaurora.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi-owner@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=pawel.moll@arm.com \
--cc=pebolle@tiscali.nl \
--cc=robherring2@gmail.com \
--cc=santoshsy@gmail.com \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox