From: Philipp Zabel <p.zabel@pengutronix.de>
To: David Lechner <david@lechnology.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH v4] reset: add support for non-DT systems
Date: Thu, 22 Feb 2018 12:34:54 +0100 [thread overview]
Message-ID: <1519299294.7447.4.camel@pengutronix.de> (raw)
In-Reply-To: <8ef4b901-f38d-d885-e7bc-657202a2e248@lechnology.com>
On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote:
[...]
> > In your case the platform code that adds the lookup may be identical to
> > the code that registers the struct reset_controller_dev, but that
> > doesn't have to be the case. I'm not sure how that is supposed to work
> > for the phy framework (I see no platform code adding phy lookups, only
> > drivers).
> >
> In our use case, we would be adding the lookup in the driver rather than
> in the platform code, which is why I am suggesting doing it like the phy
> framework.
Shouldn't it be the job of the platform code to describe the connections
between reset controller and peripheral module reset
inputs?
regards
Philipp
next prev parent reply other threads:[~2018-02-22 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 16:58 [PATCH v4] reset: add support for non-DT systems Bartosz Golaszewski
2018-02-20 0:21 ` David Lechner
2018-02-20 10:39 ` Philipp Zabel
2018-02-20 16:40 ` David Lechner
2018-02-22 11:34 ` Philipp Zabel [this message]
2018-02-22 13:32 ` Bartosz Golaszewski
2018-02-22 16:44 ` David Lechner
2018-02-23 11:41 ` Bartosz Golaszewski
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=1519299294.7447.4.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@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