From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1A6A7CA9EB9 for ; Wed, 23 Oct 2019 23:51:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D6C742064B for ; Wed, 23 Oct 2019 23:51:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="Sebe89sf"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=codeaurora.org header.i=@codeaurora.org header.b="Sebe89sf" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392800AbfJWXvg (ORCPT ); Wed, 23 Oct 2019 19:51:36 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:33930 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389801AbfJWXvg (ORCPT ); Wed, 23 Oct 2019 19:51:36 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id B2B4D60FA9; Wed, 23 Oct 2019 23:51:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1571874695; bh=RQzk63vXXXNk90usgWk/wx+IVC7KwqQNIfrdUilq1wg=; h=Date:From:To:Subject:From; b=Sebe89sfJjKrrsOpcmAaEqYI3PDqiWvMcyY7coEc46lE/XhSI9beT9UrgkD11F/2O olpeY8getbGV/VCx1tUz3gmOthzOdlre+La++LrpxP1G8h07RFPr6dL1YqTw9q6gGT /kJ9TlmfiYSmwQKNxvpOHMExBeJkKvaFmo4Z1Igc= Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 6A1C160F5F for ; Wed, 23 Oct 2019 23:51:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1571874695; bh=RQzk63vXXXNk90usgWk/wx+IVC7KwqQNIfrdUilq1wg=; h=Date:From:To:Subject:From; b=Sebe89sfJjKrrsOpcmAaEqYI3PDqiWvMcyY7coEc46lE/XhSI9beT9UrgkD11F/2O olpeY8getbGV/VCx1tUz3gmOthzOdlre+La++LrpxP1G8h07RFPr6dL1YqTw9q6gGT /kJ9TlmfiYSmwQKNxvpOHMExBeJkKvaFmo4Z1Igc= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 23 Oct 2019 16:51:35 -0700 From: asutoshd@codeaurora.org To: linux-scsi@vger.kernel.org Subject: Query: SCSI Device node creation when UFS is loaded as a module Message-ID: <468eb805fa69da76c88a0a37aa209c7f@codeaurora.org> X-Sender: asutoshd@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-scsi-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-scsi@vger.kernel.org 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/<...>/.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 ? I've looked into sd.c but I couldn't figure out the exact place yet. Any pointers please? TIA -asd