From: kernel test robot <lkp@intel.com>
To: LECOINTRE Philippe <philippe.lecointre@thalesgroup.com>,
Lucas Stach <l.stach@pengutronix.de>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
"etnaviv@lists.freedesktop.org" <etnaviv@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
LENAIN Simon <simon.lenain@thalesgroup.com>,
BARBEAU Etienne <etienne.barbeau@thalesgroup.com>,
LEJEUNE Sebastien <sebastien.lejeune@thalesgroup.com>
Subject: Re: [PATCH] drm/etnaviv: add optional reset support
Date: Wed, 6 Nov 2024 07:04:22 +0800 [thread overview]
Message-ID: <202411060610.iIIdHXHP-lkp@intel.com> (raw)
In-Reply-To: <0825fa6ad3954cda970b42c25b45fb0d@thalesgroup.com>
Hi LECOINTRE,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on drm-exynos/exynos-drm-next drm-misc/drm-misc-next linus/master drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip v6.12-rc6]
[cannot apply to next-20241105]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/LECOINTRE-Philippe/drm-etnaviv-add-optional-reset-support/20241105-224118
base: git://anongit.freedesktop.org/drm/drm drm-next
patch link: https://lore.kernel.org/r/0825fa6ad3954cda970b42c25b45fb0d%40thalesgroup.com
patch subject: [PATCH] drm/etnaviv: add optional reset support
config: i386-buildonly-randconfig-003-20241106 (https://download.01.org/0day-ci/archive/20241106/202411060610.iIIdHXHP-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241106/202411060610.iIIdHXHP-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/oe-kbuild-all/202411060610.iIIdHXHP-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/gpu/drm/etnaviv/etnaviv_gpu.c: In function 'etnaviv_gpu_platform_probe':
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:9: error: implicit declaration of function 'irq_set_status_flags' [-Werror=implicit-function-declaration]
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
| ^~~~~~~~~~~~~~~~~~~~
>> drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:40: error: 'IRQ_NOAUTOEN' undeclared (first use in this function); did you mean 'IRQF_NO_AUTOEN'?
1900 | irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
| ^~~~~~~~~~~~
| IRQF_NO_AUTOEN
drivers/gpu/drm/etnaviv/etnaviv_gpu.c:1900:40: note: each undeclared identifier is reported only once for each function it appears in
cc1: all warnings being treated as errors
vim +/irq_set_status_flags +1900 drivers/gpu/drm/etnaviv/etnaviv_gpu.c
1874
1875 static int etnaviv_gpu_platform_probe(struct platform_device *pdev)
1876 {
1877 struct device *dev = &pdev->dev;
1878 struct etnaviv_gpu *gpu;
1879 int err;
1880
1881 gpu = devm_kzalloc(dev, sizeof(*gpu), GFP_KERNEL);
1882 if (!gpu)
1883 return -ENOMEM;
1884
1885 gpu->dev = &pdev->dev;
1886 mutex_init(&gpu->lock);
1887 mutex_init(&gpu->sched_lock);
1888
1889 /* Map registers: */
1890 gpu->mmio = devm_platform_ioremap_resource(pdev, 0);
1891 if (IS_ERR(gpu->mmio))
1892 return PTR_ERR(gpu->mmio);
1893
1894 /* Get Interrupt: */
1895 gpu->irq = platform_get_irq(pdev, 0);
1896 if (gpu->irq < 0)
1897 return gpu->irq;
1898
1899 /* Avoid enabling the interrupt until everything is ready */
> 1900 irq_set_status_flags(gpu->irq, IRQ_NOAUTOEN);
1901
1902 err = devm_request_irq(&pdev->dev, gpu->irq, irq_handler, 0,
1903 dev_name(gpu->dev), gpu);
1904 if (err) {
1905 dev_err(dev, "failed to request IRQ%u: %d\n", gpu->irq, err);
1906 return err;
1907 }
1908
1909 /* Get Reset: */
1910 gpu->rst = devm_reset_control_get_optional(&pdev->dev, NULL);
1911 if (IS_ERR(gpu->rst))
1912 return dev_err_probe(dev, PTR_ERR(gpu->rst),
1913 "failed to get reset\n");
1914
1915 /* Get Clocks: */
1916 gpu->clk_reg = devm_clk_get_optional(&pdev->dev, "reg");
1917 DBG("clk_reg: %p", gpu->clk_reg);
1918 if (IS_ERR(gpu->clk_reg))
1919 return PTR_ERR(gpu->clk_reg);
1920
1921 gpu->clk_bus = devm_clk_get_optional(&pdev->dev, "bus");
1922 DBG("clk_bus: %p", gpu->clk_bus);
1923 if (IS_ERR(gpu->clk_bus))
1924 return PTR_ERR(gpu->clk_bus);
1925
1926 gpu->clk_core = devm_clk_get(&pdev->dev, "core");
1927 DBG("clk_core: %p", gpu->clk_core);
1928 if (IS_ERR(gpu->clk_core))
1929 return PTR_ERR(gpu->clk_core);
1930 gpu->base_rate_core = clk_get_rate(gpu->clk_core);
1931
1932 gpu->clk_shader = devm_clk_get_optional(&pdev->dev, "shader");
1933 DBG("clk_shader: %p", gpu->clk_shader);
1934 if (IS_ERR(gpu->clk_shader))
1935 return PTR_ERR(gpu->clk_shader);
1936 gpu->base_rate_shader = clk_get_rate(gpu->clk_shader);
1937
1938 /* TODO: figure out max mapped size */
1939 dev_set_drvdata(dev, gpu);
1940
1941 /*
1942 * We treat the device as initially suspended. The runtime PM
1943 * autosuspend delay is rather arbitary: no measurements have
1944 * yet been performed to determine an appropriate value.
1945 */
1946 pm_runtime_use_autosuspend(gpu->dev);
1947 pm_runtime_set_autosuspend_delay(gpu->dev, 200);
1948 pm_runtime_enable(gpu->dev);
1949
1950 err = component_add(&pdev->dev, &gpu_ops);
1951 if (err < 0) {
1952 dev_err(&pdev->dev, "failed to register component: %d\n", err);
1953 return err;
1954 }
1955
1956 return 0;
1957 }
1958
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-05 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 14:37 [PATCH] drm/etnaviv: add optional reset support LECOINTRE Philippe
2024-11-05 23:04 ` kernel test robot [this message]
2024-11-05 23:15 ` 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=202411060610.iIIdHXHP-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=christian.gmeiner@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etienne.barbeau@thalesgroup.com \
--cc=etnaviv@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philippe.lecointre@thalesgroup.com \
--cc=sebastien.lejeune@thalesgroup.com \
--cc=simon.lenain@thalesgroup.com \
--cc=simona@ffwll.ch \
/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