From: Rohit Sarkar <rohitsarkar5398@gmail.com> To: linux-iio@vger.kernel.org Cc: jic23@kernel.org, gregkh@linuxfoundation.org, devel@driverdev.osuosl.org Subject: [PATCH v2] staging: iio: update TODO Date: Tue, 25 Feb 2020 20:31:02 +0530 [thread overview] Message-ID: <5e5536b1.1c69fb81.5f37a.daf6@mx.google.com> (raw) Since there are no uses of the old GPIO API, remove the item from the TODO and some new items. Changes from v1: Add work item mentioned by Alexandru in https://marc.info/?l=linux-iio&m=158261515624212&w=2 Signed-off-by: Rohit Sarkar <rohitsarkar5398@gmail.com> --- drivers/staging/iio/TODO | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/iio/TODO b/drivers/staging/iio/TODO index 1b8ebf2c1b69..e54510c2ef5f 100644 --- a/drivers/staging/iio/TODO +++ b/drivers/staging/iio/TODO @@ -1,11 +1,17 @@ -2018-04-15 +2020-02-25 -All affected drivers: -Convert all uses of the old GPIO API from <linux/gpio.h> to the -GPIO descriptor API in <linux/gpio/consumer.h> and look up GPIO -lines from device tree, ACPI or board files, board files should -use <linux/gpio/machine.h>. +- Documentation + - Binding docs for devices that are obviously used via device tree + - Yaml conversions for abandoned drivers + - ABI Documentation + - Audit driviers/iio/staging/Documentation +- Replace iio_dev->mlock by either a local lock or use iio_claim_direct. + (Requires analysis of the purpose of the lock.) + +- Converting drivers from device tree centric to more generic property handlers + Refactor old platform_data constructs from drivers and convert it to state + struct and using property handlers and readers. ADI Drivers: CC the device-drivers-devel@blackfin.uclinux.org mailing list when -- 2.23.0.385.gbc12974a89
WARNING: multiple messages have this Message-ID (diff)
From: Rohit Sarkar <rohitsarkar5398@gmail.com> To: linux-iio@vger.kernel.org Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org, jic23@kernel.org Subject: [PATCH v2] staging: iio: update TODO Date: Tue, 25 Feb 2020 20:31:02 +0530 [thread overview] Message-ID: <5e5536b1.1c69fb81.5f37a.daf6@mx.google.com> (raw) Since there are no uses of the old GPIO API, remove the item from the TODO and some new items. Changes from v1: Add work item mentioned by Alexandru in https://marc.info/?l=linux-iio&m=158261515624212&w=2 Signed-off-by: Rohit Sarkar <rohitsarkar5398@gmail.com> --- drivers/staging/iio/TODO | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/iio/TODO b/drivers/staging/iio/TODO index 1b8ebf2c1b69..e54510c2ef5f 100644 --- a/drivers/staging/iio/TODO +++ b/drivers/staging/iio/TODO @@ -1,11 +1,17 @@ -2018-04-15 +2020-02-25 -All affected drivers: -Convert all uses of the old GPIO API from <linux/gpio.h> to the -GPIO descriptor API in <linux/gpio/consumer.h> and look up GPIO -lines from device tree, ACPI or board files, board files should -use <linux/gpio/machine.h>. +- Documentation + - Binding docs for devices that are obviously used via device tree + - Yaml conversions for abandoned drivers + - ABI Documentation + - Audit driviers/iio/staging/Documentation +- Replace iio_dev->mlock by either a local lock or use iio_claim_direct. + (Requires analysis of the purpose of the lock.) + +- Converting drivers from device tree centric to more generic property handlers + Refactor old platform_data constructs from drivers and convert it to state + struct and using property handlers and readers. ADI Drivers: CC the device-drivers-devel@blackfin.uclinux.org mailing list when -- 2.23.0.385.gbc12974a89 _______________________________________________ devel mailing list devel@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2020-02-25 15:01 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-25 15:01 Rohit Sarkar [this message] 2020-02-25 15:01 ` [PATCH v2] staging: iio: update TODO Rohit Sarkar -- strict thread matches above, loose matches on Subject: below -- 2020-02-24 19:59 [PATCH] " Rohit Sarkar 2020-02-25 14:49 ` [PATCH v2] " Rohit Sarkar 2020-02-28 17:36 ` Jonathan Cameron 2020-02-28 19:46 ` Rohit Sarkar
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=5e5536b1.1c69fb81.5f37a.daf6@mx.google.com \ --to=rohitsarkar5398@gmail.com \ --cc=devel@driverdev.osuosl.org \ --cc=gregkh@linuxfoundation.org \ --cc=jic23@kernel.org \ --cc=linux-iio@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: linkBe 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.