| Age | Commit message (Collapse) | Author |
|---|
|
1/1 [
Author: Alexander Stein
Email: alexander.stein@systec-electronic.com
Subject: drivers/tty/serial/pch_uart.c: add console support
Date: Thu, 1 Mar 2012 15:59:36 -0800
commit e30f867d402d6dcc2d03d8dd5da3863f7c83572a upstream.
Add console support to pch_uart. To enable append e.g.
console=ttyPCH0,115200 to your kernel command line.
This is not expected work on CM-iTC boards due to their having a different
clock.
Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/4 [
Author: Darren Hart
Email: dvhart@linux.intel.com
Subject: pch_uart: Use uartclk instead of base_baud
Date: Thu, 1 Mar 2012 15:59:37 -0800
The term "base baud" refers to the fastest baud rate the device can communicate
at. This is clock/16. pch_uart is using base_baud as the clock itself. Rename
the variables to be semantically correct.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tomoya MORINAGA <tomoya.rohm@gmail.com>
CC: Feng Tang <feng.tang@intel.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: Alan Cox <alan@linux.intel.com>
CC: linux-serial@vger.kernel.org
]
2/4 [
Author: Darren Hart
Email: dvhart@linux.intel.com
Subject: pch_uart: Add Fish River Island II uart clock quirks
Date: Thu, 1 Mar 2012 15:59:38 -0800
Add support for the Fish River Island II (FRI2) UART clock following the CM-iTC
quirk handling mechanism. Depending on the firmware installed on the device, the
FRI2 uses a 48MHz or a 64MHz UART clock. This is detected with DMI strings.
Add similar UART clock quirk handling to the pch_console_setup() function to
enable kernel messages on boards with non-standard UART clocks.
Per Alan's suggestion, abstract out UART clock selection into
pch_uart_get_uartclk() to avoid code duplication.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tomoya MORINAGA <tomoya.rohm@gmail.com>
CC: Feng Tang <feng.tang@intel.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: Alan Cox <alan@linux.intel.com>
CC: linux-serial@vger.kernel.org
]
3/4 [
Author: Darren Hart
Email: dvhart@linux.intel.com
Subject: pch_uart: Add user_uartclk parameter
Date: Thu, 1 Mar 2012 15:59:39 -0800
For cases where boards with non-default clocks are not yet added to the kernel
or when the clock varies across hardware revisions, it is useful to be
able to specify the UART clock on the kernel command line.
Add the user_uartclk parameter and prefer it, if set, to the default and
board specific UART clock settings. Specify user_uartclock on the command-line
with "pch_uart.user_uartclk=48000000".
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tomoya MORINAGA <tomoya.rohm@gmail.com>
CC: Feng Tang <feng.tang@intel.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: Alan Cox <alan@linux.intel.com>
CC: linux-serial@vger.kernel.org
]
4/4 [
Author: Darren Hart
Email: dvhart@linux.intel.com
Subject: pch_uart: Use existing default_baud in setup_console
Date: Thu, 1 Mar 2012 15:59:40 -0800
Rather than hardcode 9600, use the existing default_baud parameter (which
also defaults to 9600).
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tomoya MORINAGA <tomoya.rohm@gmail.com>
CC: Feng Tang <feng.tang@intel.com>
CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
CC: Alan Cox <alan@linux.intel.com>
CC: linux-serial@vger.kernel.org
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Khem Raj
Email: raj.khem@gmail.com
Subject: compiler.h: Undef before redefining __attribute_const__
Date: Thu, 5 Jan 2012 11:42:35 -0800
This is required to avoid warnings like
util/include/linux/compiler.h:8:0: error: "__attribute_const__" redefined [-Werror]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Paul Gortmaker
Email: paul.gortmaker@windriver.com
Subject: mount_root: clarify error messages for when no rootfs found
Date: Thu, 26 Nov 2009 07:32:09 -0800
To an end user who doesn't really know linux that well, a
message like:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
may just look like cryptic computer speak indicating some
deep and complex problem, instead of the reality that they
have a simple local configuration problem. Ideally it would
be nice to not use the misleading "panic" at all, but since
various panic notifiers are historically expecting to be
called when there is no valid rootfs, we can't change that.
So instead, this tries to make it 100% clear to folks of
any background that it is an end user configuration issue.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Alexander Stein
Email: alexander.stein@systec-electronic.com
Subject: drivers/misc/pch_phub.c: don't oops if dmi_get_system_info returns NULL
Date: Mon, 25 Jul 2011 17:11:54 -0700
If dmi_get_system_info() returns NULL, pch_phub_probe() will dereferencea
a zero pointer.
This oops was observed on an Atom based board which has no BIOS, but a
bootloder which doesn't privde DMI data.
Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
Cc: Greg KH <gregkh@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Yoichi Yuasa
Email: yuasa@linux-mips.org
Subject: MIPS: i8259: Use struct syscore_ops instead of sysdevs
Date: Fri, 20 May 2011 13:41:41 +0900
MIPS: i8259: Use struct syscore_ops instead of sysdevs
Signed-off-by: Yoichi Yuasa <yuasa@linux-mips.org>
Cc: linux-mips <linux-mips@linux-mips.org>
Patchwork: https://patchwork.linux-mips.org/patch/2394/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
1/1 [
Author: Bruce Ashfield
Email: bruce.ashfield@windriver.com
Subject: i8259: remove obselete shutdown and resume hooks
Date: Thu, 30 Jun 2011 10:16:31 -0400
The mainline sysdev structs have removed support for shutdown
and resume. We don't really need them here, so rather than restoring
the support, we'll drop the hooks.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Roughly corresponds to:
commit db575247e16e50ce5160e18907e253c6a43b6feb
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Mon Apr 4 00:27:55 2011 -0400
yocto: 2.6.39 baseline
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
...in the full history repo, but with some extraneous files that were
deleted post db575247 deleted right here and now at the baseline
instead.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
Bruce Ashfield
Paul Gortmaker