All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] ARM: imx6plus: enable internal routing of clk_enet_ref where possible
Date: Tue, 23 Jun 2020 11:19:25 -0300	[thread overview]
Message-ID: <CAOMZO5ANnvsJ2iGrQSHiLUpd8RKCEmNZSdAvVFEQpqu8zvpp5Q@mail.gmail.com> (raw)
In-Reply-To: <20200613201703.16788-1-TheSven73@gmail.com>

Hi Sven,

On Sat, Jun 13, 2020 at 5:17 PM Sven Van Asbroeck <thesven73@gmail.com> wrote:

> +       /*
> +        * On imx6 plus, enet_ref from ANATOP/CCM can be internally routed to
> +        * be the PTP clock source, instead of having to be routed through
> +        * pads.
> +        * Board designs which route the ANATOP/CCM clock through pads are
> +        * unaffected when routing happens internally. So on these designs,
> +        * route internally by default.
> +        */
> +       if (clksel == IMX6Q_GPR1_ENET_CLK_SEL_ANATOP && cpu_is_imx6q() &&
> +                       imx_get_soc_revision() >= IMX_CHIP_REVISION_2_0) {

You should limit this to imx6 quad plus only, so you would better
check against "fsl,imx6qp".

  parent reply	other threads:[~2020-06-23 14:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 20:17 [PATCH v1] ARM: imx6plus: enable internal routing of clk_enet_ref where possible Sven Van Asbroeck
2020-06-13 20:17 ` Sven Van Asbroeck
2020-06-23 11:53 ` Shawn Guo
2020-06-24  1:40   ` [EXT] " Andy Duan
2020-06-24  1:40     ` Andy Duan
2020-06-24  2:56     ` Sven Van Asbroeck
2020-06-24  2:56       ` Sven Van Asbroeck
2020-06-24  3:46       ` Andy Duan
2020-06-24  3:46         ` Andy Duan
2020-06-23 14:19 ` Fabio Estevam [this message]
2020-06-23 15:00   ` Sven Van Asbroeck
2020-06-23 15:00     ` Sven Van Asbroeck

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=CAOMZO5ANnvsJ2iGrQSHiLUpd8RKCEmNZSdAvVFEQpqu8zvpp5Q@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=thesven73@gmail.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.