From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Kwok, WingMan" <w-kwok2@ti.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"pawel.moll@arm.com" <pawel.moll@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
"galak@codeaurora.org" <galak@codeaurora.org>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ssantosh@kernel.org" <ssantosh@kernel.org>,
"Karicheri, Muralidharan" <m-karicheri2@ti.com>
Subject: Re: [PATCH] ARM: dts: keystone: use one to one address translations under netcp
Date: Thu, 03 Sep 2015 07:48:56 -0700 [thread overview]
Message-ID: <55E85DD8.4070102@oracle.com> (raw)
In-Reply-To: <20150903142645.GS4215@atomide.com>
On 9/3/15 7:26 AM, Tony Lindgren wrote:
> * santosh shilimkar <santosh.shilimkar@oracle.com> [150902 08:55]:
>>
>> I suspected the same. I know back then we started with SERDES code
>> with NETCP but as you already know, its a separate block which
>> is needed for NIC card to work. Its more of phy and hence its
>> having different address space is not surprising.
>
> The point Santosh is making here though is that any drivers
> tinkering with registers belonging to a separate hardware block
> is a recipe for a long term maintenance nightmare with mysterious
> bugs popping up as things are not clocked or powered properly
> or become racy with other drivers.
>
> Each hardware block needs to have it's own driver and then the
> drivers can communicate using some Linux generic APIs like clock,
> regulator, phy, or mailbox frameworks.
>
Right !!
Regards,
Santosh
next prev parent reply other threads:[~2015-09-03 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 20:28 [PATCH] ARM: dts: keystone: use one to one address translations under netcp WingMan Kwok
[not found] ` <1441139324-29296-1-git-send-email-w-kwok2-l0cyMroinI0@public.gmane.org>
2015-09-01 21:19 ` santosh.shilimkar-QHcLZuEGTsvQT0dZR+AlfA
[not found] ` <55E61658.9010207-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-09-02 15:31 ` Kwok, WingMan
2015-09-02 15:50 ` santosh shilimkar
[not found] ` <55E71AB3.7070406-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-09-02 16:35 ` Murali Karicheri
2015-09-02 17:24 ` santosh shilimkar
[not found] ` <55E730D4.6040102-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-09-02 17:58 ` Murali Karicheri
[not found] ` <55E738AE.9000207-l0cyMroinI0@public.gmane.org>
2015-09-02 18:25 ` santosh shilimkar
2015-09-02 18:42 ` Murali Karicheri
2015-09-03 14:26 ` Tony Lindgren
2015-09-03 14:48 ` santosh.shilimkar [this message]
[not found] ` <20150903142645.GS4215-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-09-03 19:18 ` Murali Karicheri
[not found] ` <55E89CF8.4050700-l0cyMroinI0@public.gmane.org>
2015-09-08 15:13 ` Tony Lindgren
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=55E85DD8.4070102@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.com \
--cc=w-kwok2@ti.com \
/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).