All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Chanho Park <chanho61.park@samsung.com>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	"linux-samsung-soc@vger.kernel.org" 
	<linux-samsung-soc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Tomasz Figa <tomasz.figa@gmail.com>
Subject: Exynos850 and ExynosAuto v9 pinctrl wakeup muxed interrupt
Date: Thu, 30 Dec 2021 20:34:51 +0100	[thread overview]
Message-ID: <3c0087a9-5c3b-d665-136e-6110a0482775@canonical.com> (raw)

Hi Chanho and Sam,

I am slowly finishing dtschema for Samsung pinctrl drivers [1] and I
noticed that Exynos850 and Auto v9 do not define interrupt in pinctrl
node with: wakeup-interrupt-controller. This is an interrupt muxing
several external wakeup interrupts, e.g. EINT16 - EINT31.

For Exynos5433 this looks like:
https://elixir.bootlin.com/linux/latest/source/arch/arm64/boot/dts/exynos/exynos5433.dtsi#L857

Missing muxed interrupt for Exynos850 and Autov9 might be fine, although
you should see in dmesg error log like:
    "irq number for muxed EINTs not found"

Can you check that your wakeup-interrupt-controller is properly defined
in DTSI? If yes, I will need to include such differences in the dtschema.

[1] https://github.com/krzk/linux/tree/n/dt-bindings-samsung-pinctrl-schema

Best regards,
Krzysztof

             reply	other threads:[~2021-12-30 19:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 19:34 Krzysztof Kozlowski [this message]
2021-12-30 19:42 ` Exynos850 and ExynosAuto v9 pinctrl wakeup muxed interrupt Krzysztof Kozlowski
2022-01-03 20:59 ` Sam Protsenko
2022-01-07  8:16   ` Krzysztof Kozlowski
2022-01-10  7:54     ` Chanho Park
2022-01-11 13:17       ` Krzysztof Kozlowski
2022-01-14 20:32     ` Sam Protsenko
2022-01-15 15:46       ` Krzysztof Kozlowski
2022-01-15 20:38         ` Sam Protsenko
2022-01-16 17:15           ` Krzysztof Kozlowski
2022-01-16 22:56             ` Sam Protsenko

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=3c0087a9-5c3b-d665-136e-6110a0482775@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=chanho61.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=semen.protsenko@linaro.org \
    --cc=tomasz.figa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.