From: Stephen Boyd <sboyd@kernel.org>
To: "kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Anson Huang <anson.huang@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH] clk: imx6sl: ensure MMDC CH0 handshake is bypassed
Date: Fri, 30 Nov 2018 00:10:20 -0800 [thread overview]
Message-ID: <154356542041.88331.1938476424482018533@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <DB3PR0402MB3916F9DC4C054747211EB90FF5D30@DB3PR0402MB3916.eurprd04.prod.outlook.com>
Quoting Anson Huang (2018-11-29 23:37:14)
> Hi, Stephen
>
> Best Regards!
> Anson Huang
>
> > -----Original Message-----
> > From: Stephen Boyd [mailto:sboyd@kernel.org]
> > Sent: 2018年11月30日 15:25
> > To: kernel@pengutronix.de; linux-arm-kernel@lists.infradead.org;
> > linux-clk@vger.kernel.org; linux-kernel@vger.kernel.org;
> > mturquette@baylibre.com; s.hauer@pengutronix.de; shawnguo@kernel.org;
> > Anson Huang <anson.huang@nxp.com>; Fabio Estevam
> > <fabio.estevam@nxp.com>
> > Cc: dl-linux-imx <linux-imx@nxp.com>
> > Subject: Re: [PATCH] clk: imx6sl: ensure MMDC CH0 handshake is bypassed
> >
> > Quoting Anson Huang (2018-11-29 23:23:47)
> > > Same as other i.MX6 SoCs, ensure unused MMDC channel's handshake is
> > > bypassed, this is to make sure no request signal will be generated
> > > when periphe_clk_sel is changed or SRC warm reset is triggered.
> > >
> > > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> >
> > Does this need a fixes tag?
>
> Normally this bit is 1b'1 by reset, but during our development, it used to be
> overwritten in u-boot and lead to some clock operation fail in Linux kernel, that is why we ensure it
> in clock driver early phase. IMO, it should be OK to not add a fix tag, since it is just
> to make sure the setting is correct and NOT depends on the hardware reset value which
> could be changed in u-boot.
>
>
Hmm ok.
next prev parent reply other threads:[~2018-11-30 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:23 Anson Huang
2018-11-30 7:25 ` Stephen Boyd
2018-11-30 7:37 ` Anson Huang
2018-11-30 8:10 ` Stephen Boyd [this message]
2018-12-10 19:34 ` Stephen Boyd
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=154356542041.88331.1938476424482018533@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=anson.huang@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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
all inboxes | Powered by JetHome®