linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: davidcdueck@googlemail.com (David Dueck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 0/2] RT-Preempt on SAMA5
Date: Fri,  3 Jul 2015 17:28:41 +0200	[thread overview]
Message-ID: <1435937323-16913-1-git-send-email-davidcdueck@googlemail.com> (raw)

RT-Preempt crashes early at boot on SAMA5. The reason is that
drivers/clk/at91/* is using interrupts very early, before kthreadd is up.

Just making those IRQF_NOTHREAD is not an option as the handlers are taking
spin locks.

Perhaps we can have some discussion on how to go on with this.
Is there some problem if we just do not use interrupts here anymore?
(at least for the clocks that are needed very early)

The patches are on top of the RT patches for 4.0. The second
patch might not be needed if we just drop the RT patch that touches
the PIT code.

David Dueck (2):
  at91: make using irqs for clock handling optional
  at91: use request_irq/free_irq instead of setup_irq/remove_irq

 drivers/clk/Kconfig                   |  1 +
 drivers/clk/at91/Kconfig              |  4 ++
 drivers/clk/at91/clk-main.c           | 34 ++++++++++++++++
 drivers/clk/at91/clk-master.c         | 11 +++++
 drivers/clk/at91/clk-pll.c            | 11 ++++-
 drivers/clk/at91/clk-system.c         | 11 +++++
 drivers/clk/at91/clk-utmi.c           | 10 +++++
 drivers/clk/at91/pmc.c                |  6 +++
 drivers/clocksource/timer-atmel-pit.c | 76 ++++++++++++++++++-----------------
 9 files changed, 127 insertions(+), 37 deletions(-)
 create mode 100644 drivers/clk/at91/Kconfig

-- 
2.4.4

                 reply	other threads:[~2015-07-03 15:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1435937323-16913-1-git-send-email-davidcdueck@googlemail.com \
    --to=davidcdueck@googlemail.com \
    --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).