From: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
To: Alexander Sverdlin
<alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>,
Kevin Hilman
<khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>,
Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Murali Karicheri <m-karicheri2-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH] i2c: davinci: Fix bus rate calculation on Keystone SoC
Date: Thu, 18 Jun 2015 16:42:47 +0530 [thread overview]
Message-ID: <5582A7AF.5030000@ti.com> (raw)
In-Reply-To: <558297B3.2060406-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
On Thursday 18 June 2015 03:34 PM, Alexander Sverdlin wrote:
> Hi!
>
> On 18/06/15 11:47, ext Sekhar Nori wrote:
>>> Ah, beyond the evalboards, there are device-trees not linked into the kernel,
>>>> but flashed into the boards, as originally in OF. They are part of the HW, its
>>>> description. Not part or description of the Kernel. And you have no way to
>>>> introduce this fix any more without updating this OF part if you go with
>>>> new compatible property.
>> I see. So how critical is this fix? That should be described in the
>> commit description. And if its really critical, stable kernel should be
>> CCed too.
>
> Now we got to the point, see below...
>
>>>>>>>>>> And from the other PoV, device-trees are for something one cannot probe. We
>>>>>>>>>> can probe for Keystone revisions and can free the end-user from this headache
>>>>>>>>>> completely.
>>>>>> Keep in mind that this can invite driver patching whenever version
>>>>>> number is tinkered with in hardware - even for otherwise
>>>>>> software-invsible changes.
>>>>
>>>> That's true. But I do not have an overview, how many IP versions do you actually have?
>>>> I've found one revision in Davinci manual, one revision in Keystone manual, even
>>>> including minor revision. Checking only major revision now can survive couple of minor
>>>> changes in IP.
>> Yeah, sticking to major version should help. What I am worried about are
>> versions coming in future, not those existing. And development on
>> keystone architecture is ongoing in TI.
>
> This is not really critical fix. Currently bus rate is lower than expected because of these
> calculation errors. The fix maximizes the bus rate. So newer SoCs will run little bit slower
> until support is added to this part of the code. Not really critical. So no point in CCing
> stable maintainers also.
If its not a critical fix, do we really need to care about older DTBs
which have been ROM'ed into production?
Thanks,
Sekhar
next prev parent reply other threads:[~2015-06-18 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 8:53 [PATCH] i2c: davinci: Fix bus rate calculation on Keystone SoC Alexander Sverdlin
[not found] ` <5582870B.7030304-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 9:00 ` Sekhar Nori
[not found] ` <558288B0.1020706-l0cyMroinI0@public.gmane.org>
2015-06-18 9:09 ` Alexander Sverdlin
[not found] ` <55828ADB.3080604-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 9:25 ` Sekhar Nori
[not found] ` <55828E7F.8060501-l0cyMroinI0@public.gmane.org>
2015-06-18 9:37 ` Alexander Sverdlin
[not found] ` <55829159.8050707-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 9:47 ` Sekhar Nori
[not found] ` <558293C9.9050904-l0cyMroinI0@public.gmane.org>
2015-06-18 10:04 ` Alexander Sverdlin
[not found] ` <558297B3.2060406-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2015-06-18 11:12 ` Sekhar Nori [this message]
[not found] ` <5582A7AF.5030000-l0cyMroinI0@public.gmane.org>
2015-06-18 11:30 ` Alexander Sverdlin
2015-06-18 16:22 ` Murali Karicheri
[not found] ` <5582F049.8070407-l0cyMroinI0@public.gmane.org>
2015-07-09 19:53 ` Wolfram Sang
2015-07-10 16:02 ` Sekhar Nori
[not found] ` <559FEC8C.9030603-l0cyMroinI0@public.gmane.org>
2015-07-10 18:26 ` Grygorii Strashko
[not found] ` <55A00E56.2020308-l0cyMroinI0@public.gmane.org>
2015-08-12 8:43 ` Wolfram Sang
2015-08-13 10:29 ` Alexander Sverdlin
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=5582A7AF.5030000@ti.com \
--to=nsekhar-l0cymroini0@public.gmane.org \
--cc=alexander.sverdlin-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m-karicheri2-l0cyMroinI0@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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).