From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] drivers: reset: Add STM32 reset driver
Date: Wed, 06 Jul 2016 17:43:58 +0200 [thread overview]
Message-ID: <1467819838.2914.6.camel@pengutronix.de> (raw)
In-Reply-To: <577D264A.4050709@st.com>
Am Mittwoch, den 06.07.2016, 17:39 +0200 schrieb Gabriel Fernandez:
> Hi Philipp
>
> On 07/05/2016 03:29 PM, Philipp Zabel wrote:
> > Am Dienstag, den 05.07.2016, 09:29 +0200 schrieb Gabriel Fernandez:
> > [...]
> >>>> +static const struct reset_control_ops stm32_reset_ops = {
> >>>> + .assert = stm32_reset_assert,
> >>>> + .deassert = stm32_reset_deassert,
> >>> Are the registers not readable, or did you choose not to
> >>> implement .status on purpose?
> >> We choose to not implement.
> > Ok. Because of size issues or just because you don't need them in any of
> > your drivers?
> Because i don't need them.
Ok, thanks for clarifying.
regards
Philipp
next prev parent reply other threads:[~2016-07-06 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 13:47 [PATCH 1/4] dt-bindings: mfd: Add STM32F4 RCC numeric constants into DT include file gabriel.fernandez at st.com
2016-07-04 13:47 ` [PATCH 2/4] dt-bindings: Document the STM32 reset bindings gabriel.fernandez at st.com
2016-07-04 17:36 ` Philipp Zabel
2016-07-05 7:30 ` Gabriel Fernandez
2016-07-05 16:18 ` Rob Herring
2016-07-06 7:39 ` Gabriel Fernandez
2016-07-04 13:47 ` [PATCH 3/4] drivers: reset: Add STM32 reset driver gabriel.fernandez at st.com
2016-07-04 17:36 ` Philipp Zabel
2016-07-05 7:29 ` Gabriel Fernandez
2016-07-05 13:29 ` Philipp Zabel
2016-07-06 15:39 ` Gabriel Fernandez
2016-07-06 15:43 ` Philipp Zabel [this message]
2016-07-05 13:28 ` Philipp Zabel
2016-07-06 7:44 ` Gabriel Fernandez
2016-07-04 13:47 ` [PATCH 4/4] ARM: dts: stm32f429: add missing #reset-cells of rcc gabriel.fernandez at st.com
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=1467819838.2914.6.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).