From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Evan Green <evgreen@chromium.org>
Cc: Andy Gross <andy.gross@linaro.org>,
Brian Norris <briannorris@chromium.org>,
Ben Chan <benchan@chromium.org>,
linux-arm-msm@vger.kernel.org,
David Brown <david.brown@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] soc: qcom: rmtfs-mem: Add class to enable uevents
Date: Fri, 21 Dec 2018 14:05:33 -0800 [thread overview]
Message-ID: <20181221220533.GB9704@minitux> (raw)
In-Reply-To: <20181221201001.160613-2-evgreen@chromium.org>
On Fri 21 Dec 12:10 PST 2018, Evan Green wrote:
> Currently the qcom_rmtfs_memN devices are entirely invisible to the udev world.
> Add a class to the rmtfs device so that uevents fire when the device is added.
>
> Signed-off-by: Evan Green <evgreen@chromium.org>
I agree with Brian on the whitespace chances, apart from that you have
my
Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Regards,
Bjorn
> ---
>
> Changes in v2:
> - Moved class registration/deregistration into init/exit routines (Brian)
>
> drivers/soc/qcom/rmtfs_mem.c | 29 +++++++++++++++++++++--------
> 1 file changed, 21 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/soc/qcom/rmtfs_mem.c b/drivers/soc/qcom/rmtfs_mem.c
> index 97bb5989aa211..99a1363ece254 100644
> --- a/drivers/soc/qcom/rmtfs_mem.c
> +++ b/drivers/soc/qcom/rmtfs_mem.c
> @@ -132,6 +132,11 @@ static int qcom_rmtfs_mem_release(struct inode *inode, struct file *filp)
> return 0;
> }
>
> +static struct class rmtfs_class = {
> + .owner = THIS_MODULE,
> + .name = "rmtfs",
> +};
> +
> static const struct file_operations qcom_rmtfs_mem_fops = {
> .owner = THIS_MODULE,
> .open = qcom_rmtfs_mem_open,
> @@ -199,8 +204,8 @@ static int qcom_rmtfs_mem_probe(struct platform_device *pdev)
>
> dev_set_name(&rmtfs_mem->dev, "qcom_rmtfs_mem%d", client_id);
> rmtfs_mem->dev.id = client_id;
> + rmtfs_mem->dev.class = &rmtfs_class;
> rmtfs_mem->dev.devt = MKDEV(MAJOR(qcom_rmtfs_mem_major), client_id);
> -
> ret = cdev_device_add(&rmtfs_mem->cdev, &rmtfs_mem->dev);
> if (ret) {
> dev_err(&pdev->dev, "failed to add cdev: %d\n", ret);
> @@ -239,7 +244,6 @@ static int qcom_rmtfs_mem_probe(struct platform_device *pdev)
> cdev_device_del(&rmtfs_mem->cdev, &rmtfs_mem->dev);
> put_device:
> put_device(&rmtfs_mem->dev);
> -
> return ret;
> }
>
> @@ -258,7 +262,6 @@ static int qcom_rmtfs_mem_remove(struct platform_device *pdev)
>
> cdev_device_del(&rmtfs_mem->cdev, &rmtfs_mem->dev);
> put_device(&rmtfs_mem->dev);
> -
> return 0;
> }
>
> @@ -277,32 +280,42 @@ static struct platform_driver qcom_rmtfs_mem_driver = {
> },
> };
>
> -static int qcom_rmtfs_mem_init(void)
> +static int __init qcom_rmtfs_mem_init(void)
> {
> int ret;
>
> + ret = class_register(&rmtfs_class);
> + if (ret)
> + return ret;
> +
> ret = alloc_chrdev_region(&qcom_rmtfs_mem_major, 0,
> QCOM_RMTFS_MEM_DEV_MAX, "qcom_rmtfs_mem");
> if (ret < 0) {
> pr_err("qcom_rmtfs_mem: failed to allocate char dev region\n");
> - return ret;
> + goto unregister_class;
> }
>
> ret = platform_driver_register(&qcom_rmtfs_mem_driver);
> if (ret < 0) {
> pr_err("qcom_rmtfs_mem: failed to register rmtfs_mem driver\n");
> - unregister_chrdev_region(qcom_rmtfs_mem_major,
> - QCOM_RMTFS_MEM_DEV_MAX);
> + goto unregister_chrdev;
> }
>
> + return 0;
> +
> +unregister_chrdev:
> + unregister_chrdev_region(qcom_rmtfs_mem_major, QCOM_RMTFS_MEM_DEV_MAX);
> +unregister_class:
> + class_unregister(&rmtfs_class);
> return ret;
> }
> module_init(qcom_rmtfs_mem_init);
>
> -static void qcom_rmtfs_mem_exit(void)
> +static void __exit qcom_rmtfs_mem_exit(void)
> {
> platform_driver_unregister(&qcom_rmtfs_mem_driver);
> unregister_chrdev_region(qcom_rmtfs_mem_major, QCOM_RMTFS_MEM_DEV_MAX);
> + class_unregister(&rmtfs_class);
> }
> module_exit(qcom_rmtfs_mem_exit);
>
> --
> 2.18.1
>
next prev parent reply other threads:[~2018-12-21 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 20:09 [PATCH v2 0/2] soc: qcom: rmtfs-mem: Support non-root rmtfs daemons Evan Green
2018-12-21 20:10 ` [PATCH v2 1/2] soc: qcom: rmtfs-mem: Add class to enable uevents Evan Green
2018-12-21 21:55 ` Brian Norris
2018-12-21 22:05 ` Bjorn Andersson [this message]
2019-01-02 17:15 ` Evan Green
2018-12-21 20:10 ` [PATCH v2 2/2] soc: qcom: rmtfs-mem: Make sysfs attributes world-readable Evan Green
2018-12-21 22:06 ` Bjorn Andersson
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=20181221220533.GB9704@minitux \
--to=bjorn.andersson@linaro.org \
--cc=andy.gross@linaro.org \
--cc=benchan@chromium.org \
--cc=briannorris@chromium.org \
--cc=david.brown@linaro.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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