linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: linux-renesas-soc@vger.kernel.org,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: [PATCH 0/2] max9286: Refactor V4L2 support to prevent EPROBE_DEFER failures
Date: Wed, 12 Feb 2020 17:37:25 +0000	[thread overview]
Message-ID: <20200212173727.19476-1-kieran.bingham+renesas@ideasonboard.com> (raw)

Currently the V4L2 notifiers are registered during DT parsing.

Move this handling and all other V4L2 code to two distinct implementations and
contained higher in the source code.  This simplifies the hardware
initialisation functions, and makes error paths and cleanup much easier to
parse.

I hope to squash these two patches into the max9286 and then post a v7, along
with Jacopo's RDACM20 split work, with an aim to hopefully getting upstream
integration.


max9286 v7 changlog currently looks like:

    v7:
     [Kieran]
     - Ensure powerdown lines are optional
     - Add a 4ms power-up delay
     - Add max9286_check_config_link() to core
     - Add GPIO chip controller for GPIO0OUT and GPIO1OUT
     - Fix GPIO registration
    
     [Jacopo]
     - Remove redundanct MAXIM_I2C_SPEED macros
     - Move notifiers operations
     - Add delay after reverse channel reconfiguration
     - Move link setup to completion
     - Fix up max9286_check_config_link() implementation
     - Remove redundant dual configuration of reverse channel


Kieran Bingham (2):
  max9286: Split out async registration
  max9286: Collect all V4L2 registrations

 drivers/media/i2c/max9286.c | 205 ++++++++++++++++++++++--------------
 1 file changed, 127 insertions(+), 78 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-02-12 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 17:37 Kieran Bingham [this message]
2020-02-12 17:37 ` [PATCH 1/2] max9286: Split out async registration Kieran Bingham
2020-02-12 17:39   ` Kieran Bingham
2020-02-13  9:46   ` Jacopo Mondi
2020-02-13 10:07     ` Kieran Bingham
2020-02-13 10:15       ` Kieran Bingham
2020-02-13 10:20       ` Jacopo Mondi
2020-02-13 10:27         ` Kieran Bingham
2020-02-13 11:41           ` Jacopo Mondi
2020-02-12 17:37 ` [PATCH 2/2] max9286: Collect all V4L2 registrations Kieran Bingham
2020-02-13 10:21 ` [PATCH] max9286: balance v4l2_async refcnting Kieran Bingham
2020-02-13 13:06   ` Kieran Bingham
2020-02-13 13:11     ` Jacopo Mondi
2020-02-13 13:28       ` Kieran Bingham

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=20200212173727.19476-1-kieran.bingham+renesas@ideasonboard.com \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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;
as well as URLs for NNTP newsgroup(s).