public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Andreas Helbech Kleist <andreaskleist@gmail.com>,
	bingbu.cao@intel.com, linux-media@vger.kernel.org,
	sakari.ailus@linux.intel.com, laurent.pinchart@ideasonboard.com
Cc: ilpo.jarvinen@linux.intel.com, tfiga@chromium.org,
	senozhatsky@chromium.org, andriy.shevchenko@linux.intel.com,
	hdegoede@redhat.com, tomi.valkeinen@ideasonboard.com,
	tian.shu.qiu@intel.com, hongju.wang@intel.com
Subject: Re: [PATCH 10/15] media: intel/ipu6: add input system driver
Date: Thu, 19 Oct 2023 16:28:16 +0800	[thread overview]
Message-ID: <ea3cc241-4074-2b53-359f-360ca45a7b1f@linux.intel.com> (raw)
In-Reply-To: <1ce2242844b3e1348d7343b84b15dd87e0f66e6a.camel@gmail.com>

Andreas,

On 10/3/23 6:13 PM, Andreas Helbech Kleist wrote:
> Hi,
> 
> On Thu, 2023-07-27 at 15:15 +0800, bingbu.cao@intel.com wrote:
>> From: Bingbu Cao <bingbu.cao@intel.com>
>>
>> Input system driver do basic isys hardware setup and irq handling
>> and work with fwnode and v4l2 to register the ISYS v4l2 devices.
> 
>> +       media_device_pci_init(&isys->media_dev,
>> +                             pdev, IPU6_MEDIA_DEV_MODEL_NAME);
>> +
>> +       strscpy(isys->v4l2_dev.name, isys->media_dev.model,
>> +               sizeof(isys->v4l2_dev.name));
>> +
>> +       ret = media_device_register(&isys->media_dev);
>> +       if (ret < 0)
>> +               goto out_media_device_unregister;
> ...
>> +out_media_device_unregister:
>> +       media_device_unregister(&isys->media_dev);
>> +       media_device_cleanup(&isys->media_dev);
> 
> You should only call media_device_cleanup() if media_device_register()
> fails.
> 
> 
>> +static const struct pci_device_id isys_pci_tbl[] = {
>> +       { PCI_VDEVICE(INTEL, IPU6_PCI_ID) },
>> +       { PCI_VDEVICE(INTEL, IPU6SE_PCI_ID) },
>> +       { PCI_VDEVICE(INTEL, IPU6EP_ADL_P_PCI_ID) },
>> +       { PCI_VDEVICE(INTEL, IPU6EP_ADL_N_PCI_ID) },
>> +       { PCI_VDEVICE(INTEL, IPU6EP_RPL_P_PCI_ID) },
>> +       { PCI_VDEVICE(INTEL, IPU6EP_MTL_PCI_ID) },
>> +       { }
>> +};
> 
> Unused

Have you tried that whether isys driver can be auto-loaded w/o
this pci id table? It cannot on my side.

> 
>> +static const struct auxiliary_device_id ipu6_isys_id_table[] = {
>> +       {
>> +               .name = "intel_ipu6.isys",
>> +               .driver_data =
>> (kernel_ulong_t)&ipu6_isys_auxdrv_data,
>> +       },
>> +};
> 
> Missing sentinel {}.
> 
> 
> Best regards,
> Andreas
> 

-- 
Best regards,
Bingbu Cao

  reply	other threads:[~2023-10-19  8:31 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  7:15 [PATCH 00/15] Intel IPU6 and IPU6 input system drivers bingbu.cao
2023-07-27  7:15 ` [PATCH 01/15] media: intel/ipu6: add Intel IPU6 PCI device driver bingbu.cao
2023-07-27 10:47   ` Andy Shevchenko
2023-10-03 10:12   ` Andreas Helbech Kleist
2023-10-16  9:39     ` Andreas Helbech Kleist
2023-10-19  8:23       ` Bingbu Cao
2023-10-20 10:48         ` Andreas Helbech Kleist
2023-10-20 10:48         ` Andreas Helbech Kleist
2023-07-27  7:15 ` [PATCH 02/15] media: intel/ipu6: add IPU auxiliary devices bingbu.cao
2023-10-03 10:13   ` Andreas Helbech Kleist
2023-10-19  8:24     ` Bingbu Cao
2023-07-27  7:15 ` [PATCH 03/15] media: intel/ipu6: add IPU6 buttress interface driver bingbu.cao
2023-07-27  7:15 ` [PATCH 04/15] media: intel/ipu6: CPD parsing for get firmware components bingbu.cao
2023-07-27  7:15 ` [PATCH 05/15] media: intel/ipu6: add IPU6 DMA mapping API and MMU table bingbu.cao
2023-07-27  7:15 ` [PATCH 06/15] media: intel/ipu6: add syscom interfaces between firmware and driver bingbu.cao
2023-07-27  7:15 ` [PATCH 07/15] media: intel/ipu6: input system ABI " bingbu.cao
2023-07-27  7:15 ` [PATCH 08/15] media: intel/ipu6: add IPU6 CSI2 receiver v4l2 sub-device bingbu.cao
2023-07-27  7:15 ` [PATCH 09/15] media: intel/ipu6: add the CSI2 DPHY implementation bingbu.cao
2023-07-27  7:15 ` [PATCH 10/15] media: intel/ipu6: add input system driver bingbu.cao
2023-10-03 10:13   ` Andreas Helbech Kleist
2023-10-19  8:28     ` Bingbu Cao [this message]
2023-10-19 12:22       ` Andy Shevchenko
2023-10-20  2:21         ` Cao, Bingbu
2023-10-20 10:20           ` Andy Shevchenko
2023-10-20 10:47       ` Andreas Helbech Kleist
2023-10-20 14:39         ` Hans de Goede
2023-10-23  6:23           ` Andreas Helbech Kleist
2023-10-23  7:44             ` Hans de Goede
2023-10-23  8:23               ` Bingbu Cao
2023-10-23 11:29               ` Andy Shevchenko
2023-12-20 12:53               ` RFC: Intel IPU4 driver proof of concept Andreas Helbech Kleist
2026-02-22 19:57                 ` Ruslan Bay
2026-03-04 11:03                   ` Ruslan Bay
2026-03-04 12:16                     ` johannes.goede
2023-10-23 11:29             ` [PATCH 10/15] media: intel/ipu6: add input system driver Andy Shevchenko
2023-07-27  7:15 ` [PATCH 11/15] media: intel/ipu6: input system video capture nodes bingbu.cao
2023-10-23 11:36   ` Andreas Helbech Kleist
2023-12-07  9:28   ` Andreas Helbech Kleist
2023-12-20  3:42   ` Bingbu Cao
2023-12-20  6:51     ` Laurent Pinchart
2023-12-20  9:25       ` Bingbu Cao
2023-07-27  7:15 ` [PATCH 12/15] media: add Kconfig and Makefile for IPU6 bingbu.cao
2023-10-03 10:13   ` Andreas Helbech Kleist
2023-10-19  8:28     ` Bingbu Cao
2023-07-27  7:15 ` [PATCH 13/15] MAINTAINERS: add maintainers for Intel IPU6 input system driver bingbu.cao
2023-07-27 10:19   ` Andy Shevchenko
2023-07-27  7:15 ` [PATCH 14/15] Documentation: add Intel IPU6 ISYS driver admin-guide doc bingbu.cao
2023-07-27  7:15 ` [PATCH 15/15] Documentation: add documentation of Intel IPU6 driver and hardware overview bingbu.cao
2023-08-20 15:09 ` [PATCH 00/15] Intel IPU6 and IPU6 input system drivers Claus Stovgaard
2023-08-21  3:14   ` Bingbu Cao
2023-08-21  6:22     ` Bingbu Cao
2023-08-21  6:55       ` Claus Stovgaard
2023-08-21 10:07         ` Claus Stovgaard
2023-08-21 12:19           ` Laurent Pinchart
2023-08-22 12:52             ` claus.stovgaard
2023-08-22 14:22               ` Laurent Pinchart
2023-08-24 20:35                 ` Claus Stovgaard
2023-08-22  3:05           ` Bingbu Cao
2023-08-24 20:19             ` Claus Stovgaard
2023-08-31 21:24           ` Hans de Goede
2023-09-02 14:54             ` Hans de Goede
2023-09-03 14:32               ` Hans de Goede
2023-09-04  3:13                 ` Cao, Bingbu
2023-09-04  7:35                   ` Hans de Goede
2023-10-02 17:19                   ` Hans de Goede
2023-10-02 17:38                     ` Laurent Pinchart
2023-10-02 17:41                       ` Hans de Goede
2023-10-09  6:23                         ` Bingbu Cao
2023-10-09 12:25                         ` Bingbu Cao
2023-10-09 12:53                           ` Hans de Goede
2023-10-10  2:54                             ` Bingbu Cao
2023-10-10  8:10                               ` Hans de Goede
2023-10-10  8:35                                 ` Bingbu Cao
2023-09-04  6:12                 ` Bingbu Cao
2023-09-04  9:16                   ` Andy Shevchenko
2023-09-19 10:23                   ` Hans de Goede
2023-09-20  4:46                     ` Bingbu Cao
2023-09-20  8:52                       ` Hans de Goede
2023-09-20 12:32                         ` Claus Stovgaard

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=ea3cc241-4074-2b53-359f-360ca45a7b1f@linux.intel.com \
    --to=bingbu.cao@linux.intel.com \
    --cc=andreaskleist@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=hongju.wang@intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=senozhatsky@chromium.org \
    --cc=tfiga@chromium.org \
    --cc=tian.shu.qiu@intel.com \
    --cc=tomi.valkeinen@ideasonboard.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