From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3] reset: Add a defer reset object to send board specific reset
Date: Thu, 14 Aug 2014 12:47:38 +0200 [thread overview]
Message-ID: <20140814104738.GV15297@lukather> (raw)
In-Reply-To: <1408008998.4035.43.camel@paszta.hi.pengutronix.de>
On Thu, Aug 14, 2014 at 11:36:38AM +0200, Philipp Zabel wrote:
> Hi Maxime,
>
> Am Montag, den 11.08.2014, 19:33 +0200 schrieb Maxime Ripard:
> > > Mostly because Maxime and I seem to have a completely different opinion
> > > and nobody else argued one way or the other.
> >
> > Yep, mostly because I don't see how a generic approach can work.
> >
> > The existing reset-gpios property only provide the gpio to use, but
> > some informations are encoded in the driver, such as the reset
> > duration, or a reset sequence if any.
>
> The driver should provide the duration.
How? This used to be in the code, and reset_control_reset doesn't take
such argument.
> I'd really like to see an example where sequencing is necessary.
Well, if you have several reset lines, the sequencing between each
might be important.
> I agree that as soon as things get significantly more complicated than
> pulsing a single GPIO, the reset-gpios binding is too limited.
While the generic reset bindings are perfect for that.
> Still, I'm not happy to mandate a separate gpio reset device for each
> reset line if most devices are simple enough for it to work without.
Well, it's pretty much already the case for other subsystems, such as
regulator.
I guess we can treat this as a legacy option, but allow the reset-gpio
code to be a full driver of its own, if we need more advanced use
cases?
> What about using reset-gpios for the majority of simple cases and have a
> separate gpio-reset-sequencer driver when multiple GPIO resets have to
> be timed?
I don't know. I feel like it should be in the driver itself, rather
than in a generic layer.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140814/36248234/attachment.sig>
prev parent reply other threads:[~2014-08-14 10:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1403098673-3058-1-git-send-email-houcheng@gmail.com>
2014-07-08 7:52 ` [RFC PATCH v3] reset: Add a defer reset object to send board specific reset Linus Walleij
2014-07-08 8:05 ` Maxime Ripard
2014-07-08 9:38 ` Linus Walleij
2014-08-08 14:23 ` Philipp Zabel
2014-08-11 17:33 ` Maxime Ripard
2014-08-14 9:36 ` Philipp Zabel
2014-08-14 10:47 ` Maxime Ripard [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=20140814104738.GV15297@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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