mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Umang Jain <umang.jain@ideasonboard.com>
To: linux-staging@lists.linux.dev,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stefan.wahren@i2se.com, gregkh@linuxfoundation.org,
	f.fainelli@gmail.com, athierry@redhat.com, error27@gmail.com,
	dave.stevenson@raspberrypi.com, kieran.bingham@ideasonboard.com,
	laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v9 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type
Date: Wed, 19 Jul 2023 22:24:28 +0530	[thread overview]
Message-ID: <fe8ed301-dda8-9038-a035-c24e84bc2c5c@ideasonboard.com> (raw)
In-Reply-To: <20230719164427.1383646-1-umang.jain@ideasonboard.com>

Hi,

One comment,

On 7/19/23 10:14 PM, Umang Jain wrote:
> The patch series added a new bus type vchiq_bus_type and registers
> child devices in order to move them away from using platform
> device/driver.
>
> Patch 1/5 and 2/5 adds a new bus_type and registers them to vchiq
> interface
>
> Patch 3/5 and 4/5 moves the bcm2835-camera and bcm2835-audio
> to the new bus respectively
>
> Patch 5/5 removes a platform registeration helper which is no
> longer required.
>
> Changes in v9:
> - Fix module autoloading

While the autoloading of bcm2835-audio, bcm2835-camera is fixed as part 
of this series, there is one WARN coming in when bcm2835-audio is loaded 
regarding dma_alloc_attr

dmesg output: https://paste.debian.net/plain/1286359

I am investigating further...
> - Implement bus_type's probe() callback to load drivers
> - Implement bus_type's uevent() to make sure appropriate drivers are
>    loaded when device are registed from vchiq.
>
> Changes in v8:
> - Drop dual licensing. Instead use GPL-2.0 only for patch 1/5
>
> Changes in v7:
> (5 out of 6 patches from v6 merged)
> - Split the main patch (6/6) as requested.
> - Use struct vchiq_device * instead of struct device * in
>    all bus functions.
> - Drop additional name attribute displayed in sysfs (redundant info)
> - Document vchiq_interface doesn't enumerate device discovery
> - remove EXPORT_SYMBOL_GPL(vchiq_bus_type)
>
> Changes in v6:
> - Split struct device and struct driver wrappers in vchiq_device.[ch]
> - Move vchiq_bus_type definition to vchiq_device.[ch] as well
> - return error on bus_register() failure
> - drop dma_set_mask_and_coherent
> - trivial variable name change
>
> Changes in v5:
> - Fixup missing "staging: " in commits' subject line
> - No code changes from v4
>
> Changes in v4:
> - Introduce patches to drop include directives from Makefile
>
> Changes in v3:
> - Rework entirely to replace platform devices/driver model
>
> -v2:
> https://lore.kernel.org/all/20221222191500.515795-1-umang.jain@ideasonboard.com/
>
> -v1:
> https://lore.kernel.org/all/20221220084404.19280-1-umang.jain@ideasonboard.com/
>
> Umang Jain (5):
>    staging: vc04_services: vchiq_arm: Add new bus type and device type
>    staging: vc04_services: vchiq_arm: Register vchiq_bus_type
>    staging: bcm2835-camera: Register bcm2835-camera with vchiq_bus_type
>    staging: bcm2835-audio: Register bcm2835-audio with vchiq_bus_type
>    staging: vc04_services: vchiq_arm: Remove vchiq_register_child()
>
>   drivers/staging/vc04_services/Makefile        |   1 +
>   .../vc04_services/bcm2835-audio/bcm2835.c     |  20 ++--
>   .../bcm2835-camera/bcm2835-camera.c           |  17 +--
>   .../interface/vchiq_arm/vchiq_arm.c           |  48 ++++-----
>   .../interface/vchiq_arm/vchiq_device.c        | 102 ++++++++++++++++++
>   .../interface/vchiq_arm/vchiq_device.h        |  54 ++++++++++
>   6 files changed, 196 insertions(+), 46 deletions(-)
>   create mode 100644 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.c
>   create mode 100644 drivers/staging/vc04_services/interface/vchiq_arm/vchiq_device.h
>


  parent reply	other threads:[~2023-07-19 16:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 16:44 Umang Jain
2023-07-19 16:44 ` [PATCH v9 1/5] staging: vc04_services: vchiq_arm: Add new bus type and device type Umang Jain
2023-07-19 17:51   ` Stefan Wahren
2023-07-19 16:44 ` [PATCH v9 2/5] staging: vc04_services: vchiq_arm: Register vchiq_bus_type Umang Jain
2023-07-20  5:37   ` Dan Carpenter
2023-07-19 16:44 ` [PATCH v9 3/5] staging: bcm2835-camera: Register bcm2835-camera with vchiq_bus_type Umang Jain
2023-07-19 16:44 ` [PATCH v9 4/5] staging: bcm2835-audio: Register bcm2835-audio " Umang Jain
2023-07-19 17:55   ` Stefan Wahren
2023-07-19 16:44 ` [PATCH v9 5/5] staging: vc04_services: vchiq_arm: Remove vchiq_register_child() Umang Jain
2023-07-19 16:54 ` Umang Jain [this message]
2023-07-19 17:35   ` [PATCH v9 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type Stefan Wahren
2023-07-20 12:08     ` Umang Jain
2023-07-20 16:16       ` Stefan Wahren

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=fe8ed301-dda8-9038-a035-c24e84bc2c5c@ideasonboard.com \
    --to=umang.jain@ideasonboard.com \
    --cc=athierry@redhat.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=error27@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=stefan.wahren@i2se.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

all inboxes | Powered by JetHome®