devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Cc: dbaryshkov@gmail.com, dwmw2@infradead.org, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	grant.likely@linaro.org, rdunlap@infradead.org,
	linux@arm.linux.org.uk, grygorii.strashko@ti.com, olof@lixom.net,
	w-kwok2@ti.com, sboyd@codeaurora.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, m-karicheri2@ti.com
Subject: Re: [Patch v4 2/5] Power: reset: add bindings for keystone reset driver
Date: Wed, 21 May 2014 12:09:50 -0400	[thread overview]
Message-ID: <537CCFCE.7070701@ti.com> (raw)
In-Reply-To: <13696681.6eGQ96hCX4@wuerfel>

On Wednesday 21 May 2014 12:07 PM, Arnd Bergmann wrote:
> On Wednesday 21 May 2014 19:03:38 Ivan Khoronzhuk wrote:
>>
>> I've slightly confused where should I add these bindings.
>> The main pll controller mostly used by clk driver....
>> As its register set is used also by reset driver it's logically to put 
>> it to bindings/mfd,
>> but pll controller in mfd it's strange....
>>
>> Could you please help to decide where should it be?.
> 
> Put it into Documentation/devicetree/bindings/clock/keystone-pll.txt
> 
I was just about post the same suggestion. Lets do that.

regards,
Santosh


  reply	other threads:[~2014-05-21 16:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 14:27 [Patch v4 0/5] Introduce keystone reset driver Ivan Khoronzhuk
2014-05-21 14:27 ` [Patch v4 1/5] Power: reset: keystone-reset: introduce " Ivan Khoronzhuk
2014-05-21 14:27 ` [Patch v4 2/5] Power: reset: add bindings for " Ivan Khoronzhuk
2014-05-21 14:50   ` Arnd Bergmann
2014-05-21 16:03     ` Ivan Khoronzhuk
2014-05-21 16:07       ` Arnd Bergmann
2014-05-21 16:09         ` Santosh Shilimkar [this message]
2014-05-21 14:27 ` [Patch v4 3/5] ARM: keystone: remove redundant reset stuff Ivan Khoronzhuk
2014-05-21 14:27 ` [Patch v4 4/5] ARM: dts: keystone: update reset node to work with reset driver Ivan Khoronzhuk
2014-05-21 14:50   ` Arnd Bergmann
2014-05-21 16:05     ` Ivan Khoronzhuk
2014-05-21 14:27 ` [Patch v4 5/5] ARM: keystone: enable reset driver support Ivan Khoronzhuk
2014-05-21 14:52 ` [Patch v4 0/5] Introduce keystone reset driver Arnd Bergmann

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=537CCFCE.7070701@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=arnd@arndb.de \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ivan.khoronzhuk@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=m-karicheri2@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --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).