From: Philipp Zabel <p.zabel@pengutronix.de>
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
Steve Longerbeam <steve_longerbeam@mentor.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] gpu: ipu-v3: Fix CSI selection for VDIC
Date: Tue, 06 Jun 2017 10:22:56 +0200 [thread overview]
Message-ID: <1496737376.2966.5.camel@pengutronix.de> (raw)
In-Reply-To: <1496516241-28277-1-git-send-email-steve_longerbeam@mentor.com>
On Sat, 2017-06-03 at 11:57 -0700, Steve Longerbeam wrote:
> From: Marek Vasut <marex@denx.de>
>
> The description of the CSI_SEL bit in the i.MX6 reference manual is
> incorrect. It states "This bit defines which CSI is the input to the
> IC. This bit is effective only if IC_INPUT is bit cleared".
>
> From experiment it was found this is in fact not correct. The CSI_SEL
> bit selects which CSI is input to _both_ the VDIC _and_ the IC. If the
> IC_INPUT bit is set so that the IC is receiving from the VDIC, the IC
> ignores the CSI_SEL bit, but CSI_SEL still selects which CSI the VDIC
> receives from in that case.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Signed-off-by: Steve Longerbeam <steve_longerbeam@mentor.com>
> ---
> drivers/gpu/ipu-v3/ipu-common.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/ipu-v3/ipu-common.c b/drivers/gpu/ipu-v3/ipu-common.c
> index 16d5568..2fb5f43 100644
> --- a/drivers/gpu/ipu-v3/ipu-common.c
> +++ b/drivers/gpu/ipu-v3/ipu-common.c
> @@ -725,15 +725,16 @@ void ipu_set_ic_src_mux(struct ipu_soc *ipu, int csi_id, bool vdi)
> spin_lock_irqsave(&ipu->lock, flags);
>
> val = ipu_cm_read(ipu, IPU_CONF);
> - if (vdi) {
> + if (vdi)
> val |= IPU_CONF_IC_INPUT;
> - } else {
> + else
> val &= ~IPU_CONF_IC_INPUT;
> - if (csi_id == 1)
> - val |= IPU_CONF_CSI_SEL;
> - else
> - val &= ~IPU_CONF_CSI_SEL;
> - }
> +
> + if (csi_id == 1)
> + val |= IPU_CONF_CSI_SEL;
> + else
> + val &= ~IPU_CONF_CSI_SEL;
> +
> ipu_cm_write(ipu, val, IPU_CONF);
>
> spin_unlock_irqrestore(&ipu->lock, flags);
Applied, thanks.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-06-06 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 18:57 [PATCH] gpu: ipu-v3: Fix CSI selection for VDIC Steve Longerbeam
2017-06-06 8:22 ` Philipp Zabel [this message]
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=1496737376.2966.5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=marex@denx.de \
--cc=slongerbeam@gmail.com \
--cc=steve_longerbeam@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox