From: Ricardo Ribalda <ribalda@chromium.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ross Zwisler <zwisler@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Ricardo Ribalda <ribalda@chromium.org>
Subject: [PATCH v1 0/1] pinctrl:mtk: Fix kexec() initialization
Date: Tue, 22 Nov 2022 00:38:54 +0100 [thread overview]
Message-ID: <20221122-mtk-pinctrl-v1-0-bedf5655a3d2@chromium.org> (raw)
When we use kexec to reboot a system, the hardware keeps its
old state.
This can be problematic for interrupt controllers.
Lets initialise the controller with a know state.
To: Sean Wang <sean.wang@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-mediatek@lists.infradead.org
Cc: linux-gpio@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: Joel Fernandes (Google) <joel@joelfernandes.org>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ross Zwisler <zwisler@kernel.org>
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
Ricardo Ribalda (1):
pinctrl: meditatek: Startup with the IRQs disabled
drivers/pinctrl/mediatek/mtk-eint.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
---
base-commit: eb7081409f94a9a8608593d0fb63a1aa3d6f95d8
change-id: 20221122-mtk-pinctrl-a82d0240c848
Best regards,
--
Ricardo Ribalda <ribalda@chromium.org>
next reply other threads:[~2022-11-21 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 23:38 Ricardo Ribalda [this message]
2022-11-21 23:38 ` [PATCH v1 1/1] pinctrl: meditatek: Startup with the IRQs disabled Ricardo Ribalda
2022-11-22 8:34 ` Linus Walleij
2022-11-22 9:23 ` AngeloGioacchino Del Regno
2022-11-22 9:48 ` Matthias Brugger
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=20221122-mtk-pinctrl-v1-0-bedf5655a3d2@chromium.org \
--to=ribalda@chromium.org \
--cc=joel@joelfernandes.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sean.wang@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=zwisler@kernel.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).