From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, Alan Cox <alan@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Peter Huewe <PeterHuewe@gmx.de>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
peter_hong@fintek.com.tw
Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Subject: [PATCH 0/5] serial/8250_fintek Support any configuration.
Date: Mon, 15 Jun 2015 16:18:41 +0200 [thread overview]
Message-ID: <1434377926-31958-1-git-send-email-ricardo.ribalda@gmail.com> (raw)
The original driver only supported the default configuration of the chip.
This patchset add supports for all the possible configurations:
-Different io address
-Multiple chips
-Different chip_ids
Reported-by: Peter Hong <peter_hong@fintek.com.tw>
Ricardo Ribalda Delgado (5):
serial/8250_fintek: Use private data structure
serial/8250_fintek: Support for multiple base_ports
serial/8250_fintek: Support for chip_ip 0x0501
serial/8250_fintek: Support keys different than default
serial/8250_fintek: Support for any io address.
drivers/tty/serial/8250/8250_fintek.c | 170 +++++++++++++++++++++-------------
1 file changed, 106 insertions(+), 64 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-15 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 14:18 Ricardo Ribalda Delgado [this message]
2015-06-15 14:18 ` [PATCH 1/5] serial/8250_fintek: Use private data structure Ricardo Ribalda Delgado
2015-06-15 14:18 ` [PATCH 2/5] serial/8250_fintek: Support for multiple base_ports Ricardo Ribalda Delgado
2015-06-15 14:18 ` [PATCH 3/5] serial/8250_fintek: Support for chip_ip 0x0501 Ricardo Ribalda Delgado
2015-06-15 14:18 ` [PATCH 4/5] serial/8250_fintek: Support keys different than default Ricardo Ribalda Delgado
2015-06-15 14:18 ` [PATCH 5/5] serial/8250_fintek: Support for any io address Ricardo Ribalda Delgado
2015-06-15 14:25 ` Alan Cox
2015-06-15 15:22 ` Ricardo Ribalda Delgado
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=1434377926-31958-1-git-send-email-ricardo.ribalda@gmail.com \
--to=ricardo.ribalda@gmail.com \
--cc=PeterHuewe@gmx.de \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=rafael.j.wysocki@intel.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).