From: Sekhar Nori <nsekhar@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: "Franklin S Cooper Jr." <fcooper@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <khilman@deeprootsystems.com>,
<linux@arm.linux.org.uk>, <galak@codeaurora.org>,
<ijc+devicetree@hellion.org.uk>, <mark.rutland@arm.com>,
<pawel.moll@arm.com>, <robh+dt@kernel.org>,
<linux-arm-kernel@list.infradead.org>, <ssantosh@kernel.org>
Subject: Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value
Date: Tue, 11 Aug 2015 14:54:33 +0530 [thread overview]
Message-ID: <55C9BF51.5080401@ti.com> (raw)
In-Reply-To: <20150811090342.GG10748@sirena.org.uk>
On Tuesday 11 August 2015 02:33 PM, Mark Brown wrote:
> On Tue, Aug 11, 2015 at 12:28:21PM +0530, Sekhar Nori wrote:
>> On Tuesday 11 August 2015 05:17 AM, Franklin S Cooper Jr. wrote:
>
>>> ping. Patches 1 and 2 have already been pulled into Mark's spi tree and are currently in in linux-next.
>
>> Mark, can you apply this patch to your tree as well? Thats the preferred
>> route for me.
>
>> If thats not an option for you, can you confirm that the topic/davinci
>> branch of your spi tree is an immutable commit I can base my pull
>> request to ARM-SoC on?
>
> Why would there be any interdependency between the the two trees, that
> would be very unusual? Adding a new value to DT doesn't need the kernel
> to understand it and the driver should be compatible with existing DTs.
> If there *is* some dependency that suggests the driver update has
> problems...
The dependency is because of platform data. Patch 2/4 adds a new
platform data member 'prescaler_limit' which this patch populates for
DaVinci devices using legacy booting.
> In any case I don't have a copy of the patch any more.
I can resend this patch to you with my ack included.
Thanks,
Sekhar
next prev parent reply other threads:[~2015-08-11 9:25 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 2/4] spi: davinci: Choose correct pre-scaler limit based on SOC Franklin S Cooper Jr
2015-07-24 11:49 ` Sekhar Nori
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
2015-08-10 23:47 ` Franklin S Cooper Jr.
2015-08-11 6:58 ` Sekhar Nori
2015-08-11 9:03 ` Mark Brown
2015-08-11 9:24 ` Sekhar Nori [this message]
2015-08-11 9:28 ` Mark Brown
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
2015-08-24 13:36 ` Franklin S Cooper Jr.
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=55C9BF51.5080401@ti.com \
--to=nsekhar@ti.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=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).