From: kernel test robot <lkp@intel.com>
To: Andreas Helbech Kleist <andreaskleist@gmail.com>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: [kleist:ipu4-dev 19/59] drivers/media/pci/intel/ipu6/ipu6-bus.c:101:14: error: no member named 'dma_ops' in 'struct device'
Date: Mon, 1 Jan 2024 13:25:33 +0800 [thread overview]
Message-ID: <ZZJMzcpposIbvJ2l@rli9-mobl> (raw)
tree: https://github.com/Kleist/linux ipu4-dev
head: 15245fe26e07c9118f0f5c03af5469832928f3dc
commit: d35c2043fb50817f1e5eb1ddb6ae4b95d367ae55 [19/59] media: intel/ipu4: HACK: Re-purpose ipu6 files for ipu4 driver
:::::: branch date: 9 days ago
:::::: commit date: 10 days ago
config: x86_64-randconfig-r112-20231229 (https://download.01.org/0day-ci/archive/20231230/202312300202.D9KXE9bV-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231230/202312300202.D9KXE9bV-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202312300202.D9KXE9bV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/media/pci/intel/ipu6/ipu6-bus.c:101:14: error: no member named 'dma_ops' in 'struct device'
101 | auxdev->dev.dma_ops = &ipu6_dma_ops;
| ~~~~~~~~~~~ ^
1 error generated.
vim +101 drivers/media/pci/intel/ipu6/ipu6-bus.c
214681ec4e2bf1 Bingbu Cao 2023-10-24 74
214681ec4e2bf1 Bingbu Cao 2023-10-24 75 struct ipu6_bus_device *
214681ec4e2bf1 Bingbu Cao 2023-10-24 76 ipu6_bus_initialize_device(struct pci_dev *pdev, struct device *parent,
89e2423725f00f Andreas Helbech Kleist 2023-11-10 77 void *pdata, const struct ipu6_buttress_ctrl *ctrl,
214681ec4e2bf1 Bingbu Cao 2023-10-24 78 char *name)
214681ec4e2bf1 Bingbu Cao 2023-10-24 79 {
214681ec4e2bf1 Bingbu Cao 2023-10-24 80 struct auxiliary_device *auxdev;
214681ec4e2bf1 Bingbu Cao 2023-10-24 81 struct ipu6_bus_device *adev;
214681ec4e2bf1 Bingbu Cao 2023-10-24 82 struct ipu6_device *isp = pci_get_drvdata(pdev);
214681ec4e2bf1 Bingbu Cao 2023-10-24 83 int ret;
214681ec4e2bf1 Bingbu Cao 2023-10-24 84
214681ec4e2bf1 Bingbu Cao 2023-10-24 85 adev = kzalloc(sizeof(*adev), GFP_KERNEL);
214681ec4e2bf1 Bingbu Cao 2023-10-24 86 if (!adev)
214681ec4e2bf1 Bingbu Cao 2023-10-24 87 return ERR_PTR(-ENOMEM);
214681ec4e2bf1 Bingbu Cao 2023-10-24 88
214681ec4e2bf1 Bingbu Cao 2023-10-24 89 adev->dma_mask = DMA_BIT_MASK(isp->secure_mode ? IPU6_MMU_ADDR_BITS :
214681ec4e2bf1 Bingbu Cao 2023-10-24 90 IPU6_MMU_ADDR_BITS_NON_SECURE);
214681ec4e2bf1 Bingbu Cao 2023-10-24 91 adev->isp = isp;
214681ec4e2bf1 Bingbu Cao 2023-10-24 92 adev->ctrl = ctrl;
214681ec4e2bf1 Bingbu Cao 2023-10-24 93 adev->pdata = pdata;
214681ec4e2bf1 Bingbu Cao 2023-10-24 94 auxdev = &adev->auxdev;
214681ec4e2bf1 Bingbu Cao 2023-10-24 95 auxdev->name = name;
214681ec4e2bf1 Bingbu Cao 2023-10-24 96 auxdev->id = (pci_domain_nr(pdev->bus) << 16) |
214681ec4e2bf1 Bingbu Cao 2023-10-24 97 PCI_DEVID(pdev->bus->number, pdev->devfn);
214681ec4e2bf1 Bingbu Cao 2023-10-24 98
214681ec4e2bf1 Bingbu Cao 2023-10-24 99 auxdev->dev.parent = parent;
214681ec4e2bf1 Bingbu Cao 2023-10-24 100 auxdev->dev.release = ipu6_bus_release;
214681ec4e2bf1 Bingbu Cao 2023-10-24 @101 auxdev->dev.dma_ops = &ipu6_dma_ops;
214681ec4e2bf1 Bingbu Cao 2023-10-24 102 auxdev->dev.dma_mask = &adev->dma_mask;
214681ec4e2bf1 Bingbu Cao 2023-10-24 103 auxdev->dev.dma_parms = pdev->dev.dma_parms;
214681ec4e2bf1 Bingbu Cao 2023-10-24 104 auxdev->dev.coherent_dma_mask = adev->dma_mask;
214681ec4e2bf1 Bingbu Cao 2023-10-24 105
214681ec4e2bf1 Bingbu Cao 2023-10-24 106 ret = auxiliary_device_init(auxdev);
214681ec4e2bf1 Bingbu Cao 2023-10-24 107 if (ret < 0) {
214681ec4e2bf1 Bingbu Cao 2023-10-24 108 dev_err(&isp->pdev->dev, "auxiliary device init failed (%d)\n",
214681ec4e2bf1 Bingbu Cao 2023-10-24 109 ret);
214681ec4e2bf1 Bingbu Cao 2023-10-24 110 kfree(adev);
214681ec4e2bf1 Bingbu Cao 2023-10-24 111 return ERR_PTR(ret);
214681ec4e2bf1 Bingbu Cao 2023-10-24 112 }
214681ec4e2bf1 Bingbu Cao 2023-10-24 113
214681ec4e2bf1 Bingbu Cao 2023-10-24 114 dev_pm_domain_set(&auxdev->dev, &ipu6_bus_pm_domain);
214681ec4e2bf1 Bingbu Cao 2023-10-24 115
214681ec4e2bf1 Bingbu Cao 2023-10-24 116 pm_runtime_forbid(&adev->auxdev.dev);
214681ec4e2bf1 Bingbu Cao 2023-10-24 117 pm_runtime_enable(&adev->auxdev.dev);
214681ec4e2bf1 Bingbu Cao 2023-10-24 118
214681ec4e2bf1 Bingbu Cao 2023-10-24 119 return adev;
214681ec4e2bf1 Bingbu Cao 2023-10-24 120 }
214681ec4e2bf1 Bingbu Cao 2023-10-24 121
:::::: The code at line 101 was first introduced by commit
:::::: 214681ec4e2bf174045d6527cb97d44941d84eb5 media: intel/ipu6: add IPU auxiliary devices
:::::: TO: Bingbu Cao <bingbu.cao@intel.com>
:::::: CC: Andreas Helbech Kleist <andreaskleist@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-01 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 5:25 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-29 18:08 [kleist:ipu4-dev 19/59] drivers/media/pci/intel/ipu6/ipu6-bus.c:101:14: error: no member named 'dma_ops' in 'struct device' kernel test robot
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=ZZJMzcpposIbvJ2l@rli9-mobl \
--to=lkp@intel.com \
--cc=andreaskleist@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.