From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2,1/3] meson_uart: expose CLKID_UARTx
Date: Fri, 31 Mar 2017 17:37:37 +0200 [thread overview]
Message-ID: <1490974657.12951.5.camel@baylibre.com> (raw)
In-Reply-To: <m2y3vn6dhk.fsf@baylibre.com>
On Wed, 2017-03-29 at 13:21 -0700, Kevin Hilman wrote:
> Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
>
> [...]
>
> > for Helmut this would mean that instead of dropping this patch (or
> > dropping CLKID_UART1 and CLKID_UART2 from this patch) he would rather
> > have to *add* another patch (for meson-gxbb.dtsi and meson-gxl.dtsi)
> > which passes the core clocks to the corresponding UART controllers
> > (similar to the CLKID_SD_EMMC_ clocks).
>
> Yes, this is what I would like to see.
>
> If a new CLKID is exposed, I want to see the users of it at the same
> time.
Helmut,
If you send another version of these patches, considering the feedback of Kevin
and Martin, could you please change the subject of this patch to:
dt-bindings: clock: gxbb: expose?UART clocks
Thx
Jerome
>
> Kevin
next prev parent reply other threads:[~2017-03-31 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 9:25 [PATCH v2, 0/3] tty/serial: meson_uart: add support for core clock handling Helmut Klein
2017-03-28 9:25 ` [PATCH v2,1/3] meson_uart: expose CLKID_UARTx Helmut Klein
2017-03-28 15:51 ` Jerome Brunet
2017-03-28 18:18 ` Helmut Klein
2017-03-28 19:14 ` Jerome Brunet
2017-03-28 21:24 ` Martin Blumenstingl
2017-03-29 6:21 ` Jerome Brunet
2017-03-29 20:21 ` Kevin Hilman
2017-03-31 15:37 ` Jerome Brunet [this message]
2017-03-31 17:03 ` Helmut Klein
2017-03-28 9:25 ` [PATCH v2, 2/3] tty/serial: meson_uart: add documentation for the dt-bindings Helmut Klein
2017-03-28 10:05 ` Mark Rutland
2017-03-28 18:20 ` Helmut Klein
2017-03-28 9:25 ` [PATCH v2, 3/3] tty/serial: meson_uart: add the core clock handling to the driver Helmut Klein
2017-03-28 19:16 ` Jerome Brunet
2017-03-29 9:47 ` Helmut Klein
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=1490974657.12951.5.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@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