All of lore.kernel.org
 help / color / mirror / Atom feed
From: <ckim@etri.re.kr>
To: "'Greg KH'" <greg@kroah.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: RE: can't find device_create funtion in a driver containing cdev (habanalabs)
Date: Thu, 29 Apr 2021 09:56:09 +0900	[thread overview]
Message-ID: <018201d73c92$7153fb60$53fbf220$@etri.re.kr> (raw)
In-Reply-To: <YImqLM4JkAMWjSy6@kroah.com>

Hi, Greg KH,

To me cdev_device_add seems to be calling only cdev_add(below). 
In this case since dev->devt already holds dev_t value ("hl%d"), it just
sets cdev_set_parent and cdev_add. 

int cdev_device_add(struct cdev *cdev, struct device *dev)
{       
    int rc = 0;
        
    if (dev->devt) {
        cdev_set_parent(cdev, &dev->kobj);

        rc = cdev_add(cdev, dev->devt, 1);
        if (rc)
            return rc;
    }   
    
    rc = device_add(dev);
    if (rc)
        cdev_del(cdev);

    return rc;
}

Are you sure cdev_device_add contains "device_create function"? Shouldn't
device_create be called after class_create?
Class_create is called much later inside the function device_cdev_sysfs_add
later in hl_device_init function(line 1238).

And device_cdev_sysfs_add contains this code. The hl_sysfs_init calls
device_add_groups which calls sysfs_create_groups.
Isn't this sysfs_create_groups function by any chance a group equivalent of
device_create function?

/* hl_sysfs_init() must be done after adding the device to the system */
    rc = hl_sysfs_init(hdev);
    if (rc) {
        dev_err(hdev->dev, "failed to initialize sysfs\n");
        goto delete_ctrl_cdev_device;
    }

    hdev->cdev_sysfs_created = true;

Thanks for helps and regards,

Chan Kim

> -----Original Message-----
> From: Greg KH <greg@kroah.com>
> Sent: Thursday, April 29, 2021 3:32 AM
> To: ckim@etri.re.kr
> Cc: kernelnewbies@kernelnewbies.org
> Subject: Re: can't find device_create funtion in a driver containing cdev
> (habanalabs)
> 
> On Wed, Apr 28, 2021 at 10:46:21PM +0900, ckim@etri.re.kr wrote:
> > Hello list members,
> >
> > In habanalabs' goya chip driver,
> > (https://elixir.bootlin.com/linux/v5.4.21/source/drivers/misc/habanala
> > bs/dev
> > ice.c#L1057)
> >
> > I can see cdev_init, cdev_add and class_create functions.
> >
> > Cdev_init is called insde device_init_cdev and cdev_add is called from
> > device_cdev_sysfs_add -> cdev_device_add.
> >
> > I can see class_create being called too. But I couldn't find
> > device_create function (which is used to make sysfs entry?)
> >
> > Can anyone tell me where device_create is called? (or where
> > alternative method is being used?)
> 
> Happens in the call to cdev_device_add()
> 





_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2021-04-29  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 13:46 can't find device_create funtion in a driver containing cdev (habanalabs) ckim
2021-04-28 18:32 ` Greg KH
2021-04-29  0:56   ` ckim [this message]
2021-04-29  7:29     ` 'Greg KH'

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='018201d73c92$7153fb60$53fbf220$@etri.re.kr' \
    --to=ckim@etri.re.kr \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.