mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor@kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devicetree-compiler@vger.kernel.org,
	devicetree-spec@vger.kernel.org
Subject: [ANNOUNCEMENT / CFP] LPC 2025 Devicetree Microconference CFP
Date: Thu, 7 Aug 2025 13:46:18 +0200	[thread overview]
Message-ID: <8c59ef9a-7b5c-4fec-b630-ac84218ed955@kernel.org> (raw)

There will be a dedicated Devicetree Microconference on Linux Plumbers
2025 in December in Tokyo and Call For Papers is currently open.

The Devicetree Microconference focuses on discussing and solving
problems present in the systems using Devicetree as firmware
representation. Primarily this will be Linux kernel and U-Boot, but also
can cover topics relevant to Zephyr or System Devicetrees.

Topics suggested for discussion include, but are not limited to:
1. DTS validation against DT schema,
2. Style checking/linting for DTS,
3. Using the Linux kernel DTS in U-Boot or other projects,
4. DTB selection on EFI systems like arm64 laptops,
5. Hot-pluggable hardware with Devicetree overlay,
6. Common incorrect or problematic patterns of using OF Linux API, e.g.
impossible to disable unconditional device_init_wakeup().

Feel welcomed to bring any other topics I am not aware of. Few more
ideas for discussions are mentioned on DT MC abstract page:
https://lpc.events/event/19/sessions/237/


CFP ends on: 14th of September 2025

Proposals can be submitted here:

https://lpc.events/event/19/abstracts/


This email has a list of people in Bcc. It is far from being complete,
so feel free to forward it further.

Best regards,
Krzysztof


                 reply	other threads:[~2025-08-07 11:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8c59ef9a-7b5c-4fec-b630-ac84218ed955@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®