From: Konstantin Sinyuk <sinyuk@gmail.com>
To: "linus.walleij@linaro.org" <linus.walleij@linaro.org>
Cc: ksummit@lists.linux.dev, Konstantin Sinyuk <konstantin.sinyuk@intel.com>
Subject: Re: [TECH TOPIC] UALink driver upstreaming
Date: Thu, 11 Sep 2025 21:10:11 +0300 [thread overview]
Message-ID: <CAPpb9yn9akO=pBiQs0=xTcPGTY-XghK8nYcm0dAgQO1Es5udWw@mail.gmail.com> (raw)
In-Reply-To: <a74382d8-a2bf-4534-b0ee-a97d8faabf16@intel.com>
On Thu, Sep 11, 2025 at 10:42:01AM +0200, Linus Walleij wrote:
> So this gives at hand that since this is no "ordinary" memory-mapped
> driver, it needs its own bus and therefore intuitively its own subsystem?
>
> What about drivers/accel/ual where other accelerators live?
>
> Or if that is somehow inappropriate, just drivers/ual, don't be shy.
Hi Linus,
For the initial RFC, I thought to start under drivers/misc/ just as a
lightweight entry point to get early review. But I agree with you that
UALink fits more naturally as its own subsystem, similar to how CXL is
handled, rather than being grouped under accel. The long-term plan
should definitely be drivers/ual/.
Best Regards,
Konstantin
next prev parent reply other threads:[~2025-09-11 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 19:37 Sinyuk, Konstantin
2025-09-10 23:58 ` dan.j.williams
2025-09-11 5:13 ` Greg KH
[not found] ` <a70edcba-0ef7-4d0d-bc00-0e8519a458e8@intel.com>
2025-09-11 11:13 ` Konstantin Sinyuk
2025-09-11 10:59 ` Mimi Zohar
[not found] ` <DM3PR11MB86833A11AD52C01C9063FFE1E309A@DM3PR11MB8683.namprd11.prod.outlook.com>
2025-09-11 11:09 ` FW: " Konstantin Sinyuk
2025-09-11 15:19 ` Linus Walleij
[not found] ` <a74382d8-a2bf-4534-b0ee-a97d8faabf16@intel.com>
2025-09-11 18:10 ` Konstantin Sinyuk [this message]
2025-09-11 19:02 ` Leon Romanovsky
2025-09-12 7:22 ` Linus Walleij
2025-09-12 7:47 ` Greg KH
[not found] ` <0f876c7c-566b-476a-b590-d490d41d605c@intel.com>
2025-09-12 12:07 ` Konstantin Sinyuk
2025-09-12 12:18 ` Linus Walleij
2025-09-12 13:49 ` Rodrigo Vivi
2025-09-12 16:13 ` Matthew Brost
2025-09-13 19:11 ` Jason Gunthorpe
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='CAPpb9yn9akO=pBiQs0=xTcPGTY-XghK8nYcm0dAgQO1Es5udWw@mail.gmail.com' \
--to=sinyuk@gmail.com \
--cc=konstantin.sinyuk@intel.com \
--cc=ksummit@lists.linux.dev \
--cc=linus.walleij@linaro.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