From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Marc Dietrich <marvin24@gmx.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Andrey Danin <danindrey@mail.ru>,
	Ian Campbell <ian.campbell@citrix.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	Pawel Moll <Pawel.Moll@arm.com>
Subject: Re: [RFC] binding for nvec mfd device
Date: Wed, 31 Jul 2013 14:57:32 -0600	[thread overview]
Message-ID: <51F97A3C.9010409@wwwdotorg.org> (raw)
In-Reply-To: <20130731141314.GO29859@e106331-lin.cambridge.arm.com>
On 07/31/2013 08:13 AM, Mark Rutland wrote:
> On Mon, Jul 29, 2013 at 10:59:26PM +0100, Stephen Warren wrote:
>> On 07/27/2013 07:23 AM, Marc Dietrich wrote:
>>> Hi,
>>>
>>> this is an RFC for an mfd device introduced here [1]. I didn't got much 
>>> response, except from Stephen, but that bothered me enough already ;-)
... [propose binding for Tegra I2C slave controller, and NVEC protocol
components]
>> One question I have here: There is a single I2C HW module on Tegra that
>> can act either as a master or a slave. I don't think it can do both at
>> once. Should we: ...
> 
> Is that configurable at run-time, or an integration decision?
It's certainly a run-time decision whether to operate the HW in master
or slave mode, and this is independent from anything on the board,
except of course for whether it actually makes sense to use master or
slave mode purely based on which external components are hooked up to
the bus.
I imagine that at least by appropriately resetting or reconfiguring it,
you could switch roles at run-time too. I don't know if you can actually
actively use both the master and slave portions of the HW at the exact
same time independently though. Marc is right that the diagrams in the
documentation certainly imply you can use both at the same time,
although I'm not totally convinced looking at the registers. I'm CCing
Laxman to answer that question, since he knows the HW better than I.
     prev parent reply	other threads:[~2013-07-31 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-27 13:23 [RFC] binding for nvec mfd device Marc Dietrich
2013-07-29 21:59 ` Stephen Warren
2013-07-31 14:13   ` Mark Rutland
2013-07-31 14:57     ` Marc Dietrich
2013-07-31 15:33       ` Mark Rutland
2013-07-31 16:52         ` Marc Dietrich
2013-07-31 21:03           ` Stephen Warren
     [not found]             ` <51F97B92.1040707-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-17  7:53               ` Marc Dietrich
     [not found]                 ` <17687182.lGWlO75r41-D3pzGp0ZKuDWZbiwp4sFPyrtisivX6KghOMvlBiLbJSELgA04lAiVw@public.gmane.org>
2013-09-17 21:48                   ` Stephen Warren
     [not found]                     ` <5238CE1C.3050107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-23 14:52                       ` Marc Dietrich
     [not found]                         ` <2112732.zfJtNyCk0i-D3pzGp0ZKuDWZbiwp4sFPyrtisivX6KghOMvlBiLbJSELgA04lAiVw@public.gmane.org>
2013-09-23 16:36                           ` Stephen Warren
     [not found]                             ` <52406E1E.5040005-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-09-24  7:39                               ` Andrey Danin
2013-09-24  9:33                                 ` Marc Dietrich
     [not found]                                   ` <1597574.dB5YEoR44o-D3pzGp0ZKuDWZbiwp4sFPyrtisivX6KghOMvlBiLbJSELgA04lAiVw@public.gmane.org>
2013-09-24 17:19                                     ` Stephen Warren
     [not found]                             ` <CAMRQQz-ri99PcK5=-Rzw-fmLoyvzxbd1whUWdqASx1Pi+2GNnQ@mail.gmail.com>
     [not found]                               ` <CAMRQQz-ri99PcK5=-Rzw-fmLoyvzxbd1whUWdqASx1Pi+2GNnQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-24 17:04                                 ` Stephen Warren
2013-09-18 17:28                   ` Wolfram Sang
2013-07-31 20:57     ` Stephen Warren [this message]
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=51F97A3C.9010409@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=Pawel.Moll@arm.com \
    --cc=danindrey@mail.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=ian.campbell@citrix.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=marvin24@gmx.de \
    --cc=rob.herring@calxeda.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).