From: Stefan Wahren <stefan.wahren@i2se.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
Stefan Wahren <stefan.wahren@i2se.com>,
Takashi Iwai <tiwai@suse.de>, Eric Anholt <eric@anholt.net>,
linux-arm-kernel@lists.infradead.org,
Dave Stevenson <dave.stevenson@raspberrypi.org>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: [PATCH 00/10] staging: vc04_services: Improve driver load/unload
Date: Thu, 6 Dec 2018 19:28:50 +0100 [thread overview]
Message-ID: <1544120940-13716-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series improves the load/unload of bcm2835 camera and audio
drivers.
Changes since RFC:
- rebase on current staging-next
- add Nicolas' reviewed-by
- address Dan Carpenter's comments about error handling of device registration
Stefan Wahren (10):
staging: bcm2835-camera: Abort probe if there is no camera
staging: bcm2835-camera: fix module autoloading
staging: bcm2835-camera: Move module info to the end
staging: vchiq_arm: Fix camera device registration
staging: vchiq_arm: Register a platform device for audio
staging: bcm2835-audio: Enable compile test
staging: bcm2835-audio: use module_platform_driver() macro
staging: bcm2835-audio: Drop DT dependency
staging: bcm2835-camera: Provide more specific probe error messages
staging: bcm2835-camera: Add hint about possible faulty config
.../staging/vc04_services/bcm2835-audio/Kconfig | 2 +-
.../staging/vc04_services/bcm2835-audio/bcm2835.c | 51 +++-----------
.../vc04_services/bcm2835-camera/bcm2835-camera.c | 78 +++++++++++++++-------
.../vc04_services/bcm2835-camera/mmal-vchiq.c | 5 +-
.../vc04_services/interface/vchiq_arm/vchiq_arm.c | 29 +++++++-
5 files changed, 95 insertions(+), 70 deletions(-)
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2018-12-06 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 18:28 Stefan Wahren [this message]
2018-12-06 18:28 ` [PATCH 01/10] staging: bcm2835-camera: Abort probe if there is no camera Stefan Wahren
2018-12-06 18:28 ` [PATCH 02/10] staging: bcm2835-camera: fix module autoloading Stefan Wahren
2018-12-06 18:28 ` [PATCH 03/10] staging: bcm2835-camera: Move module info to the end Stefan Wahren
2018-12-06 18:28 ` [PATCH 04/10] staging: vchiq_arm: Fix camera device registration Stefan Wahren
2018-12-06 18:28 ` [PATCH 05/10] staging: vchiq_arm: Register a platform device for audio Stefan Wahren
2018-12-06 18:28 ` [PATCH 06/10] staging: bcm2835-audio: Enable compile test Stefan Wahren
2018-12-06 18:28 ` [PATCH 07/10] staging: bcm2835-audio: use module_platform_driver() macro Stefan Wahren
2018-12-06 18:28 ` [PATCH 08/10] staging: bcm2835-audio: Drop DT dependency Stefan Wahren
2018-12-06 18:28 ` [PATCH 09/10] staging: bcm2835-camera: Provide more specific probe error messages Stefan Wahren
2018-12-06 18:29 ` [PATCH 10/10] staging: bcm2835-camera: Add hint about possible faulty config Stefan Wahren
2018-12-07 6:21 ` [PATCH 00/10] staging: vc04_services: Improve driver load/unload Dan Carpenter
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=1544120940-13716-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=dave.stevenson@raspberrypi.org \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=tiwai@suse.de \
/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