From: "Sam Shih (史碩三)" <Sam.Shih@mediatek.com>
To: "u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>
Cc: "daniel@makrotopia.org" <daniel@makrotopia.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] pwm: mediatek: Add support for MT7986
Date: Thu, 24 Nov 2022 04:47:03 +0000 [thread overview]
Message-ID: <ca3283fbe762db7c7f665eda15e807d7207bb578.camel@mediatek.com> (raw)
In-Reply-To: <20221117115624.t2kbwscxvkvffo7x@pengutronix.de>
Hi Uwe,
Sorry for the late reply.
Since the CK_26M_SEL register does exist on MT7986, and for the other
mediatek SoCs, we should update the value of the CK_26M_SEL register if
it exists on the SoC, even the MT7986's PWM hardware just bypasses this
setting.
From this point of view, I think it is fine to mark '.has_ck_26m_sel'
attribute to 'true'.
For this patch:
Reviewed-by: Sam Shih <sam.shih@mediatek.com>
Thanks,
Best Regards,
Sam Shih
On Thu, 2022-11-17 at 12:56 +0100, Uwe Kleine-König wrote:
> On Tue, Oct 25, 2022 at 02:35:43PM +0800, Sam Shih wrote:
> > Hi Daniel:
> >
> > On Fri, 2022-10-21 at 16:24 +0100, Daniel Golle wrote:
> > > Add support for PWM on MT7986 which has 2 PWM channels, one of
> > > them
> > > is
> > > typically used for a temperature controlled fan.
> > >
> > > Signed-off-by: Daniel Golle <daniel@makrotopia.org>
> > > ---
> > > drivers/pwm/pwm-mediatek.c | 7 +++++++
> > > 1 file changed, 7 insertions(+)
> > >
> > > diff --git a/drivers/pwm/pwm-mediatek.c b/drivers/pwm/pwm-
> > > mediatek.c
> > > index 6901a44dc428de..2219cba033e348 100644
> > > --- a/drivers/pwm/pwm-mediatek.c
> > > +++ b/drivers/pwm/pwm-mediatek.c
> > > @@ -329,6 +329,12 @@ static const struct pwm_mediatek_of_data
> > > mt8365_pwm_data = {
> > > .has_ck_26m_sel = true,
> > > };
> > >
> > > +static const struct pwm_mediatek_of_data mt7986_pwm_data = {
> > > + .num_pwms = 2,
> > > + .pwm45_fixup = false,
> > > + .has_ck_26m_sel = true,
> >
> > For MT7986 SoC, I think the value of "has_ck_26m_sel" should be
> > 'false'
>
> The status of the discussion isn't clear to me. You didn't visibly
> agree
> which value is right now. Will there be a v2 of this patch? Or is it
> expected to be picked up as is.
>
> From my side (i.e. not having checked the hw details just judging
> with
> the PWM hat on) the patch is fine.
>
> Best regards
> Uwe
>
prev parent reply other threads:[~2022-11-24 5:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 15:24 [PATCH 1/2] pwm: mediatek: Add support for MT7986 Daniel Golle
2022-10-25 6:35 ` Sam Shih
2022-10-25 11:57 ` Daniel Golle
2022-10-26 6:17 ` Sam Shih
2022-10-26 10:00 ` Daniel Golle
2022-11-17 11:56 ` Uwe Kleine-König
2022-11-17 14:23 ` Daniel Golle
2022-11-24 4:47 ` Sam Shih (史碩三) [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=ca3283fbe762db7c7f665eda15e807d7207bb578.camel@mediatek.com \
--to=sam.shih@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@gmail.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