From: Eugeniy Paltsev <eugeniy.paltsev@synopsys.com>
To: Vitor Soares <vitor.soares@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vitor.soares@synopsys.com" <vitor.soares@synopsys.com>
Cc: Joao Pinto <joao.pinto@synopsys.com>,
"nelson.costa@synopsys.com" <nelson.costa@synopsys.com>,
Luis de Oliveira <luis.oliveira@synopsys.com>,
"eugeniy.Paltsev@synopsys.com" <eugeniy.paltsev@synopsys.com>,
"gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>,
"Alexey Brodkin" <alexey.brodkin@synopsys.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"jose.abreu@synopsys.com" <jose.abreu@synopsys.com>,
"pedrom.sousa@synopsys.com" <pedrom.sousa@synopsys.com>
Subject: Re: [PATCH] reset: axs10x: Implement assert and deassert callbacks
Date: Fri, 12 Apr 2019 13:22:33 +0000 [thread overview]
Message-ID: <1555075350.2668.17.camel@synopsys.com> (raw)
In-Reply-To: <13D59CF9CEBAF94592A12E8AE55501350A611EA9@DE02WEMBXB.internal.synopsys.com>
Hi Vitor,
On Mon, 2019-04-08 at 13:25 +0000, Vitor Soares wrote:
> Hi Eugeniy,
>
> From: Eugeniy Paltsev <paltsev@synopsys.com>
> Date: Mon, Apr 08, 2019 at 12:40:00
>
> > Hi Vitor,
> >
> > On Mon, 2019-04-08 at 12:31 +0200, Vitor Soares wrote:
> > > Some custom IP-block connected to ARC AXS10x board need assert and
> > > deassert functions to control reset signal of selected peripherals.
> > >
> > > This patch improve AXS10x reset driver by adding assert and deassert
> > > callbacks.
> >
> >
> > In the AXS10x reset driver only 'reset' callback is intentionally
> > > implemented.
> >
> > AXS10x is FPGA based boards and with our default firmware AXS10x reset
> > > register is implemented as self-deasserted.
>
> I have another reset block connect through AXI.
>
> > Do you have somehow modified AXS10x firmware where reset register is not
> > > self-deasserted?
> >
> > In that case "simple-reset" driver will be suitable for you, I guess.
>
> I will try it.
>
> > Otherwise this implementation is incorrect - there should be no 'assert' for
> > > reset controller with self-deasserted logic.
>
> So the assert and reset callback are mutually exclusive?
Not actually.
Adding 'assert' callback is incorrect for exclusive reset controls in
case of self-deasserted reset controller.
It will cause reset_control_assert() to return success for exclusive
reset controls, even though the .assert op failed to leave the reset
line asserted after the function returns.
[snap]
>
> Best regards,
> Vitor Soares
>
--
Eugeniy Paltsev
next prev parent reply other threads:[~2019-04-12 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 10:31 [PATCH] reset: axs10x: Implement assert and deassert callbacks Vitor Soares
2019-04-08 11:23 ` Jose Abreu
2019-04-12 13:26 ` Eugeniy Paltsev
2019-04-08 11:40 ` Eugeniy Paltsev
2019-04-08 13:25 ` Vitor Soares
2019-04-12 13:22 ` Eugeniy Paltsev [this message]
2019-04-12 14:42 ` Vitor Soares
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=1555075350.2668.17.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=alexey.brodkin@synopsys.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=joao.pinto@synopsys.com \
--cc=jose.abreu@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.oliveira@synopsys.com \
--cc=nelson.costa@synopsys.com \
--cc=p.zabel@pengutronix.de \
--cc=pedrom.sousa@synopsys.com \
--cc=vitor.soares@synopsys.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