From: "Chetan Chinnadagudihundi Ravindranath (Consultant) (QUIC)" <quic_cchinnad@quicinc.com>
To: Bart Van Assche <bvanassche@acm.org>, <jejb@linux.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH V1] scsi: ufs: Get boot device storage type from command line
Date: Thu, 28 Jul 2022 14:05:18 +0530 [thread overview]
Message-ID: <c66ffd91-8649-edb7-86dc-422ae82e1b84@quicinc.com> (raw)
In-Reply-To: <a09de6e0-700b-0715-06a8-150ab41e8e7f@acm.org>
Hi Brat,
Thanks for you response!
Yes, since SCSI_UFSHCD=y am selecting UFS_QCOM_CMDLINE=y so that it gets
__setup() declarations. I am able to read the command line arguments and
get this "androidboot.bootdevice=" info. I had cross checked again.
Thanks,
Chetan C R
On 7/27/2022 11:16 PM, Bart Van Assche wrote:
> On 7/27/22 01:28, Chetan C R wrote:
>> diff --git a/drivers/ufs/Kconfig b/drivers/ufs/Kconfig
>> index 90226f7..9d2f84e 100644
>> --- a/drivers/ufs/Kconfig
>> +++ b/drivers/ufs/Kconfig
>> @@ -9,6 +9,7 @@ menuconfig SCSI_UFSHCD
>> select PM_DEVFREQ
>> select DEVFREQ_GOV_SIMPLE_ONDEMAND
>> select NLS
>> + select UFS_QCOM_CMDLINE if ARCH_QCOM
>> help
>> Enables support for UFS (Universal Flash Storage) host
>> controllers.
>> A UFS host controller is an electronic component that is able to
>
> [ ... ]
>
>> +__setup("androidboot.bootdevice=", get_android_boot_dev_v3);
>
> How can this work since __setup() declarations should occur in the
> core kernel and since the ufshcd driver can be built as a kernel module?
>
> Thanks,
>
> Bart.
next prev parent reply other threads:[~2022-07-28 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 8:28 Chetan C R
2022-07-27 13:04 ` kernel test robot
2022-07-27 17:46 ` Bart Van Assche
2022-07-28 8:35 ` Chetan Chinnadagudihundi Ravindranath (Consultant) (QUIC) [this message]
2022-07-28 13:33 ` Bart Van Assche
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=c66ffd91-8649-edb7-86dc-422ae82e1b84@quicinc.com \
--to=quic_cchinnad@quicinc.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®