From: santosh shilimkar <santosh.shilimkar@oracle.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
broonie@kernel.org, nsekhar@ti.com, ssantosh@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@arm.linux.org.uk, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, khilman@deeprootsystems.com,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-arm-kernel@list.infradead.org, robh+dt@kernel.org,
galak@codeaurora.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND][PATCH 4/4] ARM: dts: keystone: Add ti,keystone-spi for SPI
Date: Wed, 22 Jul 2015 09:17:11 -0700 [thread overview]
Message-ID: <55AFC207.3050100@oracle.com> (raw)
In-Reply-To: <1437568344-18889-5-git-send-email-fcooper@ti.com>
On 7/22/2015 5:32 AM, Franklin S Cooper Jr wrote:
> Add ti,keystone-spi to the compatible field for the SPI node. This new
> entry insures that the proper prescaler limit is used for keystone devices
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> ---
Once the binding and driver makes it, I can pick this up.
Keep me posted. Thanks !!
Regards,
Santosh
next prev parent reply other threads:[~2015-07-22 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 12:32 [RESEND][PATCH 0/4] spi: davinci: Improve prescaler limit support Franklin S Cooper Jr
2015-07-22 12:32 ` [RESEND][PATCH 1/4] spi: davinci: Set prescale value based on register value Franklin S Cooper Jr
2015-07-22 12:32 ` [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value Franklin S Cooper Jr
2015-07-24 11:50 ` Sekhar Nori
[not found] ` <55B22681.3060000-l0cyMroinI0@public.gmane.org>
2015-08-10 23:47 ` Franklin S Cooper Jr.
[not found] ` <55C9380D.1060802-l0cyMroinI0@public.gmane.org>
2015-08-11 6:58 ` Sekhar Nori
[not found] ` <55C99D0D.9050605-l0cyMroinI0@public.gmane.org>
2015-08-11 9:03 ` Mark Brown
[not found] ` <20150811090342.GG10748-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-08-11 9:24 ` Sekhar Nori
[not found] ` <55C9BF51.5080401-l0cyMroinI0@public.gmane.org>
2015-08-11 9:28 ` Mark Brown
[not found] ` <1437568344-18889-1-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2015-07-22 12:32 ` [RESEND][PATCH 2/4] spi: davinci: Choose correct pre-scaler limit based on SOC Franklin S Cooper Jr
[not found] ` <1437568344-18889-3-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2015-07-24 11:49 ` Sekhar Nori
2015-07-22 12:32 ` [RESEND][PATCH 4/4] ARM: dts: keystone: Add ti,keystone-spi for SPI Franklin S Cooper Jr
2015-07-22 16:17 ` santosh shilimkar [this message]
[not found] ` <55AFC207.3050100-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-08-24 13:36 ` Franklin S Cooper Jr.
[not found] ` <55DB1DC5.7060607-l0cyMroinI0@public.gmane.org>
2015-08-24 16:15 ` santosh shilimkar
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=55AFC207.3050100@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@list.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.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;
as well as URLs for NNTP newsgroup(s).