From: <Claudiu.Beznea@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<robh+dt@kernel.org>, <mark.rutland@arm.com>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] add slow clock support for SAM9X60
Date: Thu, 14 Feb 2019 11:39:40 +0000 [thread overview]
Message-ID: <0d330ff8-e8f4-d157-299c-da181be4a0fd@microchip.com> (raw)
In-Reply-To: <1550140748-21714-1-git-send-email-claudiu.beznea@microchip.com>
Hi,
Please ignore this series. I'll resend a new one better formating the patches.
Thank you,
Claudiu Beznea
On 14.02.2019 12:39, Claudiu Beznea - M18063 wrote:
> From: Claudiu Beznea <claudiu.beznea@microchip.com>
>
> Hi,
>
> This series add slow clock support for SAM9X60. Apart from previous IPs, this
> one uses different offsets in control register for different functionalities.
> The series adapt current driver to work for all IPs using per IP
> configurations initialized at probe.
>
> Thank you,
> Claudiu Beznea
>
> Claudiu Beznea (2):
> clk: at91: sckc: adapt sckc driver to work for SAM9X60
> dt-bindings: clk: at91: add bindings for SAM9X60's slow clock
> controller
>
> .../devicetree/bindings/clock/at91-clock.txt | 3 +-
> drivers/clk/at91/sckc.c | 142 ++++++++++++++++-----
> 2 files changed, 109 insertions(+), 36 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-14 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 10:39 [PATCH 0/2] add slow clock support for SAM9X60 Claudiu.Beznea
2019-02-14 10:39 ` [PATCH 1/2] clk: at91: sckc: adapt sckc driver to work " Claudiu.Beznea
2019-02-14 10:39 ` [PATCH 2/2] dt-bindings: clk: at91: add bindings for SAM9X60's slow clock controller Claudiu.Beznea
2019-02-14 11:39 ` Claudiu.Beznea [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=0d330ff8-e8f4-d157-299c-da181be4a0fd@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).