From: <Christian.Gromm@microchip.com>
To: <erosca@de.adit-jv.com>
Cc: <andrey.shvetsov@k2l.de>,
<driverdev-devel@linuxdriverproject.org>, <sudipi@jp.adit-jv.com>,
<gregkh@linuxfoundation.org>, <roscaeugeniu@gmail.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 16/28] staging: most: sound: call snd_card_new with struct device
Date: Mon, 29 Apr 2019 09:29:45 +0000 [thread overview]
Message-ID: <1556530363.2904.8.camel@microchip.com> (raw)
In-Reply-To: <20190424185032.GA9019@vmlxhi-102.adit-jv.com>
On Mi, 2019-04-24 at 20:50 +0200, Eugeniu Rosca wrote:
> External E-Mail
>
>
> Hi Christian,
>
> On Tue, 08 May 2018 02:46:44 -0700, Christian Gromm wrote:
> >
> > This patch is needed as function snd_card_new needs a valid
> > parent device. Passing a NULL pointer leads to kernel Ooops.
> >
> > Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
> > ---
> > drivers/staging/most/core.h | 1 +
> > drivers/staging/most/sound/sound.c | 2 +-
> > drivers/staging/most/usb/usb.c | 1 +
> > 3 files changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/most/core.h
> > b/drivers/staging/most/core.h
> > index 7a3c70bead19..64cc02f161e7 100644
> > --- a/drivers/staging/most/core.h
> > +++ b/drivers/staging/most/core.h
> > @@ -230,6 +230,7 @@ struct mbo {
> > */
> > struct most_interface {
> > struct device dev;
> > + struct device *driver_dev;
> > struct module *mod;
> > enum most_interface_type interface;
> > const char *description;
> > diff --git a/drivers/staging/most/sound/sound.c
> > b/drivers/staging/most/sound/sound.c
> > index 18f722410a63..04c18323c2ea 100644
> > --- a/drivers/staging/most/sound/sound.c
> > +++ b/drivers/staging/most/sound/sound.c
> > @@ -590,7 +590,7 @@ static int audio_probe_channel(struct
> > most_interface *iface, int channel_id,
> > if (ret < 0)
> > return ret;
> >
> > - ret = snd_card_new(NULL, -1, card_name, THIS_MODULE,
> > + ret = snd_card_new(&iface->dev, -1, card_name,
> > THIS_MODULE,
> > sizeof(*channel), &card);
> > if (ret < 0)
> > return ret;
> > diff --git a/drivers/staging/most/usb/usb.c
> > b/drivers/staging/most/usb/usb.c
> > index 5ed1dccc0839..f18726049528 100644
> > --- a/drivers/staging/most/usb/usb.c
> > +++ b/drivers/staging/most/usb/usb.c
> > @@ -1043,6 +1043,7 @@ hdm_probe(struct usb_interface *interface,
> > const struct usb_device_id *id)
> > mdev->link_stat_timer.expires = jiffies + (2 * HZ);
> >
> > mdev->iface.mod = hdm_usb_fops.owner;
> > + mdev->iface.driver_dev = &interface->dev;
> > mdev->iface.interface = ITYPE_USB;
> > mdev->iface.configure = hdm_configure_channel;
> > mdev->iface.request_netinfo = hdm_request_netinfo;
> Just for your information, when mapping commits from vanilla to those
> from https://github.com/microchip-ais/linux/commits/mld-1.8.0, we've
> stumbled upon some subtle but striking difference between mld-1.8.0
> commit [0] and v4.18-rc1 commit [1]. The latter looks like an
> upstreamed
> version of the former. However, while commit [0] creates a new 'dev'
> member in 'struct most_interface' and uses it consistently, commit
> [1]
> creates 'driver_dev' and uses it intermixed with 'dev'.
This looks sort of suspicious. I'll check it.
Thanks for letting me know.
Regards,
Chris
>
> Since we don't use aim-sound, we just signal this feedback to you
> as FWIW without sending a patch (which we can't test).
>
> [0] https://github.com/microchip-ais/linux/commit/2fef0f89f04703
> ("staging: most: add struct device to most interface")
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.gi
> t/commit/?id=69c90cf1b2faf5
> ("staging: most: sound: call snd_card_new with struct device")
>
prev parent reply other threads:[~2019-04-29 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180609182902.A31D621C28@pdx-korg-gitolite-1.ci.codeaurora.org>
2019-04-24 18:50 ` [PATCH 16/28] staging: most: sound: call snd_card_new with struct device Eugeniu Rosca
2019-04-29 9:29 ` Christian.Gromm [this message]
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=1556530363.2904.8.camel@microchip.com \
--to=christian.gromm@microchip.com \
--cc=andrey.shvetsov@k2l.de \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=erosca@de.adit-jv.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roscaeugeniu@gmail.com \
--cc=sudipi@jp.adit-jv.com \
/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