From: Claudiu Beznea <claudiu.beznea@microchip.com>
To: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com>,
<robh+dt@kernel.org>, <nicolas.ferre@microchip.com>,
<ludovic.desroches@microchip.com>, <tglx@linutronix.de>,
<jason@lakedaemon.net>, <maz@kernel.org>
Cc: <linux-rtc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: [PATCH v2 0/3] add RTT support for SAM9X60
Date: Wed, 10 Jun 2020 12:05:33 +0300 [thread overview]
Message-ID: <1591779936-18577-1-git-send-email-claudiu.beznea@microchip.com> (raw)
This series adds RTT support for SAM9X60.
Changes in v2:
- use "atmel,at91sam9260-rtt" as fallback for compatible
- in patch 1 keep only the addition of sam9x60_aic_irq_fixup
- get rid of patches 2/5 from v1
- squash patches 4/5, 5/5 from v1
- change commit title for patch "rtc: at91sam9: add microchip,sam9x60-rtt"
from v1 into "dt-bindings: rtc: add microchip,sam9x60-rtt" and
place it before device tree patch
Claudiu Beznea (3):
irqchip/atmel-aic5: add support for sam9x60 rtt fixup
dt-bindings: rtc: add microchip,sam9x60-rtt
ARM: dts: sam9x60: add rtt
Documentation/devicetree/bindings/rtc/atmel,at91sam9-rtc.txt | 4 +++-
arch/arm/boot/dts/at91-sam9x60ek.dts | 9 +++++++++
arch/arm/boot/dts/sam9x60.dtsi | 7 +++++++
drivers/irqchip/irq-atmel-aic5.c | 8 +++++++-
4 files changed, 26 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2020-06-10 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 9:05 Claudiu Beznea [this message]
2020-06-10 9:05 ` [PATCH v2 1/3] irqchip/atmel-aic5: add support for sam9x60 rtt fixup Claudiu Beznea
2020-06-26 20:38 ` Alexandre Belloni
2020-06-10 9:05 ` [PATCH v2 2/3] dt-bindings: rtc: add microchip,sam9x60-rtt Claudiu Beznea
2020-06-17 22:22 ` Rob Herring
2020-06-10 9:05 ` [PATCH v2 3/3] ARM: dts: sam9x60: add rtt Claudiu Beznea
2020-06-26 20:44 ` [PATCH v2 0/3] add RTT support for SAM9X60 Alexandre Belloni
2020-06-27 11:08 ` Marc Zyngier
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=1591779936-18577-1-git-send-email-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=maz@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
/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).