From: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
To: ssantosh@kernel.org, s-anna@ti.com
Cc: grzegorz.jaszczyk@linaro.org, santosh.shilimkar@oracle.com,
robh+dt@kernel.org, lee.jones@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
praneeth@ti.com, tony@atomide.com
Subject: [PATCH 0/2] Extend TI PRUSS platform driver
Date: Thu, 3 Sep 2020 20:41:39 +0200 [thread overview]
Message-ID: <1599158501-8302-1-git-send-email-grzegorz.jaszczyk@linaro.org> (raw)
Hi,
This patch-set extends TI PRUSS platform driver about CORECLK_MUX and
IEPCLK_MUX support. The corresponding dt-binding is updated accordingly.
This patch series depends on TI PRUSS platform driver patchset [1].
[1] https://patchwork.kernel.org/cover/11729645/
Grzegorz Jaszczyk (2):
dt-bindings: soc: ti: Update TI PRUSS bindings regarding clock-muxes
soc: ti: pruss: support CORECLK_MUX and IEPCLK_MUX
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 121 +++++++++++++-
drivers/soc/ti/pruss.c | 184 ++++++++++++++++++++-
include/linux/pruss_driver.h | 6 +
3 files changed, 303 insertions(+), 8 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
To: ssantosh@kernel.org, s-anna@ti.com
Cc: devicetree@vger.kernel.org, grzegorz.jaszczyk@linaro.org,
praneeth@ti.com, santosh.shilimkar@oracle.com,
linux-kernel@vger.kernel.org, tony@atomide.com,
robh+dt@kernel.org, linux-omap@vger.kernel.org,
lee.jones@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Extend TI PRUSS platform driver
Date: Thu, 3 Sep 2020 20:41:39 +0200 [thread overview]
Message-ID: <1599158501-8302-1-git-send-email-grzegorz.jaszczyk@linaro.org> (raw)
Hi,
This patch-set extends TI PRUSS platform driver about CORECLK_MUX and
IEPCLK_MUX support. The corresponding dt-binding is updated accordingly.
This patch series depends on TI PRUSS platform driver patchset [1].
[1] https://patchwork.kernel.org/cover/11729645/
Grzegorz Jaszczyk (2):
dt-bindings: soc: ti: Update TI PRUSS bindings regarding clock-muxes
soc: ti: pruss: support CORECLK_MUX and IEPCLK_MUX
.../devicetree/bindings/soc/ti/ti,pruss.yaml | 121 +++++++++++++-
drivers/soc/ti/pruss.c | 184 ++++++++++++++++++++-
include/linux/pruss_driver.h | 6 +
3 files changed, 303 insertions(+), 8 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-03 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 18:41 Grzegorz Jaszczyk [this message]
2020-09-03 18:41 ` [PATCH 0/2] Extend TI PRUSS platform driver Grzegorz Jaszczyk
2020-09-03 18:41 ` [PATCH 1/2] dt-bindings: soc: ti: Update TI PRUSS bindings regarding clock-muxes Grzegorz Jaszczyk
2020-09-03 18:41 ` Grzegorz Jaszczyk
2020-09-03 18:41 ` [PATCH 2/2] soc: ti: pruss: support CORECLK_MUX and IEPCLK_MUX Grzegorz Jaszczyk
2020-09-03 18:41 ` Grzegorz Jaszczyk
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=1599158501-8302-1-git-send-email-grzegorz.jaszczyk@linaro.org \
--to=grzegorz.jaszczyk@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=tony@atomide.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.