From: Pawel Laszczak <pawell@cadence.com>
To: <peter.chen@nxp.com>
Cc: <gregkh@linuxfoundation.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <balbi@kernel.org>,
<colin.king@canonical.com>, <rogerq@ti.com>,
<kurahul@cadence.com>, <nsekhar@ti.com>, <a-govindraju@ti.com>,
Pawel Laszczak <pawell@cadence.com>
Subject: [PATCH v5 05/10] usb: cdns3: Changed type of gadget_dev in cdns structure
Date: Mon, 7 Dec 2020 11:32:22 +0100 [thread overview]
Message-ID: <20201207103227.606-6-pawell@cadence.com> (raw)
In-Reply-To: <20201207103227.606-1-pawell@cadence.com>
Patch changes the type for gadget_dev pointer in cdns structure from
pointer to cdns3_device structure to void pointer.
This filed is in reusable code and after this change it will be used to
point to both cdns3_device or cdnsp_device objects.
Signed-off-by: Pawel Laszczak <pawell@cadence.com>
Tested-by: Aswath Govindraju <a-govindraju@ti.com>
---
drivers/usb/cdns3/core.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/cdns3/core.h b/drivers/usb/cdns3/core.h
index f664eb2d8df4..cbd2e1cc8eb1 100644
--- a/drivers/usb/cdns3/core.h
+++ b/drivers/usb/cdns3/core.h
@@ -64,7 +64,7 @@ struct cdns3_platform_data {
* @roles: array of supported roles for this controller
* @role: current role
* @host_dev: the child host device pointer for cdns core
- * @gadget_dev: the child gadget device pointer for cdns3 core
+ * @gadget_dev: the child gadget device pointer
* @usb2_phy: pointer to USB2 PHY
* @usb3_phy: pointer to USB3 PHY
* @mutex: the mutex for concurrent code at driver
@@ -104,7 +104,7 @@ struct cdns {
struct cdns_role_driver *roles[USB_ROLE_DEVICE + 1];
enum usb_role role;
struct platform_device *host_dev;
- struct cdns3_device *gadget_dev;
+ void *gadget_dev;
struct phy *usb2_phy;
struct phy *usb3_phy;
/* mutext used in workqueue*/
--
2.17.1
next prev parent reply other threads:[~2020-12-07 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 10:32 [PATCH v5 00/10] Introduced new Cadence USBSSP DRD Driver Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 01/10] usb: cdns3: Add support for DRD CDNSP Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 02/10] usb: cdns3: Split core.c into cdns3-plat and core.c file Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 03/10] usb: cdns3: Moves reusable code to separate module Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 04/10] usb: cdns3: Refactoring names in reusable code Pawel Laszczak
2020-12-07 10:32 ` Pawel Laszczak [this message]
2020-12-07 10:32 ` [PATCH v5 06/10] usb: cdnsp: Device side header file for CDNSP driver Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 07/10] usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 08/10] usb: cdnsp: Add tracepoints for CDNSP driver Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 09/10] usb: cdns3: Change file names for cdns3 driver Pawel Laszczak
2020-12-07 10:32 ` [PATCH v5 10/10] MAINTAINERS: add Cadence USBSSP DRD IP driver entry Pawel Laszczak
2020-12-08 9:15 ` [PATCH v5 00/10] Introduced new Cadence USBSSP DRD Driver Peter Chen
2020-12-10 0:39 ` Peter Chen
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=20201207103227.606-6-pawell@cadence.com \
--to=pawell@cadence.com \
--cc=a-govindraju@ti.com \
--cc=balbi@kernel.org \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.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;
as well as URLs for NNTP newsgroup(s).