I forgot to rename pci_mmcfg_for_each_region() content. Will send fixed
patch.
Tomasz
On 10.03.2015 12:35, Tomasz Nowicki wrote:
This commit is consequence of making x86 MMCONFIG code available for all
architectures. Current code has old name fashion so for the sake of
making it more
On Mon, Mar 09, 2015 at 12:44:47PM -0700, Doug Anderson wrote:
> If the i2c-hid device was runtime suspended and then the system
> suspended itself we'd end up disabling interrupts twice (in
> i2c_hid_runtime_suspend and i2c_hid_suspend) and not reenabling them
> until later when the i2c-hid
On Tue, Mar 10, 2015 at 03:52:41PM +0530, Archit Taneja wrote:
> On 03/10/2015 03:35 PM, Daniel Vetter wrote:
> >On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
> >>On 03/10/2015 03:17 PM, Daniel Vetter wrote:
> >>>On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
>
On Tue, Mar 10, 2015 at 12:22:06AM +0100, Heiko Stuebner wrote:
> When {devm_}regulator_get returns -EPROBE_DEFER the driver in question will
> try probing again at a later time. So don't spam the log with failure messages
> as this is an expected result of probe ordering.
> -
On Tue, Mar 10, 2015 at 07:21:59PM +0800, fan.chen wrote:
> On Mon, 2015-03-09 at 11:38 +0100, Sascha Hauer wrote:
> > > > +
> > > > + switch (ck_mhz) {
> > > > + case 18:
> > > > + if (pwrap_is_mt8135(wrp))
> > > > + pwrap_writel(wrp, 0xc,
On Tue, Mar 10, 2015 at 11:27:23AM +, Peter Zijlstra wrote:
> On Mon, Mar 09, 2015 at 12:46:30PM +, Suzuki K. Poulose wrote:
> > From: "Suzuki K. Poulose"
> >
> > Don't allow grouping hardware events from different PMUs
> > (eg. CCI + CPU).
>
> Uhm, how does this work? If we have
From: Boris BREZILLON
Add support for the AXP22x PMIC devices to the existing AXP20x driver.
This includes the AXP221 and AXP223, which are identical except for
the external data bus. Only AXP221 is added for now. AXP223 will be
added after it's Reduced Serial Bus (RSB) interface is supported.
From: Boris BREZILLON
Add AXP22X regulator definitions and variant id associations.
This introduces a new "switch" type output for one of the regulators.
It is a switchable secondary output of one regulator, with the same
voltage level as the primary output.
Signed-off-by: Boris BREZILLON
This patch adds the AXP221 regulators. Only the ones directly used
on the board are added.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun6i-a31-hummingbird.dts | 56 -
1 file changed, 55 insertions(+), 1 deletion(-)
diff --git
On Mon, Mar 09, 2015 at 08:28:45PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Mar 09, 2015 at 08:11:19PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Mar 09, 2015 at 06:51:21PM -0300, Arnaldo Carvalho de Melo escreveu:
SNIP
> [root@zoo ~]# find
From: Boris BREZILLON
Rework the AXP20X_ macros and probe function to support the several chip
families, so that each family can define it's own set of regulators.
Signed-off-by: Boris BREZILLON
[w...@csie.org: Support different DC-DC work frequency ranges]
Signed-off-by: Chen-Yu Tsai
---
I
On Mon 2015-03-09 09:40:55, Josh Poimboeuf wrote:
> On Mon, Mar 09, 2015 at 02:25:28PM +0100, Petr Mladek wrote:
> > There is a notifier that handles live patches for coming and going modules.
> > It takes klp_mutex lock to avoid races with coming and going patches but
> > it does not keep the
From: Boris BREZILLON
The p2wi controller has only one possible pinmux setting. Use it by
default in the dtsi, instead of having to set it in each board's dts.
Signed-off-by: Boris BREZILLON
[w...@csie.org: reformat commit title; rename p2wi pins and use as default]
Signed-off-by: Chen-Yu Tsai
The Hummingbird A31 has an AXP221 PMIC hooked up to the
P2WI controller.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun6i-a31-hummingbird.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun6i-a31-hummingbird.dts
On 04/03/15 09:06, Liu Ying wrote:
> The LCDIF engines embedded in i.MX6sl and i.MX6sx SoCs need the axi clock
> as the engine's system clock. The clock should be enabled when accessing
> LCDIF registers, otherwise the kernel would hang up. We should also keep
> the clock being enabled when the
Now that the axp20x-regulators driver supports different variants of the
AXP family, we can enable regulator support for AXP22X without the risk
of incorrectly configuring regulators.
Signed-off-by: Chen-Yu Tsai
---
drivers/mfd/axp20x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
mmc1 is used to connect to the WiFi chip on the Hummingbird A31.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun6i-a31.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi
index 92abea20b946..39d87a901b46
The Hummingbird A31 has an AMPAK AP6210 WiFi+Bluetooth module. The
WiFi part is a BCM43362 IC connected to MMC1 in the A31 SoC via SDIO.
The IC also takes a power enable signal via GPIO. This is supported
with the new power sequencing bindings.
The WiFi module supports out-of-band interrupt
The Hummingbird A31 has an AXP221 PMIC hooked up to the P2WI controller.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun6i-a31-hummingbird.dts | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun6i-a31-hummingbird.dts
b/arch/arm/boot/dts/sun6i-a31-hummingbird.dts
On 10/03/15 11:27, Peter Zijlstra wrote:
On Mon, Mar 09, 2015 at 12:46:30PM +, Suzuki K. Poulose wrote:
From: "Suzuki K. Poulose"
Don't allow grouping hardware events from different PMUs
(eg. CCI + CPU).
Uhm, how does this work? If we have multiple hardware PMUs we'll stop
scheduling
The Hummingbird A31 has an AMPAK AP6210 WiFi+Bluetooth module. The
WiFi part is a BCM43362 IC connected to MMC1 in the A31 SoC via SDIO.
The IC also takes a power enable signal via GPIO.
The WiFi module supports out-of-band interrupt signaling via GPIO,
but this is not supported in this patch.
Add AXP221 to the list of supported devices.
Also replace any mention of AXP20x in the document with a
generic "PMIC".
Signed-off-by: Chen-Yu Tsai
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
Add the list of regulators for AXP22x to the DT bindings.
This includes the names and supply names.
Signed-off-by: Chen-Yu Tsai
---
Documentation/devicetree/bindings/mfd/axp20x.txt | 27
1 file changed, 27 insertions(+)
diff --git
Hi everyone,
This is v5 of the AXP221 series. I've taken over the work from Boris.
This version is based on v4.0-rc1, plus "mfd: AXP20x: Add bindings
documentation" which was posted a few weeks ago. I've worked on this
series for some time, so the changelog might not be completely accurate.
The
Currently probe deferral prints a message every time a device requests
deferral at info severity (which is displayed by default). This can have
an impact on system boot times with serial consoles and is generally quite
noisy.
Since subsystems and drivers should already be logging the specific
Hi Boris,
On 10/03/15 11:37, Borislav Petkov wrote:
Hi,
I just triggered this is on rc3 + tip/master which has your patch. This
is an Intel SNB. Ideas, already fixed?
No, not seen this before. I will test tip/master on my Intel i7 box
again and get back to you.
Regards,
Sudeep
--
To
Hi!
> It seems that pcmcia was unhappy even before, but eject definitely
> oopsed it.
Aha, I was confused; the oops is with 3.18, not with 4.0. For 4.0,
pcmcia does not work at all:
[ 617.062718] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
[ 622.840108] pcmcia_socket
Add trace events to driver to allow monitoring and profilig
of activities such as PM suspend/resume, hibernate enter/exit,
clock gating and clock scaling up/down.
In addition, add UFS host controller register dumps to provide
detailed information in case of errors to assist in analysis
of issues.
From: Lee Susman
Adding debugfs capability for ufshcd.
debugfs attributes introduced in this patch:
- View driver/controller runtime data
- Command tag statistics for performance analisis
- Dump device descriptor info
- Track recoverable errors statistics during runtime
- Change UFS power
From: Dolev Raviv
This patch exposes the ioctl interface for UFS driver via SCSI device
ioctl interface. As of now UFS driver would provide the ioctl for query
interface to connected UFS device.
Signed-off-by: Dolev Raviv
Signed-off-by: Noa Rubens
Signed-off-by: Raviv Shvili
Signed-off-by:
Changes from V4:
Dropped error injection change titled:
scsi: ufs: inject errors to verify error handling
Dolev Raviv (1):
scsi: ufs: add ioctl interface for query request
Gilad Broner (1):
scsi: ufs: add trace events and dump prints for debug
Lee Susman (1):
scsi: ufs: add debugfs for
On 2015.03.07 at 09:35 +, Filipe David Manana wrote:
> On Tue, Mar 3, 2015 at 2:13 PM, Markus Trippelsdorf
> wrote:
> > On 2015.03.02 at 14:29 +0100, Markus Trippelsdorf wrote:
> >> On 2015.03.02 at 12:07 +, Filipe David Manana wrote:
> >> > >> [83159.038708] [ cut here
On Mon, Dec 29, Christoph Hellwig wrote:
> +++ b/drivers/scsi/storvsc_drv.c
> static struct scsi_host_template scsi_driver = {
> .module = THIS_MODULE,
> .name = "storvsc_host_t",
> + .cmd_size = sizeof(struct storvsc_cmd_request),
>
On Tue, Mar 10, 2015 at 09:57:06AM +, Lorenzo Stoakes wrote:
> This patch assigns the more appropriate void* type to the mmio750 variable
> eliminating an unnecessary volatile qualifier in the process. Additionally it
> updates parameter types as necessary where those parameters interact with
At Mon, 9 Mar 2015 22:13:03 +0100,
Yannick Guerrini wrote:
>
> Change 'propper' to 'proper'
> Change 'paramters' to 'parameters'
> Change 'SYT_INTEVAL' to 'SYT_INTERVAL'
> Change 'aligh'/'alighed' to 'align'/'aligned'
>
> Signed-off-by: Yannick Guerrini
Applied, thanks.
Takashi
> ---
>
Hi,
I just triggered this is on rc3 + tip/master which has your patch. This
is an Intel SNB. Ideas, already fixed?
Thanks.
[ cut here ]
WARNING: CPU: 3 PID: 1 at fs/sysfs/group.c:102
internal_create_group+0x151/0x280()
sysfs: (bin_)attrs not set by subsystem for group:
- fix typo
- improve explanation
- add reference to the related document
Signed-off-by: Tomasz Nowicki
---
arch/x86/include/asm/pci_x86.h | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/pci_x86.h b/arch/x86/include/asm/pci_x86.h
index
ECAM standard and MCFG table are architecture independent and it makes
sense to share common code across all architectures. Both are going to
corresponding files - ecam.c and mcfg.c
While we are here, rename pci_parse_mcfg to acpi_parse_mcfg.
We already have acpi_parse_mcfg prototype which is
mmconfig_64.c version is going to be default implementation for arch
agnostic low-level direct PCI config space accessors for ECAM dirver.
However, now it initialize raw_pci_ext_ops pointer which is x86 specific
code only. Moreover, mmconfig_32.c is doing the same thing at the same time.
Move it
On 2015年03月10日 19:19, Leif Lindholm wrote:
On Tue, Mar 10, 2015 at 04:01:16PM +0800, Hanjun Guo wrote:
index 000..f052e7a
--- /dev/null
+++ b/arch/arm64/kernel/acpi.c
@@ -0,0 +1,101 @@
+/*
+ * ARM64 Specific Low-Level ACPI Boot Support
+ *
+ * Copyright (C) 2013-2014, Linaro Ltd.
+ *
Those two functions are required by ACPI subsystem to make PCI config
space accessible. Generic code assume to do nothing for early init call but
late init call does as follow:
- parse MCFG table and add regions to ECAM resource list
- map regions
- add regions to iomem_resource
Signed-off-by:
This commit is consequence of making x86 MMCONFIG code available for all
architectures. Current code has old name fashion so for the sake of
making it more understandable and express where it comes from,
we are changing functions/variables/macros etc. name *mmconfig* -> *ecam*
Signed-off-by:
This patch is the first step for MMCONFIG refactoring process.
Code that uses pci_mmcfg_lock will be moved to common file and become
accessible for all architectures. pci_mmconfig_insert() cannot be moved
so easily since it is mixing generic mmconfig code with x86 specific logic
inside of mutual
Architectures which want to take advantage of ECAM generic goodness
should select CONFIG_PCI_ECAM_GENERIC. Otherwise, like x86 32bits, machines
are obligated to provide own low-level ECAM calls.
Signed-off-by: Tomasz Nowicki
---
arch/x86/Kconfig | 1 +
arch/x86/pci/Makefile |
MCFG can be used perfectly for all architectures which support ACPI.
ACPI mandates MCFG to describe PCI config space ranges which means
we should use MMCONFIG accessors by default.
Signed-off-by: Tomasz Nowicki
---
drivers/acpi/mcfg.c | 20
1 file changed, 20 insertions(+)
MCFG ACPI table and PCI ECAM standard have no arch dependencies so it can be
used across all architectures. Currently MMCONFIG related code resides in
arch/x86 directories. This patch set is going to isolate non-architecture
specific code and make it accessible for all architectures.
v2 -> v3
>From now on, readb()/writeb()/etc. generic calls are used as default
approach. Special MMIO accessors are registered for AMD Fam10h CPUs only.
Signed-off-by: Tomasz Nowicki
---
arch/x86/include/asm/pci_x86.h | 8 +++
arch/x86/pci/mmconfig-shared.c | 114
Hi Olof,
On 2015年03月06日 02:49, Olof Johansson wrote:
Hi,
On Wed, Feb 25, 2015 at 04:39:53PM +0800, Hanjun Guo wrote:
MADT contains the information for MPIDR which is essential for
SMP initialization, parse the GIC cpu interface structures to
get the MPIDR value and map it to
On Mon 2015-03-09 09:03:18, Mark Seaborn wrote:
> On 6 January 2015 at 15:20, Pavel Machek wrote:
> > On Mon 2015-01-05 19:23:29, One Thousand Gnomes wrote:
> > Actually, I could not get my test code to run; and as code from
> >
> > https://github.com/mseaborn/rowhammer-test
> >
> > reproduces
On 2015-03-10 04:10, Aleksa Sarai wrote:
Hi Austin,
Does pids limit make sense in the root cgroup?
I would say it kind of does, although I would just expect it to track
/proc/sys/kernel/pid_max (either as a read-only value, or as an alternative
way to set it).
Personally, that seems
On 14/02/15 16:22, Thomas Niederprüm wrote:
> Am Thu, 12 Feb 2015 16:11:21 +0100
> schrieb Maxime Ripard :
>
>> On Sat, Feb 07, 2015 at 04:35:41PM +0100, Thomas Niederprüm wrote:
>>> Am Sat, 7 Feb 2015 12:18:21 +0100
>>> schrieb Maxime Ripard :
>>>
Hi,
On Fri, Feb 06, 2015 at
On Mon, Mar 09, 2015 at 12:46:30PM +, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose"
>
> Don't allow grouping hardware events from different PMUs
> (eg. CCI + CPU).
Uhm, how does this work? If we have multiple hardware PMUs we'll stop
scheduling events after the first failed event
On Mon, Mar 09, 2015 at 04:48:43PM -0400, Eric B Munson wrote:
> Currently, pages which are marked as unevictable are protected from
> compaction, but not from other types of migration. The mlock
> desctription does not promise that all page faults will be avoided, only
> major ones so this
On Tue, Mar 10, 2015 at 04:01:16PM +0800, Hanjun Guo wrote:
> >>index 000..f052e7a
> >>--- /dev/null
> >>+++ b/arch/arm64/kernel/acpi.c
> >>@@ -0,0 +1,101 @@
> >>+/*
> >>+ * ARM64 Specific Low-Level ACPI Boot Support
> >>+ *
> >>+ * Copyright (C) 2013-2014, Linaro Ltd.
> >>+ * Author: Al
On Tue 2015-03-10 12:53:21, Rusty Russell wrote:
> Petr Mladek writes:
> > On Sat 2015-03-07 11:34:36, Rusty Russell wrote:
> >> I don't think you should handle going modules at all. Rarely happens,
> >> and it should happen fast.
> >
> > I would like to handle it correctly. It would be pity to
On Fri, Mar 06, 2015 at 11:47:48PM +0200, grygorii.stras...@linaro.org wrote:
> Hi Russell,
>
> On 03/05/2015 10:17 PM, Russell King - ARM Linux wrote:
> > On Thu, Mar 05, 2015 at 08:55:07PM +0200, grygorii.stras...@linaro.org
> > wrote:
> >> The dma_coerce_mask_and_coherent() will fail in case
On Tue, Mar 10, 2015 at 10:10:56AM +0200, Ivan T. Ivanov wrote:
> On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
> > > About the API usage, point taken. GPIO requesting part is more important
> > > in this case. pinctrl core did not request pins and wrong DT configuration
> > > could lead
On Wed, Mar 4, 2015 at 1:00 AM, Nishanth Menon wrote:
> SoC family such as DRA7 family of processors have, in addition
> to the regular muxing of pins (as done by pinctrl-single), an
> additional hardware module called IODelay which is also expected to be
> configured. This "IODelay" module has
2015-03-09 20:28-0300, Marcelo Tosatti:
> On Fri, Feb 27, 2015 at 06:19:18PM -0600, Joel Schopp wrote:
> > From: David Kaplan
> > No need to re-decode WBINVD since we know what it is from the intercept.
> >
> > Signed-off-by: David Kaplan
> > [extracted from larger unlrelated patch, forward
On Sat, Mar 07, 2015 at 06:13:47PM +0100, Oleg Nesterov wrote:
> I think the patch is fine, but this reminds me...
>
> On 03/07, tip-bot for Jason Low wrote:
> >
> > bool rwsem_spin_on_owner(struct rw_semaphore *sem, struct task_struct
> > *owner)
> > {
> > long count;
> >
> >
On 03/10/2015 12:29 AM, Ingo Molnar wrote:
>
> * Sasha Levin wrote:
>
>> Hi all,
>>
>> While fuzzing with trinity inside the latest -next kernel using trinity I've
>> stumbled on:
>>
>> [ 936.784266] divide error: [#1] PREEMPT SMP KASAN
>> [ 936.793957] RIP: find_busiest_group
Hi Archit,
thanks for the cleanup!
Am Dienstag, den 10.03.2015, 15:11 +0530 schrieb Archit Taneja:
> DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation
> for
> the imx kms driver.
>
> Remove this local config option and use the top level DRM_FBDEV_EMULATION
> config
Ping.
On Mon, 2015-02-23 at 11:59 +0200, Ivan T. Ivanov wrote:
> Hi Gilad,
>
> On Thu, 2015-02-19 at 15:54 -0700, Gilad Avidov wrote:
> > Qualcomm PMIC Arbiter version-2 changes from version-1 are:
> >
> > - Some different register offsets.
> > - New channel register space, one per PMIC
On 09/02/15 10:52, Maxime Ripard wrote:
> On Sat, Feb 07, 2015 at 05:42:44PM +0100, Thomas Niederprüm wrote:
+static struct device_attribute device_attrs[] = {
+ __ATTR(contrast, S_IRUGO|S_IWUSR, show_contrast,
store_contrast),
+ __ATTR(dim, S_IRUGO|S_IWUSR, show_dim,
On Thu, Mar 05 2015, Rasmus Villemoes wrote:
> On Thu, Mar 05 2015, Tejun Heo wrote:
>
>> I'd like to see how this actually affects larger operations - sth
>> along the line of top consumes D% less CPU cycles w/ N processes - if
>> for nothing else, just to get the sense of scale,
>
> That
On Sat, Mar 07, 2015 at 04:24:02PM -0800, David Rientjes wrote:
> mempool_alloc() does not support __GFP_ZERO since elements may come from
> memory that has already been released by mempool_free().
>
> Remove __GFP_ZERO from mempool_alloc() in drbd_req_new() and properly
> initialize it to 0.
We
On 14/02/15 17:54, Maxime Ripard wrote:
> On Sat, Feb 07, 2015 at 05:05:03PM +0100, Thomas Niederprüm wrote:
>> Am Sat, 7 Feb 2015 12:20:43 +0100
>> schrieb Maxime Ripard :
>>
>>> On Fri, Feb 06, 2015 at 11:28:11PM +0100, nied...@physik.uni-kl.de
>>> wrote:
From: Thomas Niederprüm
stub_iopl is no longer needed: pt_regs->flags needs no fixing up
after previous change. Removing it.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Steven Rostedt
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Oleg Nesterov
CC: Frederic Weisbecker
CC: Alexei
All manipulations of PER_CPU(old_rsp) in C code are removed:
it is not used on SYSRET return, storing anything there is pointless.
This also allows to get rid of thread_struct::usersp,
which was needed only to set PER_CPU(old_rsp) for
correct return from fork/clone.
Tweak a few comments (we no
On Tue, Mar 10, 2015 at 01:44:41PM +1100, Stephen Rothwell wrote:
> grep is your friend ...
Indeed :(
> This patch should be applied to your tree as it is based off v4.0-rc1
> already.
Applied, thanks.
signature.asc
Description: Digital signature
On Wed, Mar 4, 2015 at 1:00 AM, Nishanth Menon wrote:
> +Configuration definition follows similar model as the pinctrl-single:
> +The groups of pin configuration are defined under "pinctrl-single,pins"
> +
> +_iodelay_core {
> + mmc2_iodelay_3v3_conf: mmc2_iodelay_3v3_conf {
> +
On 27 February 2015 at 17:21, Viresh Kumar wrote:
> Hi Thomas/Ingo,
>
> This is in response to the suggestions Ingo gave [1] on the shortcomings of
> clockevents core's state machine.
>
> This first separates out the RESUME functionality from other states as its a
> special case. Then it defines
On 07/03/15 18:08, Javier Martinez Canillas wrote:
> The doc refers to Documentation/devicetree/bindings/video/video-ports.txt
> which does not exist. The documentation seems to be outdated and wants to
> refer to Documentation/devicetree/bindings/graph.txt instead.
>
> Suggested-by: Tomi
> Check for null before being dereferenced to avoid a invalid null
> dereference.
>
> Found using Coccinelle.
>
> Signed-off-by: Tapasweni Pathak
> Acked-by: Julia Lawall
> ---
> drivers/scsi/ufs/ufshcd.c |7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git
On Tue, Mar 10, 2015 at 11:33:24AM +0200, Peter Ujfalusi wrote:
> Do you know any other device which have similar addressing? Do you have advice
> on how to handle this? Should I open code the book switching in the driver,
> which means that I should not use the cache at all in regmap.
I've
On 03/10/2015 03:35 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB
On Mon, Mar 9, 2015 at 9:45 PM, Ray Jui wrote:
> This enables GPIO based phone hook detection for Broadcom BCM911360
> phone factor board (bcm911360_entphn)
>
> Signed-off-by: Ray Jui
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, Mar 9, 2015 at 9:45 PM, Ray Jui wrote:
> This enables all 3 GPIO controllers including the ASIU GPIO, the
> chipcommonG GPIO, and the ALWAYS-ON GPIO, for Broadcom Cygnus SoC
>
> Signed-off-by: Ray Jui
> Reviewed-by: Scott Branden
> Tested-by: Dmitry Torokhov
Acked-by: Linus Walleij
>> +static bool inject_cmd_hang_tr(struct ufs_hba *hba)
>> +{
>> + int tag;
>> +
>> + tag = find_first_bit(>outstanding_reqs, hba->nutrs);
>> + if (tag == hba->nutrs)
>> + return 0;
>> +
>> + __clear_bit(tag, >outstanding_reqs);
>> + hba->lrb[tag].cmd =
On Mon, Mar 9, 2015 at 9:45 PM, Ray Jui wrote:
> This adds the initial support of the Broadcom Cygnus GPIO/PINCONF driver
> that supports all 3 GPIO controllers on Cygnus including the ASIU GPIO
> controller, the chipCommonG GPIO controller, and the always-on GPIO
> controller. Basic PINCONF
On Mon, Mar 9, 2015 at 9:44 PM, Ray Jui wrote:
> Document the GPIO/PINCONF device tree binding for Broadcom Cygnus SoC
>
> Signed-off-by: Ray Jui
> Reviewed-by: Scott Branden
Patch applied!
> +- compatible:
> +Must be "brcm,cygnus-ccm-gpio", "brcm,cygnus-asiu-gpio", or
> +
On Mon, Mar 9, 2015 at 9:44 PM, Ray Jui wrote:
> This enables the IOMUX support for Broadcom Cygnus SoC
>
> Signed-off-by: Ray Jui
> Tested-by: Dmitry Torokhov
Acked-by: Linus Walleij
Pls take this through some BRCM ARM SoC tree.
Linus
--
To unsubscribe from this list: send the line
On 03/10/2015 03:31 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:30PM +0530, Archit Taneja wrote:
DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
the i915 kms driver.
Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
config
On 06.03.2015 19:53, Bjorn Helgaas wrote:
On Fri, Feb 27, 2015 at 04:00:35PM +0100, Tomasz Nowicki wrote:
MCFG ACPI table and PCI ECAM standard have no arch dependencies so it can be
used across all architectures. Currently MMCONFIG related code resides in
arch/x86 directories. This patch set
Commit-ID: 1d23c4518b1f3a03c278f2149245c178d2a6
Gitweb: http://git.kernel.org/tip/1d23c4518b1f3a03c278f2149245c178d2a6
Author: Oleg Nesterov
AuthorDate: Tue, 10 Mar 2015 07:06:25 +0100
Committer: Ingo Molnar
CommitDate: Tue, 10 Mar 2015 07:14:31 +0100
x86/fpu: Factor out
Commit-ID: e7f180dcd8ab48f18b20d7e8a7e9b39192bdf8e0
Gitweb: http://git.kernel.org/tip/e7f180dcd8ab48f18b20d7e8a7e9b39192bdf8e0
Author: Oleg Nesterov
AuthorDate: Tue, 10 Mar 2015 07:06:24 +0100
Committer: Ingo Molnar
CommitDate: Tue, 10 Mar 2015 07:14:31 +0100
x86/fpu: Change
Commit-ID: 44fb085bfa17628c6d2aaa6af6b292a8499e9cbd
Gitweb: http://git.kernel.org/tip/44fb085bfa17628c6d2aaa6af6b292a8499e9cbd
Author: Wanpeng Li
AuthorDate: Tue, 10 Mar 2015 12:20:00 +0800
Committer: Ingo Molnar
CommitDate: Tue, 10 Mar 2015 05:46:50 +0100
sched/deadline: Add
Commit-ID: 394838c96013ba414a24ffe7a2a593a9154daadf
Gitweb: http://git.kernel.org/tip/394838c96013ba414a24ffe7a2a593a9154daadf
Author: Andy Lutomirski
AuthorDate: Mon, 9 Mar 2015 17:42:31 -0700
Committer: Ingo Molnar
CommitDate: Tue, 10 Mar 2015 04:21:51 +0100
x86/asm/entry/32: Fix
On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote:
>
>
> On 03/10/2015 03:17 PM, Daniel Vetter wrote:
> >On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
> >>Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
> >>Most modesetting drivers enable
So I got this error today:
┌─Warning:───┐
│The vmlinux
file can't be used. │
On Tue, Mar 10, 2015 at 03:11:30PM +0530, Archit Taneja wrote:
> DRM_I915_FBDEV config is currently used to enable/disable fbdev emulation for
> the i915 kms driver.
>
> Replace this with the top level DRM_FBDEV_EMULATION config option. Using this
> config lets us also prevent wrapping around
On Tue, Mar 10, 2015 at 12:21:21AM +0100, Heiko Stuebner wrote:
> At least the Rockchip variant of the dw_hdmi should control its supplying
> regulators. A cursory glance at the imx manual didn't any equivalent there,
> so I'm not sure if there are similar controllable regulators present.
>
>
On Sun, Mar 08, 2015 at 10:07:40PM +0200, Aaro Koskinen wrote:
> Hi,
>
> The first patch is a bug fix for OCTEON MD5 aimed for 4.0-rc cycle.
Please send such bug fixes in a separate series in future.
For this one in particular it does not appear to be critical
enough to go in straight away so I
Hi Philipp,
On Mon, Mar 09, 2015 at 11:16:26AM +0100, Philipp Zabel wrote:
>
> Am Freitag, den 06.03.2015, 16:05 +0100 schrieb Antoine Tenart:
> > The Berlin reset controller was introduced without being a platform
> > driver because of a needed DT rework: the node describing the reset
> >
This patch assigns the more appropriate void* type to the mmio750 variable
eliminating an unnecessary volatile qualifier in the process. Additionally it
updates parameter types as necessary where those parameters interact with
mmio750 and removes unnecessary casts.
As a consequence, this patch
On 03/10/2015 03:16 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide
On 03/10/2015 03:17 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit Taneja wrote:
Legacy fbdev emulation support via DRM is achieved through KMS FB helpers.
Most modesetting drivers enable provide fbdev emulation by default by selecting
KMS FB helpers. A few provide
Hi Greg,
On 23/02/15 16:32, Sudeep Holla wrote:
On architectures that depend on DT for obtaining cache hierarcy, we need
to validate the device node for all the cache indices, failing to do so
might result in wrong information being exposed to the userspace.
This is quite possible on
Hello Kukjin,
On 02/05/2015 03:45 PM, Javier Martinez Canillas wrote:
> Hello Andrzej,
>
> Thanks a lot for finally finding what was causing the HDMI issue.
>
> On 02/05/2015 01:35 PM, Andrzej Hajda wrote:
>> Hi,
>>
>> Exynos chipsets since 542x have asynchronous bridges connecting different
On Tue, 10 Mar 2015, Stephen Rothwell wrote:
> Hi Jiri,
>
> After merging the trivial tree, today's linux-next build ()
> produced this warning:
>
> drivers/tty/goldfish.c: In function 'goldfish_tty_probe':
> drivers/tty/goldfish.c:232:6: warning: unused variable 'i' [-Wunused-variable]
> int
701 - 800 of 1866 matches
Mail list logo
