From: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
To: johan@kernel.org
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, peter_hong@fintek.com.tw,
"Ji-Ze Hong (Peter Hong)" <hpeter+linux_kernel@gmail.com>
Subject: [PATCH V1 2/6] USB: serial: f81232: Force F81534A with RS232 mode
Date: Thu, 6 Jun 2019 10:54:12 +0800 [thread overview]
Message-ID: <1559789656-15847-3-git-send-email-hpeter+linux_kernel@gmail.com> (raw)
In-Reply-To: <1559789656-15847-1-git-send-email-hpeter+linux_kernel@gmail.com>
Force F81534A series UARTs with RS232 mode in port_probe().
Signed-off-by: Ji-Ze Hong (Peter Hong) <hpeter+linux_kernel@gmail.com>
---
drivers/usb/serial/f81232.c | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/drivers/usb/serial/f81232.c b/drivers/usb/serial/f81232.c
index 84efcc66aa56..75dfc0b9ef30 100644
--- a/drivers/usb/serial/f81232.c
+++ b/drivers/usb/serial/f81232.c
@@ -83,12 +83,22 @@ MODULE_DEVICE_TABLE(usb, id_table);
#define F81232_F81232_TYPE 1
#define F81232_F81534A_TYPE 2
+/* Serial port self GPIO control, 2bytes [control&output data][input data] */
+#define F81534A_GPIO_REG 0x10e
+#define F81534A_GPIO_MODE2_DIR BIT(6) /* 1: input, 0: output */
+#define F81534A_GPIO_MODE1_DIR BIT(5)
+#define F81534A_GPIO_MODE0_DIR BIT(4)
+#define F81534A_GPIO_MODE2_OUTPUT BIT(2)
+#define F81534A_GPIO_MODE1_OUTPUT BIT(1)
+#define F81534A_GPIO_MODE0_OUTPUT BIT(0)
+
struct f81232_private {
struct mutex lock;
u8 modem_control;
u8 modem_status;
u8 shadow_lcr;
u8 device_type;
+ u8 gpio_mode;
speed_t baud_base;
struct work_struct lsr_work;
struct work_struct interrupt_work;
@@ -871,6 +881,11 @@ static int f81232_port_probe(struct usb_serial_port *port)
switch (priv->device_type) {
case F81232_F81534A_TYPE:
priv->process_read_urb = f81534a_process_read_urb;
+ priv->gpio_mode = F81534A_GPIO_MODE2_DIR;
+
+ /* tri-state with pull-high, default RS232 Mode */
+ status = f81232_set_register(port, F81534A_GPIO_REG,
+ priv->gpio_mode);
break;
case F81232_F81232_TYPE:
--
2.7.4
next prev parent reply other threads:[~2019-06-06 2:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 2:54 [PATCH V1 0/6] USB: serial: f81232: Add F81534A support Ji-Ze Hong (Peter Hong)
2019-06-06 2:54 ` [PATCH V1 1/6] " Ji-Ze Hong (Peter Hong)
2019-08-28 14:56 ` Johan Hovold
2019-06-06 2:54 ` Ji-Ze Hong (Peter Hong) [this message]
2019-08-28 14:58 ` [PATCH V1 2/6] USB: serial: f81232: Force F81534A with RS232 mode Johan Hovold
2019-06-06 2:54 ` [PATCH V1 3/6] USB: serial: f81232: Add generator for F81534A Ji-Ze Hong (Peter Hong)
2019-08-28 15:02 ` Johan Hovold
2019-09-02 2:59 ` Ji-Ze Hong (Peter Hong)
2019-09-20 8:15 ` Johan Hovold
2019-06-06 2:54 ` [PATCH V1 4/6] USB: serial: f81232: Add tx_empty function Ji-Ze Hong (Peter Hong)
2019-08-28 15:16 ` Johan Hovold
2019-06-06 2:54 ` [PATCH V1 5/6] USB: serial: f81232: Use devm_kzalloc Ji-Ze Hong (Peter Hong)
2019-06-06 2:54 ` [PATCH V1 6/6] USB: serial: f81232: Add gpiolib to GPIO device Ji-Ze Hong (Peter Hong)
2019-08-28 15:37 ` Johan Hovold
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=1559789656-15847-3-git-send-email-hpeter+linux_kernel@gmail.com \
--to=hpeter@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
/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).