linux.kernel - 26 new messages in 12 topics - digest

linux.kernel
http://groups.google.com/group/linux.kernel?hl=en

linux.kernel@googlegroups.com

Today's topics:

* Last minute ACPI fix for v3.13 - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/738628a78fd4d949?hl=en
* iMX gpio: Allow reading back of pin status if configured as gpio output - 1
messages, 1 author
http://groups.google.com/group/linux.kernel/t/f34a9e40faa9372a?hl=en
* x86, CPU, AMD: Add workaround for family 16h, erratum 793 - 5 messages, 3
authors
http://groups.google.com/group/linux.kernel/t/0e4150592fc82fa1?hl=en
* use ether_addr_equal_64bits - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/c126115ff68bc79d?hl=en
* More GPIO madness on iMX6 - and the crappy ARM port of Linux - 1 messages, 1
author
http://groups.google.com/group/linux.kernel/t/3756c905d46867b0?hl=en
* Add mm flag to control THP - 3 messages, 1 author
http://groups.google.com/group/linux.kernel/t/eff632e7496a6e85?hl=en
* net/dt: Add support for overriding phy configuration from device tree - 1
messages, 1 author
http://groups.google.com/group/linux.kernel/t/136c5a0335789c2c?hl=en
* mmc: sdhci: fix possible scheduling while atomic - 5 messages, 4 authors
http://groups.google.com/group/linux.kernel/t/5220ab2fee9bc8b4?hl=en
* i2c: New bus driver for the QUP I2C controller - 3 messages, 1 author
http://groups.google.com/group/linux.kernel/t/2c6bb71246961625?hl=en
* MAINTAINERS tree branches [xen tip as an example] - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/e080ae587afdec2e?hl=en
* net: rfkill: gpio: add device tree support - 1 messages, 1 author
http://groups.google.com/group/linux.kernel/t/502551497c79a009?hl=en
* pinctrl: capri: add dependency on OF - 3 messages, 2 authors
http://groups.google.com/group/linux.kernel/t/bcdbebbdc79aee31?hl=en

==============================================================================
TOPIC: Last minute ACPI fix for v3.13
http://groups.google.com/group/linux.kernel/t/738628a78fd4d949?hl=en
==============================================================================

== 1 of 1 ==
Date: Fri, Jan 17 2014 2:30 pm
From: "Rafael J. Wysocki"


Hi Linus,

Please pull from the git repository at

git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git acpi-3.13-fixup

to receive a last-minute ACPI fix for 3.13 as commit
b40f93bb008ed5d83aa608b21c8c65c5111512e1

Revert "ACPI: Add BayTrail SoC GPIO and LPSS ACPI IDs"

on top of commit 7e22e91102c6b9df7c4ae2168910e19d2bb14cd6

Linux 3.13-rc8

This reverts a commit that causes the Alan Cox' ASUS T100TA to "crash and
burn" during boot if the Baytrail pinctrl driver is compiled in.

Thanks!


---------------

Rafael J. Wysocki (1):
Revert "ACPI: Add BayTrail SoC GPIO and LPSS ACPI IDs"

---------------

drivers/acpi/acpi_lpss.c | 1 -
drivers/pinctrl/pinctrl-baytrail.c | 1 -
2 files changed, 2 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/





==============================================================================
TOPIC: iMX gpio: Allow reading back of pin status if configured as gpio output
http://groups.google.com/group/linux.kernel/t/f34a9e40faa9372a?hl=en
==============================================================================

== 1 of 1 ==
Date: Fri, Jan 17 2014 2:30 pm
From: Waibel Georg


> On Fri, Jan 17, 2014 at 14:11 +0000, Waibel Georg wrote:
> >
> > From cb384950a1153e856ec03109a5156e660a89bf6d Mon Sep 17 00:00:00 2001
> > From: Georg Waibel <georg.waibel@sensor-technik.de>
> > Date: Fri, 17 Jan 2014 14:51:38 +0100
> > Subject: [PATCH 1/1] iMX gpio: Allow reading back of pin status if configured
> > as gpio output
> >
> > Register PSR was used to read the pin status in the mxc_gpio driver. This
> > register reflects the pin status if a pin is configured as gpio input.
> > If a pin is configured as an gpio output register PSR is not updated and
> > returns 0 instead of the actual pin status. Thus attempting to read back the
> > status of an gpio output pin via PSR returns a wrong value.
> >
> > Reading register DR instead of PSR fixes this issue:
> > - If pin is gpio output: DR returns the value written to DR by software
> > - If pin is gpio input: DR returns the value of register PSR und thus the
> > pin status
>
> Got curious because of your specific wording. In the output
> case, does the DR value reflect what you drive to the pin, or
> what the pin's status is? Because this need not be identical in
> the open collector case (or other "weak" scenarios like bus
> keeper, and what else HW development came up with).
>
> If DR always reflects the pin's status, then the patch would be
> OK but the commit message would need an update. If DR does not
> appropriately reflect the pin's status, then the patch would be
> an improvement (would fix the totem-pole case), but still would
> be wrong or incomplete in the open-collector case.


Hi Gerhard,

actually I did not take the open-collector case into account.
I checked the iMX6q reference manual and came to this conclusion:

In the output case, reading register DR returns the value I have written
to DR, not the actual pad state. Thus may patch only works for the
push-pull (totem-pole) output case, not for open-drain.

However, there is a solution to read back the pin status regardless of
its input or output configuration. Its the SION (Software Input On Bit)
in the IOMUXC MUX control register. If SION is set, the pad status can be
read back through register PSR. Thats exactly what I intended to do.
Bit SION can be set in the device tree (IOMUXC: CONFIG filed in the
fsl,pins binding, bit 30).
I will verify this on my iMX6 hardware next week.

Seems there is no need for my patch at all.

Thanks for your hint.
Regards
Georg

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/





==============================================================================
TOPIC: x86, CPU, AMD: Add workaround for family 16h, erratum 793
http://groups.google.com/group/linux.kernel/t/0e4150592fc82fa1?hl=en
==============================================================================

== 1 of 5 ==
Date: Fri, Jan 17 2014 2:30 pm
From: Pavel Machek


On Tue 2014-01-14 17:27:23, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> This adds the workaround for erratum 793 as a precaution in case not
> every BIOS implements it. This addresses CVE-2013-6885.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> arch/x86/kernel/cpu/amd.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index 4a48e8bbd857..e4d6f8c91f51 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -507,6 +507,17 @@ static void early_init_amd(struct cpuinfo_x86 *c)
> set_cpu_cap(c, X86_FEATURE_EXTD_APICID);
> }
>