From: Andrew Lunn <andrew@lunn.ch> To: "Andreas Färber" <afaerber@suse.de> Cc: Rob Herring <robh@kernel.org>, "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>, linux-usb@vger.kernel.org, Linux-MIPS <linux-mips@linux-mips.org>, Xue Liu <liuxuenetmail@gmail.com>, Ben Whitten <ben.whitten@lairdtech.com>, devicetree@vger.kernel.org, "netdev@vger.kernel.org" <netdev@vger.kernel.org>, Oliver Neukum <oneukum@suse.com>, Alexander Graf <agraf@suse.de>, "LoRa_Community_Support@semtech.com" <LoRa_Community_Support@semtech.com>, Jian-Hong Pan <starnight@g.ncu.edu.tw>, Stefan Rehm <rehm@miromico.ch>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: Re: serdev: How to attach serdev devices to USB based tty devices? Date: Wed, 15 Aug 2018 02:46:36 +0200 [thread overview] Message-ID: <20180815004636.GB11610@lunn.ch> (raw) In-Reply-To: <3639955d-5990-1c82-7158-ac07b33c41f2@suse.de> Hi Andreas This not my area of expertise. But i wanted to point out that there exists a mechanism to make the FDTI driver release a port so that it can be used from user space, e.g. for JTAG. It might be possible to extend this mechanism to make the FTDI driver perform the registration to serdev. It is however not a generic solution. Andrew
WARNING: multiple messages have this Message-ID (diff)
From: andrew@lunn.ch (Andrew Lunn) To: linux-arm-kernel@lists.infradead.org Subject: serdev: How to attach serdev devices to USB based tty devices? Date: Wed, 15 Aug 2018 02:46:36 +0200 [thread overview] Message-ID: <20180815004636.GB11610@lunn.ch> (raw) In-Reply-To: <3639955d-5990-1c82-7158-ac07b33c41f2@suse.de> Hi Andreas This not my area of expertise. But i wanted to point out that there exists a mechanism to make the FDTI driver release a port so that it can be used from user space, e.g. for JTAG. It might be possible to extend this mechanism to make the FTDI driver perform the registration to serdev. It is however not a generic solution. Andrew
next prev parent reply other threads:[~2018-08-15 3:36 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-14 2:28 serdev: How to attach serdev devices to USB based tty devices? Andreas Färber 2018-08-14 2:28 ` Andreas Färber 2018-08-14 2:28 ` Andreas Färber 2018-08-14 7:23 ` Oliver Neukum 2018-08-14 7:23 ` Oliver Neukum 2018-08-14 7:23 ` Oliver Neukum 2018-08-15 0:46 ` Andrew Lunn [this message] 2018-08-15 0:46 ` Andrew Lunn 2018-08-15 0:46 ` Andrew Lunn 2018-08-15 18:21 ` Sebastian Reichel 2018-08-15 18:21 ` Sebastian Reichel 2018-08-15 18:21 ` Sebastian Reichel 2018-08-21 14:29 ` Johan Hovold 2018-08-21 14:29 ` Johan Hovold 2018-08-15 19:53 ` Rob Herring 2018-08-15 19:53 ` Rob Herring 2018-08-15 19:53 ` Rob Herring 2018-08-17 5:55 ` Tony Lee 2018-08-29 6:57 ` Tony Lee 2018-08-21 16:32 ` Frank Kunz 2018-08-21 16:32 ` Frank Kunz 2018-08-21 16:32 ` Frank Kunz 2018-08-21 16:32 ` Frank Kunz 2018-08-21 18:01 ` Rob Herring 2018-08-21 18:01 ` Rob Herring
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=20180815004636.GB11610@lunn.ch \ --to=andrew@lunn.ch \ --cc=LoRa_Community_Support@semtech.com \ --cc=afaerber@suse.de \ --cc=agraf@suse.de \ --cc=ben.whitten@lairdtech.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-mips@linux-mips.org \ --cc=linux-serial@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=liuxuenetmail@gmail.com \ --cc=netdev@vger.kernel.org \ --cc=oneukum@suse.com \ --cc=rehm@miromico.ch \ --cc=robh@kernel.org \ --cc=starnight@g.ncu.edu.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: 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.