From: Florian Fainelli <f.fainelli@gmail.com>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Kevin Cernekee <cernekee@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
MIPS Mailing List <linux-mips@linux-mips.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>
Subject: Re: [PATCH 2/2] reset: bcm63xx: Add support for the BCM63xx soft-reset controller
Date: Wed, 2 Dec 2015 10:03:20 -0800 [thread overview]
Message-ID: <CAGVrzcbjdsbGLuH6T6DSoC5SGN5WDFdM1h1xB5nQyX8wm-Esow@mail.gmail.com> (raw)
In-Reply-To: <565CB86F.4040303@simon.arlott.org.uk>
2015-11-30 12:58 GMT-08:00 Simon Arlott <simon@fire.lp0.eu>:
> The BCM63xx contains a soft-reset controller activated by setting
> a bit (that must previously have cleared).
>
> Signed-off-by: Simon Arlott <simon@fire.lp0.eu>
> ---
> MAINTAINERS | 1 +
> drivers/reset/Kconfig | 9 +++
> drivers/reset/Makefile | 1 +
> drivers/reset/reset-bcm63xx.c | 134 ++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 145 insertions(+)
> create mode 100644 drivers/reset/reset-bcm63xx.c
Could you create a bcm directory and then add your reset-bcm63xx.c
file there? I have a pending submission for the BCM63138 reset
controller which is not at all using the same structure and will share
nothing with your driver.
[snip]
> +static int bcm63xx_reset_xlate(struct reset_controller_dev *rcdev,
> + const struct of_phandle_args *reset_spec)
> +{
> + struct bcm63xx_reset_priv *priv = to_bcm63xx_reset_priv(rcdev);
> +
> + if (WARN_ON(reset_spec->args_count != rcdev->of_reset_n_cells))
> + return -EINVAL;
> +
> + if (reset_spec->args[0] >= rcdev->nr_resets)
> + return -EINVAL;
Should not these two things be moved to the core reset controller code
based on the #reset-cells value?
[snip]
> + if (of_property_read_u32(np, "offset", &priv->offset))
> + return -EINVAL;
> +
> + /* valid reset bits */
> + if (of_property_read_u32(np, "mask", &priv->mask))
> + priv->mask = 0xffffffff;
> +
> + priv->rcdev.owner = THIS_MODULE;
> + priv->rcdev.ops = &bcm63xx_reset_ops;
> + priv->rcdev.nr_resets = 32;
Should not that come from Device Tree, or be computed based on the
mask property, like hweight_long() or something along these lines?
> + priv->rcdev.of_node = pdev->dev.of_node;
> + priv->rcdev.of_reset_n_cells = 1;
> + priv->rcdev.of_xlate = bcm63xx_reset_xlate;
--
Florian
next prev parent reply other threads:[~2015-12-02 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 20:57 [PATCH 1/2] reset: Add brcm,bcm63xx-reset device tree binding Simon Arlott
2015-11-30 20:58 ` [PATCH 2/2] reset: bcm63xx: Add support for the BCM63xx soft-reset controller Simon Arlott
2015-12-02 18:03 ` Florian Fainelli [this message]
2015-12-02 20:43 ` Simon Arlott
2015-11-30 22:24 ` [PATCH 1/2] reset: Add brcm,bcm63xx-reset device tree binding Rob Herring
2015-12-01 11:16 ` Sergei Shtylyov
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=CAGVrzcbjdsbGLuH6T6DSoC5SGN5WDFdM1h1xB5nQyX8wm-Esow@mail.gmail.com \
--to=f.fainelli@gmail.com \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=simon@fire.lp0.eu \
/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).