linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Hartley <james.hartley@imgtec.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Damien Horsley <damien.horsley@imgtec.com>,
	Govindraj Raja <govindraj.raja@imgtec.com>
Subject: Re: [PATCH 1/2] reset: img: Add pistachio reset controller binding document
Date: Fri, 15 Jan 2016 16:32:35 +0000	[thread overview]
Message-ID: <56991F23.8010500@imgtec.com> (raw)
In-Reply-To: <1452873439.6067.86.camel@pengutronix.de>

Hi Philipp,

Thanks for the quick review,

On 01/15/16 15:57, Philipp Zabel wrote:
> Am Freitag, den 15.01.2016, 14:44 +0000 schrieb James Hartley:
[..]
>> +Example:
>> +
>> +	pistachio_reset: reset-controller {
>> +		compatible = "img,pistachio-reset";
>> +		img,cr-periph = <&cr_periph>;
>> +		#reset-cells = <1>;
>> +	};
> If this is just a register in the cr_periph syscon, why not put the
> reset-controller node inside the cr_periph node:
>
>      cr_periph: syscon@xyz {
>          compatible = "syscon", "simple-mfd";
>          pistachio_reset: reset-controller {
>              compatible = "img,pistachio-reset";
>              #reset-cells = <1>;
>          };
>      };
>
> And in the driver use
>      syscon_node_to_regmap(np->parent);
> instead of
>      syscon_regmap_lookup_by_phandle(np, "img,cr-periph");
> ?

Yes that makes sense, I'll look at changing that for a V2 patchset.

> Do you need a reg property, or is will the register offset be 0 in all
> pistachio variants?

The offset will always be 0 for all pistachio variants.

[..]
> +Example:
> +
> +	spdif_out: spdif-out@18100d00 {
> +		...
> +		resets = <&pistachio_reset PISTACHIO_RESET_SPDIF_OUT>;
> +		reset-names = "rst";
> reset-names is not needed for devices that only have one reset.

Agreed, but there are already audio drivers that pistachio uses that 
have been merged upstream
using this name in their dt-entries - is there any harm in leaving it in?

>
> regards
> Philipp
>
Thanks,
James.

  reply	other threads:[~2016-01-15 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 14:44 [PATCH 0/2] reset: img: Add pistachio SoC reset support James Hartley
     [not found] ` <1452869073-27608-2-git-send-email-james.hartley@imgtec.com>
2016-01-15 15:57   ` [PATCH 1/2] reset: img: Add pistachio reset controller binding document Philipp Zabel
2016-01-15 16:32     ` James Hartley [this message]
2016-01-15 16:48       ` Philipp Zabel

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=56991F23.8010500@imgtec.com \
    --to=james.hartley@imgtec.com \
    --cc=damien.horsley@imgtec.com \
    --cc=devicetree@vger.kernel.org \
    --cc=govindraj.raja@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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).