From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"eugeniy.paltsev@synopsys.com" <eugeniy.paltsev@synopsys.com>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"joao.pinto@synopsys.com" <joao.pinto@synopsys.com>
Subject: Re: [PATCH v2] ARC: Configure APB GPIO controller on ARC HSDK platform
Date: Fri, 6 Jul 2018 16:35:21 +0000 [thread overview]
Message-ID: <1b200ba226f7e509049f0ffbf4478ca0d80a67b0.camel@synopsys.com> (raw)
In-Reply-To: <5f3c59cdf0f4eb8bf22ca27031187fd866ffbecc.1530872741.git.gustavo.pimentel@synopsys.com>
Hi Gustavo,
On Fri, 2018-07-06 at 11:32 +0100, Gustavo Pimentel wrote:
> In case of HSDK we have intermediate INTC in for of DW APB GPIO controller
> which is used as a de-bounce logic for interrupt wires that come from
> outside the board.
>
> We cannot use existing "irq-dw-apb-ictl" driver here because all input
> lines are routed to corresponding output lines but not muxed into one
> line (this is configured in RTL and we cannot change this in software).
>
> But even if we add such a feature to "irq-dw-apb-ictl" driver that won't
> benefit us as higher-level INTC (in case of HSDK it is IDU) anyways has
> per-input control so adding fully-controller intermediate INTC will only
> bring some overhead on interrupt processing but no other benefits.
>
> Thus we just do one-time configuration of DW APB GPIO controller and
> forget about it.
>
> Based on implementation available on arch/arc/plat-axs10x/axs10x.c file.
>
> Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Acked-by: Alexey Brodkin <abrodkin@synopsys.com>
prev parent reply other threads:[~2018-07-06 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 10:32 Gustavo Pimentel
2018-07-06 16:35 ` Alexey Brodkin [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=1b200ba226f7e509049f0ffbf4478ca0d80a67b0.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=eugeniy.paltsev@synopsys.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=joao.pinto@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.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
all inboxes | Powered by JetHome®