Message ID | 20230719164427.1383646-1-umang.jain@ideasonboard.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:c923:0:b0:3e4:2afc:c1 with SMTP id j3csp2589797vqt; Wed, 19 Jul 2023 10:21:00 -0700 (PDT) X-Google-Smtp-Source: APBJJlE6ytKYvTOREiiVlgUexEni7Bj/8fsGl8YEwESPDk6pm0kc5oBgzyjIB0o4BhpT9ciLuCom X-Received: by 2002:a05:6402:b28:b0:51d:d37f:ab49 with SMTP id bo8-20020a0564020b2800b0051dd37fab49mr27021edb.6.1689787260263; Wed, 19 Jul 2023 10:21:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1689787260; cv=none; d=google.com; s=arc-20160816; b=VuXgBFtjF2UC97JZFMwSQ1CfWfJ1WVkW8ETQqfq1buPzahLYJhbO4cTKYNgb9OQqLZ jTj1b3dFy6xtI/Cc4xBJMvFzCHJ2DFr0VvUb1E/SGCBnFCHzv0x+vA3LUUm+06/NQqjy CN2JTGTgBD2TG2iH1RqP8T+RsFvDDyxDjnHls4EPBXWZ/JvEkBGje8N4OY5nqmPX45fQ /qFsM0/DQoHybn3DnO3QDPwk8kULBM8G7k4dkf2wz3HZ7vLEBaWoXC2c5Mf+0yog4lEJ e3sVt48hstU5vXKHbnLB5Y6anJlEalrfR7ZUHWzxWJDHcQzv5vAXy7k98pZnxofAuGLA pWHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=Hqydr12cMYY6a2aGNGds30KyqP++KAwWR1DQ6z9AT0A=; fh=HOFam38REw6BIxvQyXL0jcX3gf57D0OJSEWCuf65U0M=; b=APme5XQWM/ehQzpbCbY9jM9ZIlfmY61f5E0GpqVjRGeGIN2wmW6HuMrfhie70ZnnCj aTPLjlj2eSvMpSAEX3n684lDkM+5/7VC+A1c2yKe37E1QI6EuCyhpB6Tu3sKCangVOB0 PuYsiGOGxmnLtFNvnD7f8bM4XYl8L3ZRWZSMp5dCJb7/CmzcOhOo3Av9a9CGndhhFGEs PUu1/Wga6sJdcz4vDVoiBIRhTDc0vrPQV49mUZtuxAS/Ib20k/NyM6jd4mxt4i42aV0o +zXn2jWcYDMxkueQv1UMg3PdgC8nfzWYGoAUslONvwIc7ckGIQQT9T8UDmClUG+Mkmnf EJzg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=Kj3BdlBm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a1-20020aa7cf01000000b0051e1690103bsi3188050edy.574.2023.07.19.10.20.36; Wed, 19 Jul 2023 10:21:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=Kj3BdlBm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230242AbjGSQo5 (ORCPT <rfc822;assdfgzxcv4@gmail.com> + 99 others); Wed, 19 Jul 2023 12:44:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60504 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229989AbjGSQoz (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Wed, 19 Jul 2023 12:44:55 -0400 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 273AE1FED; Wed, 19 Jul 2023 09:44:43 -0700 (PDT) Received: from umang.jainideasonboard.com (unknown [103.86.18.219]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 85F9375B; Wed, 19 Jul 2023 18:43:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1689785026; bh=KY0KfMwlJOjWmTN7bkILqIjrm65iQUQb//QhYN5SlzQ=; h=From:To:Cc:Subject:Date:From; b=Kj3BdlBmQMSUxSe130AvRRQc3vM8N6DYZgyJ8b7OJ+kJaOtXNWMbUjdmxkCMgZ+kW CnYrNiDhR9wgLa7GxxqfOa1NUWyVQZ67yEUpd5VQuBNSMvoEuhJbwkAS0d1uR3o0bw U3Le3N7O1WjPxDHdavVAVuUuk0DdYcXjcoDt7EOM= 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, Umang Jain <umang.jain@ideasonboard.com> Subject: [PATCH v9 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type Date: Wed, 19 Jul 2023 22:14:22 +0530 Message-Id: <20230719164427.1383646-1-umang.jain@ideasonboard.com> X-Mailer: git-send-email 2.39.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1771869583854691116 X-GMAIL-MSGID: 1771870366338727818 |
Series |
staging: vc04_services: vchiq: Register devices with a custom bus_type
|
|
Message
Umang Jain
July 19, 2023, 4:44 p.m. UTC
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 - 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
Comments
Hi Umang, Am 19.07.23 um 18:54 schrieb Umang Jain: > 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 is it possible that after your patch series no DMA mask like DMA_BIT_MASK(32) is provided? > > 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 >> >
Hi Stefan , On 7/19/23 11:05 PM, Stefan Wahren wrote: > Hi Umang, > > Am 19.07.23 um 18:54 schrieb Umang Jain: >> 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 > > is it possible that after your patch series no DMA mask like > DMA_BIT_MASK(32) is provided? I am trying to set DMA_BIT_MASK(32) via dma_set_mask_and_coherent() but it fails with -EIO > >> >> 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 >>> >>
Hi Umang, Am 20.07.23 um 14:08 schrieb Umang Jain: > Hi Stefan , > > > On 7/19/23 11:05 PM, Stefan Wahren wrote: >> Hi Umang, >> >> Am 19.07.23 um 18:54 schrieb Umang Jain: >>> 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 >> >> is it possible that after your patch series no DMA mask like >> DMA_BIT_MASK(32) is provided? > > I am trying to set DMA_BIT_MASK(32) via dma_set_mask_and_coherent() but > it fails with -EIO what happens if you assign DMA_BIT_MASK(32) to device->dev.dma_mask within vchiq_device_register()? >> >>> >>> 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 >>>> >>> > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel