From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> To: Florian Fainelli <f.fainelli@gmail.com>, Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Nicolas Saenz Julienne <nsaenz@kernel.org>, Chris Brandt <chris.brandt@renesas.com>, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-renesas-soc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Prabhakarprabhakar.csengg@gmail.com, Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Subject: [PATCH v2 0/3] i2c/busses: Use platform_get_irq/_optional() variants to fetch IRQ's Date: Tue, 21 Dec 2021 17:53:19 +0000 [thread overview] Message-ID: <20211221175322.7096-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw) Hi All, This patch series aims to drop using platform_get_resource() for IRQ types in preparation for removal of static setup of IRQ resource from DT core code. Dropping usage of platform_get_resource() was agreed based on the discussion [0]. [0] https://patchwork.kernel.org/project/linux-renesas-soc/ patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/ Cheers, Prabhakar Lad Prabhakar (3): i2c: bcm2835: Use platform_get_irq() to get the interrupt i2c: sh_mobile: Use platform_get_irq_optional() to get the interrupt i2c: riic: Use platform_get_irq() to get the interrupt drivers/i2c/busses/i2c-bcm2835.c | 11 ++++------ drivers/i2c/busses/i2c-riic.c | 10 ++++----- drivers/i2c/busses/i2c-sh_mobile.c | 34 +++++++++++++++++++++++------- 3 files changed, 35 insertions(+), 20 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> To: Florian Fainelli <f.fainelli@gmail.com>, Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Nicolas Saenz Julienne <nsaenz@kernel.org>, Chris Brandt <chris.brandt@renesas.com>, Wolfram Sang <wsa+renesas@sang-engineering.com>, linux-i2c@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-renesas-soc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Prabhakarprabhakar.csengg@gmail.com, Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Subject: [PATCH v2 0/3] i2c/busses: Use platform_get_irq/_optional() variants to fetch IRQ's Date: Tue, 21 Dec 2021 17:53:19 +0000 [thread overview] Message-ID: <20211221175322.7096-1-prabhakar.mahadev-lad.rj@bp.renesas.com> (raw) Hi All, This patch series aims to drop using platform_get_resource() for IRQ types in preparation for removal of static setup of IRQ resource from DT core code. Dropping usage of platform_get_resource() was agreed based on the discussion [0]. [0] https://patchwork.kernel.org/project/linux-renesas-soc/ patch/20211209001056.29774-1-prabhakar.mahadev-lad.rj@bp.renesas.com/ Cheers, Prabhakar Lad Prabhakar (3): i2c: bcm2835: Use platform_get_irq() to get the interrupt i2c: sh_mobile: Use platform_get_irq_optional() to get the interrupt i2c: riic: Use platform_get_irq() to get the interrupt drivers/i2c/busses/i2c-bcm2835.c | 11 ++++------ drivers/i2c/busses/i2c-riic.c | 10 ++++----- drivers/i2c/busses/i2c-sh_mobile.c | 34 +++++++++++++++++++++++------- 3 files changed, 35 insertions(+), 20 deletions(-) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-12-21 17:53 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-21 17:53 Lad Prabhakar [this message] 2021-12-21 17:53 ` [PATCH v2 0/3] i2c/busses: Use platform_get_irq/_optional() variants to fetch IRQ's Lad Prabhakar 2021-12-21 17:53 ` [PATCH v2 1/3] i2c: bcm2835: Use platform_get_irq() to get the interrupt Lad Prabhakar 2021-12-21 17:53 ` Lad Prabhakar 2021-12-21 18:24 ` Florian Fainelli 2021-12-21 18:24 ` Florian Fainelli 2022-01-03 9:18 ` Wolfram Sang 2022-01-03 9:18 ` Wolfram Sang 2021-12-21 17:53 ` [PATCH v2 2/3] i2c: sh_mobile: Use platform_get_irq_optional() " Lad Prabhakar 2021-12-21 17:53 ` Lad Prabhakar 2021-12-22 9:20 ` Geert Uytterhoeven 2021-12-22 9:20 ` Geert Uytterhoeven 2021-12-22 9:49 ` Wolfram Sang 2021-12-22 9:49 ` Wolfram Sang 2021-12-25 17:48 ` Andy Shevchenko 2021-12-25 17:48 ` Andy Shevchenko 2021-12-25 23:45 ` Prabhakar Mahadev Lad 2021-12-25 23:45 ` Prabhakar Mahadev Lad 2021-12-26 8:40 ` Andy Shevchenko 2021-12-26 8:40 ` Andy Shevchenko 2021-12-26 10:03 ` Lad, Prabhakar 2021-12-26 10:03 ` Lad, Prabhakar 2022-01-03 9:19 ` Wolfram Sang 2022-01-03 9:19 ` Wolfram Sang 2021-12-21 17:53 ` [PATCH v2 3/3] i2c: riic: Use platform_get_irq() " Lad Prabhakar 2021-12-21 17:53 ` Lad Prabhakar 2021-12-22 9:52 ` Wolfram Sang 2021-12-22 9:52 ` Wolfram Sang 2021-12-22 13:00 ` Geert Uytterhoeven 2021-12-22 13:00 ` Geert Uytterhoeven 2022-01-03 9:19 ` Wolfram Sang 2022-01-03 9:19 ` Wolfram Sang
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=20211221175322.7096-1-prabhakar.mahadev-lad.rj@bp.renesas.com \ --to=prabhakar.mahadev-lad.rj@bp.renesas.com \ --cc=Prabhakarprabhakar.csengg@gmail.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=chris.brandt@renesas.com \ --cc=f.fainelli@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=linux-rpi-kernel@lists.infradead.org \ --cc=nsaenz@kernel.org \ --cc=rjui@broadcom.com \ --cc=sbranden@broadcom.com \ --cc=wsa+renesas@sang-engineering.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: 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.