From: "Mukunda, Vijendar" <Vijendar.Mukunda@amd.com> To: Hui Wang <firstname.lastname@example.org>, Mark Brown <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com> Subject: RE: [PATCH v2] ASoC: amd: put off registering mach platform_dev to avoid -517 err Date: Fri, 22 May 2020 15:14:21 +0000 Message-ID: <DM6PR12MB2633FECD2F752EFE8DD4A6AA97B40@DM6PR12MB2633.namprd12.prod.outlook.com> (raw) In-Reply-To: <DM6PR12MB26335DA69D595C332A20779697B40@DM6PR12MB2633.namprd12.prod.outlook.com> > -----Original Message----- > From: Mukunda, Vijendar > Sent: Friday, May 22, 2020 8:01 PM > To: 'Hui Wang' <firstname.lastname@example.org>; Mark Brown > <email@example.com> > Cc: firstname.lastname@example.org > Subject: RE: [PATCH v2] ASoC: amd: put off registering mach platform_dev to > avoid -517 err > > [AMD Official Use Only - Internal Distribution Only] > > > > > -----Original Message----- > > From: Hui Wang <email@example.com> > > Sent: Friday, May 22, 2020 7:27 PM > > To: Mukunda, Vijendar <Vijendar.Mukunda@amd.com>; Mark Brown > > <firstname.lastname@example.org> > > Cc: email@example.com > > Subject: Re: [PATCH v2] ASoC: amd: put off registering mach platform_dev to > > avoid -517 err > > > > > > On 2020/5/22 下午8:59, Hui Wang wrote: > > > > > > On 2020/5/22 下午7:28, Mukunda, Vijendar wrote: > > >> > > >>> -----Original Message----- > > >>> From: Mark Brown <firstname.lastname@example.org> > > >>> Sent: Friday, May 22, 2020 4:52 PM > > >>> To: Mukunda, Vijendar <Vijendar.Mukunda@amd.com> > > >>> Cc: Hui Wang <email@example.com>; firstname.lastname@example.org > > >>> Subject: Re: [PATCH v2] ASoC: amd: put off registering mach > > >>> platform_dev to > > >>> avoid -517 err > > >>> > > >>> On Fri, May 22, 2020 at 11:13:43AM +0000, Mukunda, Vijendar wrote: > > >>> > > >>>> Does sound card registration failure at boot time due to modules > > >>>> loading > > >>> order can be considered as bug ? > > >>> > > >>> No, this is totally normal. If it failed to bind ever then that'd be a > > >>> problem but this is just deferring. > > >> In that case, we don't need this work around I guess. > > >> At maximum during boot time, we may see few sound card registration > > >> failure logs, > > >> Which is normal. > > >> > > >> With this change, our concept of ACP parent device which will create > > >> platform devices > > >> for DMA driver, Generic DMIC driver and Machine driver will be changed. > > >> We implemented same design for Raven I2S driver as well which got > > >> productized. > > >> > > > OK, got it. It doesn't affect the sound function anyway. > > > > BTW, so far, I have not seen the -517 error from ubuntu kernel dmesg on > > PC or laptop. Maybe this is the 1st driver to print this error in the > > dmesg on PC or laptop, so I guess it probably confuses the users or our QA. > > > > We have similar design for I2S endpoint which got productized on other OS > variant. > Most of the PC and Laptop comes up with Legacy HD Audio Driver solution. > This is ASoC based driver. > As this failure message only appears during boot time, Its okay to go ahead. > End user should really worry if sound card is not created even after system > boots up. I have seen sample implementation of deferred probe in one of the machine driver code using late_initcall() API. Not sure how this api really works which will resolve the modules loading sequence issue.
next prev parent reply index Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-22 8:17 Hui Wang 2020-05-22 9:16 ` Mukunda, Vijendar 2020-05-22 11:08 ` Mark Brown 2020-05-22 11:13 ` Mukunda, Vijendar 2020-05-22 11:22 ` Mark Brown 2020-05-22 11:28 ` Mukunda, Vijendar 2020-05-22 12:59 ` Hui Wang 2020-05-22 13:57 ` Hui Wang 2020-05-22 14:30 ` Mukunda, Vijendar 2020-05-22 15:14 ` Mukunda, Vijendar [this message] 2020-05-22 15:32 ` Mark Brown 2020-05-23 0:11 ` Mukunda, Vijendar 2020-05-25 3:32 ` Hui Wang 2020-05-22 19:10 ` kbuild test robot
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=DM6PR12MB2633FECD2F752EFE8DD4A6AA97B40@DM6PR12MB2633.namprd12.prod.outlook.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Alsa-Devel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/alsa-devel/0 alsa-devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 alsa-devel alsa-devel/ https://lore.kernel.org/alsa-devel \ email@example.com public-inbox-index alsa-devel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.alsa-project.alsa-devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git