From: asutoshd@codeaurora.org
To: linux-scsi@vger.kernel.org
Subject: Query: SCSI Device node creation when UFS is loaded as a module
Date: Wed, 23 Oct 2019 16:51:35 -0700 [thread overview]
Message-ID: <468eb805fa69da76c88a0a37aa209c7f@codeaurora.org> (raw)
Hi
I'm loading the ufs-qcom driver as a module but am not seeing the
/dev/sda* device nodes.
Looks like it's not being created.
I find the sda nodes in other paths being enumerated though:
/ # find /sys -name sda
/sys/kernel/debug/block/sda
/sys/class/block/sda
/sys/devices/platform/<...>/<xxx>.ufshc/host0/target0:0:0/0:0:0:0/block/sda
/sys/block/sda
All Luns are detected and I see sda is detected and prints for all the
Luns as below -:
sd 0:0:0:0: [sda] .... ....-byte logical blocks:
... so on ...
But if I link it statically instead of a module, it works fine. All
device nodes are created.
I'm trying to figure out where/how in SCSI does it create these device
nodes - /dev/sd<a/b/c/d> ?
I've looked into sd.c but I couldn't figure out the exact place yet.
Any pointers please?
TIA
-asd
next reply other threads:[~2019-10-23 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 23:51 asutoshd [this message]
2019-10-24 6:14 ` Query: SCSI Device node creation when UFS is loaded as a module Avri Altman
2019-10-24 9:50 ` Steffen Maier
2019-10-24 17:05 ` asutoshd
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=468eb805fa69da76c88a0a37aa209c7f@codeaurora.org \
--to=asutoshd@codeaurora.org \
--cc=linux-scsi@vger.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