From: Sean Anderson <sean.anderson@linux.dev>
To: kernel test robot <lkp@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev, David Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org, Michal Simek <monstr@monstr.eu>,
linux-arm-kernel@lists.infradead.org,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 3/6] drm: zynqmp_dp: Add locking
Date: Mon, 18 Mar 2024 11:09:33 -0400 [thread overview]
Message-ID: <0774c0a7-8ef7-47cb-8c1c-695c67e10182@linux.dev> (raw)
In-Reply-To: <202403161747.TRmfawhM-lkp@intel.com>
On 3/16/24 05:52, kernel test robot wrote:
> Hi Sean,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on v6.8]
> [also build test WARNING on linus/master next-20240315]
> [cannot apply to drm-misc/drm-misc-next]
> [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/Sean-Anderson/drm-zynqmp_dp-Downgrade-log-level-for-aux-retries-message/20240316-071208
> base: v6.8
> patch link: https://lore.kernel.org/r/20240315230916.1759060-4-sean.anderson%40linux.dev
> patch subject: [PATCH 3/6] drm: zynqmp_dp: Add locking
> config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240316/202403161747.TRmfawhM-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240316/202403161747.TRmfawhM-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/202403161747.TRmfawhM-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> drivers/gpu/drm/xlnx/zynqmp_dp.c:321: warning: Function parameter or struct member 'hpd_irq_work' not described in 'zynqmp_dp'
Will document.
--Sean
>
> vim +321 drivers/gpu/drm/xlnx/zynqmp_dp.c
>
> d76271d22694e8 Hyun Kwon 2018-07-07 275
> d76271d22694e8 Hyun Kwon 2018-07-07 276 /**
> d76271d22694e8 Hyun Kwon 2018-07-07 277 * struct zynqmp_dp - Xilinx DisplayPort core
> d76271d22694e8 Hyun Kwon 2018-07-07 278 * @dev: device structure
> d76271d22694e8 Hyun Kwon 2018-07-07 279 * @dpsub: Display subsystem
> d76271d22694e8 Hyun Kwon 2018-07-07 280 * @iomem: device I/O memory for register access
> d76271d22694e8 Hyun Kwon 2018-07-07 281 * @reset: reset controller
> 8ce380e6568015 Sean Anderson 2024-03-15 282 * @lock: Mutex protecting this struct and register access (but not AUX)
> d76271d22694e8 Hyun Kwon 2018-07-07 283 * @irq: irq
> 47e801bd0749f0 Laurent Pinchart 2021-08-04 284 * @bridge: DRM bridge for the DP encoder
> bd68b9b3cb2e0d Laurent Pinchart 2021-08-04 285 * @next_bridge: The downstream bridge
> d76271d22694e8 Hyun Kwon 2018-07-07 286 * @config: IP core configuration from DTS
> d76271d22694e8 Hyun Kwon 2018-07-07 287 * @aux: aux channel
> d76271d22694e8 Hyun Kwon 2018-07-07 288 * @phy: PHY handles for DP lanes
> d76271d22694e8 Hyun Kwon 2018-07-07 289 * @num_lanes: number of enabled phy lanes
> d76271d22694e8 Hyun Kwon 2018-07-07 290 * @hpd_work: hot plug detection worker
> d76271d22694e8 Hyun Kwon 2018-07-07 291 * @status: connection status
> d76271d22694e8 Hyun Kwon 2018-07-07 292 * @enabled: flag to indicate if the device is enabled
> d76271d22694e8 Hyun Kwon 2018-07-07 293 * @dpcd: DP configuration data from currently connected sink device
> d76271d22694e8 Hyun Kwon 2018-07-07 294 * @link_config: common link configuration between IP core and sink device
> d76271d22694e8 Hyun Kwon 2018-07-07 295 * @mode: current mode between IP core and sink device
> d76271d22694e8 Hyun Kwon 2018-07-07 296 * @train_set: set of training data
> d76271d22694e8 Hyun Kwon 2018-07-07 297 */
> d76271d22694e8 Hyun Kwon 2018-07-07 298 struct zynqmp_dp {
> d76271d22694e8 Hyun Kwon 2018-07-07 299 struct device *dev;
> d76271d22694e8 Hyun Kwon 2018-07-07 300 struct zynqmp_dpsub *dpsub;
> d76271d22694e8 Hyun Kwon 2018-07-07 301 void __iomem *iomem;
> d76271d22694e8 Hyun Kwon 2018-07-07 302 struct reset_control *reset;
> 8ce380e6568015 Sean Anderson 2024-03-15 303 struct mutex lock;
> d76271d22694e8 Hyun Kwon 2018-07-07 304 int irq;
> d76271d22694e8 Hyun Kwon 2018-07-07 305
> 47e801bd0749f0 Laurent Pinchart 2021-08-04 306 struct drm_bridge bridge;
> bd68b9b3cb2e0d Laurent Pinchart 2021-08-04 307 struct drm_bridge *next_bridge;
> 47e801bd0749f0 Laurent Pinchart 2021-08-04 308
> d76271d22694e8 Hyun Kwon 2018-07-07 309 struct zynqmp_dp_config config;
> d76271d22694e8 Hyun Kwon 2018-07-07 310 struct drm_dp_aux aux;
> d76271d22694e8 Hyun Kwon 2018-07-07 311 struct phy *phy[ZYNQMP_DP_MAX_LANES];
> d76271d22694e8 Hyun Kwon 2018-07-07 312 u8 num_lanes;
> 8ce380e6568015 Sean Anderson 2024-03-15 313 struct delayed_work hpd_work, hpd_irq_work;
> d76271d22694e8 Hyun Kwon 2018-07-07 314 enum drm_connector_status status;
> d76271d22694e8 Hyun Kwon 2018-07-07 315 bool enabled;
> d76271d22694e8 Hyun Kwon 2018-07-07 316
> d76271d22694e8 Hyun Kwon 2018-07-07 317 u8 dpcd[DP_RECEIVER_CAP_SIZE];
> d76271d22694e8 Hyun Kwon 2018-07-07 318 struct zynqmp_dp_link_config link_config;
> d76271d22694e8 Hyun Kwon 2018-07-07 319 struct zynqmp_dp_mode mode;
> d76271d22694e8 Hyun Kwon 2018-07-07 320 u8 train_set[ZYNQMP_DP_MAX_LANES];
> d76271d22694e8 Hyun Kwon 2018-07-07 @321 };
> d76271d22694e8 Hyun Kwon 2018-07-07 322
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-18 15:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 23:09 [PATCH 0/6] drm: zynqmp_dp: Misc. patches and debugfs support Sean Anderson
2024-03-15 23:09 ` [PATCH 1/6] drm: zynqmp_dp: Downgrade log level for aux retries message Sean Anderson
2024-03-18 16:39 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 2/6] drm: zynqmp_dp: Adjust training values per-lane Sean Anderson
2024-03-18 17:06 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 3/6] drm: zynqmp_dp: Add locking Sean Anderson
2024-03-16 9:52 ` kernel test robot
2024-03-18 15:09 ` Sean Anderson [this message]
2024-03-18 17:16 ` Laurent Pinchart
2024-03-18 17:29 ` Sean Anderson
2024-03-18 17:59 ` Laurent Pinchart
2024-03-18 18:01 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 4/6] drm: zynqmp_dp: Split off several helper functions Sean Anderson
2024-03-18 17:41 ` Laurent Pinchart
2024-03-15 23:09 ` [PATCH 5/6] drm: zynqmp_dp: Optionally ignore DPCD errors Sean Anderson
2024-03-18 17:47 ` Laurent Pinchart
2024-03-18 18:12 ` Sean Anderson
2024-03-15 23:09 ` [PATCH 6/6] drm: zynqmp_dp: Add debugfs interface for compliance testing Sean Anderson
2024-03-16 10:14 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson
2024-03-18 17:50 ` Laurent Pinchart
2024-03-18 19:05 ` Sean Anderson
2024-03-20 6:03 ` Yujie Liu
2024-03-16 10:55 ` kernel test robot
2024-03-18 15:06 ` Sean Anderson
2024-03-16 17:56 ` Dmitry Baryshkov
2024-03-18 15:22 ` Sean Anderson
2024-03-18 17:52 ` Laurent Pinchart
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=0774c0a7-8ef7-47cb-8c1c-695c67e10182@linux.dev \
--to=sean.anderson@linux.dev \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=monstr@monstr.eu \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).