From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: imx51: Configure M4IF to avoid visual artifacts
Date: Fri, 06 Jul 2018 18:18:33 +0200 [thread overview]
Message-ID: <1530893913.15725.14.camel@pengutronix.de> (raw)
In-Reply-To: <1530720842-28281-2-git-send-email-festevam@gmail.com>
Am Mittwoch, den 04.07.2018, 13:14 -0300 schrieb Fabio Estevam:
> From: Fabio Estevam <fabio.estevam@nxp.com>
>
> Configure the M4IF registers as per the vendor bootloader
> to avoid visual artifacts during video playback.
>
> This way we don't need to rely on the bootloader configuration for
> optimal IPU/VPU bus priorities.
>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Reviewed-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> ?arch/arm/mach-imx/mach-imx51.c | 29 ++++++++++++++++++++++++++++-
> ?1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/mach-imx51.c b/arch/arm/mach-imx/mach-
> imx51.c
> index 3835b6a..37ffdfa 100644
> --- a/arch/arm/mach-imx/mach-imx51.c
> +++ b/arch/arm/mach-imx/mach-imx51.c
> @@ -12,6 +12,7 @@
> ?
> ?#include <linux/io.h>
> ?#include <linux/irq.h>
> +#include <linux/of_address.h>
> ?#include <linux/of_irq.h>
> ?#include <linux/of_platform.h>
> ?#include <asm/mach/arch.h>
> @@ -48,11 +49,37 @@ static void __init imx51_ipu_mipi_setup(void)
> ? iounmap(hsc_addr);
> ?}
> ?
> +static void __init imx51_m4if_setup(void)
> +{
> + void __iomem *m4if_base;
> + struct device_node *np;
> +
> + np = of_find_compatible_node(NULL, NULL, "fsl,imx51-m4if");
> + if (!np)
> + return;
> +
> + m4if_base = of_iomap(np, 0);
> + if (!m4if_base) {
> + pr_err("Unable to map M4IF registers\n");
> + return;
> + }
> +
> + /*
> + ?* Configure VPU and IPU with higher priorities
> + ?* in order to avoid artifacts during video playback
> + ?*/
> + writel_relaxed(0x00000203, m4if_base + 0x40);
> + writel_relaxed(0x00000000, m4if_base + 0x44);
> + writel_relaxed(0x00120125, m4if_base + 0x9c);
> + writel_relaxed(0x001901A3, m4if_base + 0x48);
> + iounmap(m4if_base);
> +}
> +
> ?static void __init imx51_dt_init(void)
> ?{
> ? imx51_ipu_mipi_setup();
> ? imx_src_init();
> -
> + imx51_m4if_setup();
> ? imx_aips_allow_unprivileged_access("fsl,imx51-aipstz");
> ?}
> ?
next prev parent reply other threads:[~2018-07-06 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 16:14 [PATCH 1/2] ARM: dts: imx51: Add M4IF support Fabio Estevam
2018-07-04 16:14 ` [PATCH 2/2] ARM: imx51: Configure M4IF to avoid visual artifacts Fabio Estevam
2018-07-04 18:26 ` Sergey Lapin
2018-07-06 16:18 ` Lucas Stach [this message]
2018-07-04 18:25 ` [PATCH 1/2] ARM: dts: imx51: Add M4IF support Sergey Lapin
2018-07-06 16:17 ` Lucas Stach
2018-07-09 18:26 ` Fabio Estevam
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=1530893913.15725.14.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).