Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1204638 > unrolled thread

Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value

Started by"Franklin S Cooper Jr." <fcooper@ti.com>
First post2015-08-11 01:50 +0200
Last post2015-08-11 11:30 +0200
Articles 5 — 3 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit  value "Franklin S Cooper Jr." <fcooper@ti.com> - 2015-08-11 01:50 +0200
    Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit  value Sekhar Nori <nsekhar@ti.com> - 2015-08-11 09:00 +0200
      Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit  value Mark Brown <broonie@kernel.org> - 2015-08-11 11:10 +0200
        Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit  value Sekhar Nori <nsekhar@ti.com> - 2015-08-11 11:30 +0200
          Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit  value Mark Brown <broonie@kernel.org> - 2015-08-11 11:30 +0200

#1204638 — Re: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value

From"Franklin S Cooper Jr." <fcooper@ti.com>
Date2015-08-11 01:50 +0200
SubjectRe: [RESEND][PATCH 3/4] ARM: davinci: Set proper SPI prescale limit value
Message-ID<pW4Zj-4Ap-1@gated-at.bofh.it>

On 07/24/2015 06:50 AM, Sekhar Nori wrote:
> On Wednesday 22 July 2015 06:02 PM, Franklin S Cooper Jr wrote:
>> SPI Davinci driver has been updated to allow SOCs to specify their minimum
>> prescale value. Update the various SOCs board files that use this driver with
>> their proper prescaler limit.
>>
>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> Acked-by: Sekhar Nori <nsekhar@ti.com>
>
> in case Mark is okay to take it through his tree. It does not clash with
> anything else I have for mach-davinci.
>
> Thanks,
> Sekhar
>
ping. Patches 1 and 2 have already been pulled into Mark's spi tree and are currently in in linux-next.

--
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/

[toc] | [next] | [standalone]


#1204829

FromSekhar Nori <nsekhar@ti.com>
Date2015-08-11 09:00 +0200
Message-ID<pWbHs-5QC-19@gated-at.bofh.it>
In reply to#1204638
On Tuesday 11 August 2015 05:17 AM, Franklin S Cooper Jr. wrote:
> 
> 
> On 07/24/2015 06:50 AM, Sekhar Nori wrote:
>> On Wednesday 22 July 2015 06:02 PM, Franklin S Cooper Jr wrote:
>>> SPI Davinci driver has been updated to allow SOCs to specify their minimum
>>> prescale value. Update the various SOCs board files that use this driver with
>>> their proper prescaler limit.
>>>
>>> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
>> Acked-by: Sekhar Nori <nsekhar@ti.com>
>>
>> in case Mark is okay to take it through his tree. It does not clash with
>> anything else I have for mach-davinci.
>>
>> Thanks,
>> Sekhar
>>
> 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?

Thanks,
Sekhar

--
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/

[toc] | [prev] | [next] | [standalone]


#1204902

FromMark Brown <broonie@kernel.org>
Date2015-08-11 11:10 +0200
Message-ID<pWdJg-zE-25@gated-at.bofh.it>
In reply to#1204829

[Multipart message — attachments visible in raw view] — view raw

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...

In any case I don't have a copy of the patch any more.

[toc] | [prev] | [next] | [standalone]


#1204916

FromSekhar Nori <nsekhar@ti.com>
Date2015-08-11 11:30 +0200
Message-ID<pWe2C-Wm-15@gated-at.bofh.it>
In reply to#1204902
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

--
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/

[toc] | [prev] | [next] | [standalone]


#1204917

FromMark Brown <broonie@kernel.org>
Date2015-08-11 11:30 +0200
Message-ID<pWe2C-Wm-17@gated-at.bofh.it>
In reply to#1204916

[Multipart message — attachments visible in raw view] — view raw

On Tue, Aug 11, 2015 at 02:54:33PM +0530, Sekhar Nori wrote:
> On Tuesday 11 August 2015 02:33 PM, Mark Brown wrote:

> > 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.

Ugh, you still have legacy platforms :(

> > 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.

I guess.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web