From: Simon Horman <horms@verge.net.au>
To: kieran.bingham@ideasonboard.com
Cc: Kieran Bingham <kbingham@kernel.org>,
niklas.soderlund@ragnatech.se, linux-renesas-soc@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH] rcar-vin: Use of_nodes as specified by the subdev
Date: Wed, 26 Apr 2017 10:11:51 +0200 [thread overview]
Message-ID: <20170426081151.GL25517@verge.net.au> (raw)
In-Reply-To: <16f8afab-95c1-cc52-9b79-d04ef862a89d@ideasonboard.com>
On Wed, Apr 26, 2017 at 08:48:25AM +0100, Kieran Bingham wrote:
> Hi Simon,
>
> On 26/04/17 08:23, Simon Horman wrote:
> > Hi Kieran,
> >
> > On Tue, Apr 25, 2017 at 03:55:00PM +0100, Kieran Bingham wrote:
> >> From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> >>
> >> The rvin_digital_notify_bound() call dereferences the subdev->dev
> >> pointer to obtain the of_node. On some error paths, this dev node can be
> >> set as NULL. The of_node is mapped into the subdevice structure on
> >> initialisation, so this is a safer source to compare the nodes.
> >>
> >> Dereference the of_node from the subdev structure instead of the dev
> >> structure.
> >>
> >> Fixes: 83fba2c06f19 ("rcar-vin: rework how subdevice is found and
> >> bound")
> >> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> >> ---
> >> drivers/media/platform/rcar-vin/rcar-core.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/media/platform/rcar-vin/rcar-core.c b/drivers/media/platform/rcar-vin/rcar-core.c
> >> index 5861ab281150..a530dc388b95 100644
> >> --- a/drivers/media/platform/rcar-vin/rcar-core.c
> >> +++ b/drivers/media/platform/rcar-vin/rcar-core.c
> >> @@ -469,7 +469,7 @@ static int rvin_digital_notify_bound(struct v4l2_async_notifier *notifier,
> >>
> >> v4l2_set_subdev_hostdata(subdev, vin);
> >>
> >> - if (vin->digital.asd.match.of.node == subdev->dev->of_node) {
> >> + if (vin->digital.asd.match.of.node == subdev->of_node) {
> >> /* Find surce and sink pad of remote subdevice */
> >>
> >> ret = rvin_find_pad(subdev, MEDIA_PAD_FL_SOURCE);
> >
> > I see two different accesses to subdev->dev->of_node in the version of
> > rcar-core.c in linux-next. So I'm unsure if the following comment makes
> > sense in the context of the version you are working on. It is that
> > I wonder if all accesses to subdev->dev->of_node should be updated.
>
> Yes, all uses in rcar-core should be updated, This patch is targeted directly at
> mainline, in which only one reference occurs.
>
> I presume(?) the references in linux-next, relate to the previous version of
> this patch which I posted as a reply to Niklas' patch series:
> "[PATCH v3 00/27] rcar-vin: Add Gen3 with media controller support"
>
> The first version of this patch (which was titled differently) covered three
> uses, but two of them were not yet in mainline.
>
> The 'fixes' for those references are going to be squashed in to Niklas' next
> version of his patchset.
Understood, sounds good to me.
next prev parent reply other threads:[~2017-04-26 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 14:55 [PATCH] rcar-vin: Use of_nodes as specified by the subdev Kieran Bingham
2017-04-26 7:23 ` Simon Horman
2017-04-26 7:48 ` Kieran Bingham
2017-04-26 8:11 ` Simon Horman [this message]
2017-04-26 9:00 ` Niklas Söderlund
2017-04-26 9:13 ` Simon Horman
2017-04-27 22:49 ` Niklas Söderlund
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=20170426081151.GL25517@verge.net.au \
--to=horms@verge.net.au \
--cc=kbingham@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
/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