From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Mathew McBride <matt@traverse.com.au>
Cc: Leo Li <leoyang.li@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] soc: fsl: select FSL_GUTS driver for DPIO
Date: Thu, 23 Jun 2022 15:24:08 +0000 [thread overview]
Message-ID: <20220623152407.ogqejuwpluxonlbq@skbuf> (raw)
In-Reply-To: <20220620043243.32235-1-matt@traverse.com.au>
On Mon, Jun 20, 2022 at 04:32:43AM +0000, Mathew McBride wrote:
> The soc/fsl/dpio driver will perform a soc_device_match()
> to determine the optimal cache settings for a given CPU core.
>
> If FSL_GUTS is not enabled, this search will fail and
> the driver will not configure cache stashing for the given
> DPIO, and a string of "unknown SoC" messages will appear:
>
> fsl_mc_dpio dpio.7: unknown SoC version
> fsl_mc_dpio dpio.6: unknown SoC version
> fsl_mc_dpio dpio.5: unknown SoC version
>
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> Fixes: 51da14e96e9b ("soc: fsl: dpio: configure cache stashing destination")
> Cc: stable@vger.kernel.org
Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Ioana Ciornei <ioana.ciornei@nxp.com>
To: Mathew McBride <matt@traverse.com.au>
Cc: Leo Li <leoyang.li@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] soc: fsl: select FSL_GUTS driver for DPIO
Date: Thu, 23 Jun 2022 15:24:08 +0000 [thread overview]
Message-ID: <20220623152407.ogqejuwpluxonlbq@skbuf> (raw)
In-Reply-To: <20220620043243.32235-1-matt@traverse.com.au>
On Mon, Jun 20, 2022 at 04:32:43AM +0000, Mathew McBride wrote:
> The soc/fsl/dpio driver will perform a soc_device_match()
> to determine the optimal cache settings for a given CPU core.
>
> If FSL_GUTS is not enabled, this search will fail and
> the driver will not configure cache stashing for the given
> DPIO, and a string of "unknown SoC" messages will appear:
>
> fsl_mc_dpio dpio.7: unknown SoC version
> fsl_mc_dpio dpio.6: unknown SoC version
> fsl_mc_dpio dpio.5: unknown SoC version
>
> Signed-off-by: Mathew McBride <matt@traverse.com.au>
> Fixes: 51da14e96e9b ("soc: fsl: dpio: configure cache stashing destination")
> Cc: stable@vger.kernel.org
Reviewed-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Thanks!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-23 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 4:32 [PATCH] soc: fsl: select FSL_GUTS driver for DPIO Mathew McBride
2022-06-20 4:32 ` Mathew McBride
2022-06-23 15:24 ` Ioana Ciornei [this message]
2022-06-23 15:24 ` Ioana Ciornei
2022-09-01 5:21 ` [PATCH 0/1 RESEND] update Kconfig for DPIO to select FSL_GUTS Mathew McBride
2022-09-01 5:21 ` Mathew McBride
2022-09-01 5:21 ` [PATCH 1/1 RESEND] soc: fsl: select FSL_GUTS driver for DPIO Mathew McBride
2022-09-01 5:21 ` Mathew McBride
2022-09-02 11:00 ` patchwork-bot+linux-soc
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=20220623152407.ogqejuwpluxonlbq@skbuf \
--to=ioana.ciornei@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=matt@traverse.com.au \
--cc=stable@vger.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.