All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Van Asbroeck <thesven73@gmail.com>
To: Fabio Estevam <festevam@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:00:12 -0400	[thread overview]
Message-ID: <CAGngYiWXQ2iLMvhbKsVmdoiqSeS7onVWmo4z+dJHhXf1pBT9Uw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5ANnvsJ2iGrQSHiLUpd8RKCEmNZSdAvVFEQpqu8zvpp5Q@mail.gmail.com>

Hi Fabio,

On Tue, Jun 23, 2020 at 10:19 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> You should limit this to imx6 quad plus only, so you would better
> check against "fsl,imx6qp".

Excellent suggestion, thank you ! I tried to determine if running on a plus by
using the method from imx6q_init_machine(). But yes, checking for
"fsl,imx6qp" sounds much more elegant.

WARNING: multiple messages have this Message-ID (diff)
From: Sven Van Asbroeck <thesven73@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1] ARM: imx6plus: enable internal routing of clk_enet_ref where possible
Date: Tue, 23 Jun 2020 11:00:12 -0400	[thread overview]
Message-ID: <CAGngYiWXQ2iLMvhbKsVmdoiqSeS7onVWmo4z+dJHhXf1pBT9Uw@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5ANnvsJ2iGrQSHiLUpd8RKCEmNZSdAvVFEQpqu8zvpp5Q@mail.gmail.com>

Hi Fabio,

On Tue, Jun 23, 2020 at 10:19 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> You should limit this to imx6 quad plus only, so you would better
> check against "fsl,imx6qp".

Excellent suggestion, thank you ! I tried to determine if running on a plus by
using the method from imx6q_init_machine(). But yes, checking for
"fsl,imx6qp" sounds much more elegant.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-06-23 15:00 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
2020-06-23 15:00   ` Sven Van Asbroeck [this message]
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=CAGngYiWXQ2iLMvhbKsVmdoiqSeS7onVWmo4z+dJHhXf1pBT9Uw@mail.gmail.com \
    --to=thesven73@gmail.com \
    --cc=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 \
    /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.