From: Andrey Utkin <andrey_utkin@fastmail.com>
To: mchehab@s-opensource.com, hverkuil@xs4all.nl
Cc: ismael@iodev.co.uk, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, maintainers@bluecherrydvr.com,
andrey.utkin@corp.bluecherry.net
Subject: Re: [PATCH] [media] solo6x10: avoid delayed register write
Date: Mon, 17 Oct 2016 20:52:57 +0100 [thread overview]
Message-ID: <20161017195257.GD21569@stationary.pb.com> (raw)
In-Reply-To: <20160922000331.4193-1-andrey.utkin@corp.bluecherry.net>
On Thu, Sep 22, 2016 at 03:03:31AM +0300, Andrey Utkin wrote:
> This fixes a lockup at device probing which happens on some solo6010
> hardware samples. This is a regression introduced by commit e1ceb25a1569
> ("[media] SOLO6x10: remove unneeded register locking and barriers")
>
> The observed lockup happens in solo_set_motion_threshold() called from
> solo_motion_config().
>
> This extra "flushing" is not fundamentally needed for every write, but
> apparently the code in driver assumes such behaviour at last in some
> places.
>
> Actual fix was proposed by Hans Verkuil.
>
> Signed-off-by: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
> ---
> drivers/media/pci/solo6x10/solo6x10.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/media/pci/solo6x10/solo6x10.h b/drivers/media/pci/solo6x10/solo6x10.h
> index 5bd4987..3f8da5e 100644
> --- a/drivers/media/pci/solo6x10/solo6x10.h
> +++ b/drivers/media/pci/solo6x10/solo6x10.h
> @@ -284,7 +284,10 @@ static inline u32 solo_reg_read(struct solo_dev *solo_dev, int reg)
> static inline void solo_reg_write(struct solo_dev *solo_dev, int reg,
> u32 data)
> {
> + u16 val;
> +
> writel(data, solo_dev->reg_base + reg);
> + pci_read_config_word(solo_dev->pdev, PCI_STATUS, &val);
> }
>
> static inline void solo_irq_on(struct solo_dev *dev, u32 mask)
> --
> 2.9.2
>
Mauro, Hans,
Please pick this up. This has been around for a month, I expected it
would get to v4.9-rc1 easily.
Thanks.
prev parent reply other threads:[~2016-10-17 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 0:03 [PATCH] [media] solo6x10: avoid delayed register write Andrey Utkin
2016-10-17 19:52 ` Andrey Utkin [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=20161017195257.GD21569@stationary.pb.com \
--to=andrey_utkin@fastmail.com \
--cc=andrey.utkin@corp.bluecherry.net \
--cc=hverkuil@xs4all.nl \
--cc=ismael@iodev.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maintainers@bluecherrydvr.com \
--cc=mchehab@s-opensource.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.