From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "Jerome Brunet" <jbrunet@baylibre.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Kevin Hilman" <khilman@baylibre.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH 2/2] pwm: meson: omit video/hdmi clock as mux parent
Date: Tue, 11 Apr 2023 19:09:40 +0200 [thread overview]
Message-ID: <CAFBinCBtxQvDX8OSjACqRbFfM-DUtb5PoPp4Cwv4Q6PD8j0_gg@mail.gmail.com> (raw)
In-Reply-To: <a3fb613f-73d4-c9c7-f48f-ffd79fa654aa@gmail.com>
Hi Heiner,
On Sat, Apr 8, 2023 at 10:43 PM Heiner Kallweit <hkallweit1@gmail.com> wrote:
[...]
> + if (meson->data->omit_video_clock_parent)
> + channel->mux.table = (u32[]){ 0, 2, 3 };
Most likely it won't be relevant anymore once we switch to
clk_parent_data but this part of the code is currently a no-op.
A few lines below there's an unconditional assignment of
channel->mux.table = NULL;
Best regards,
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-04-11 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 20:40 [PATCH 0/2] pwm: meson: make full use of common clock framework Heiner Kallweit
2023-04-08 20:41 ` [PATCH 1/2] " Heiner Kallweit
2023-04-10 23:27 ` Martin Blumenstingl
2023-04-11 6:34 ` Heiner Kallweit
2023-04-08 20:43 ` [PATCH 2/2] pwm: meson: omit video/hdmi clock as mux parent Heiner Kallweit
2023-04-11 17:09 ` Martin Blumenstingl [this message]
2023-04-10 22:15 ` [PATCH 0/2] pwm: meson: make full use of common clock framework Martin Blumenstingl
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=CAFBinCBtxQvDX8OSjACqRbFfM-DUtb5PoPp4Cwv4Q6PD8j0_gg@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.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
all inboxes | Powered by JetHome®