Hi!
> > > > Well, mfd_core.c seems to call regulator_bulk_register_supply_alias()
> > > > with device that does not have dev_name initialized.
>
> > > OK, that'll be the problem then - we're not mapping the supply into the
> > > individual child device but rather system wide, probably because
Implement handling properties in subnodes and adding child devices to the
system. Child devices will not be added if configuration fails.
Since the driver now does more than suspend-resume support, dependency on
CONFIG_PM is removed.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
This machine uses own SoC device tree file, add missing part.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5410.dtsi
b/arch/arm/boot/dts/exynos5410.dtsi
index
The chip is smsc9115, connected via SROMc bank 3. Additionally, some GPIO
initialization is required.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos5410-smdk5410.dts | 41 +++
arch/arm/boot/dts/exynos5410.dtsi | 6
Add documentation for new subnode properties, allowing bank configuration.
Based on u-boot implementation, but heavily reworked.
Also, fix size of SROMc mapping in the example.
Signed-off-by: Pavel Fedin
Reviewed-by: Krzysztof Kozlowski
Acked-by: Rob Herring
---
This patch extends Exynos SROM controller driver with ability to configure
controller outputs and enables SMSC9115 Ethernet chip on SMDK5410 board,
which is connected via SROMc bank #3.
With this patchset, support for the whole existing SMDK range can be added.
Actually, only bank number is
On Sun, 15 Nov 2015 11:53:11 +0100,
Boaz Harrosh wrote:
>
> On 11/12/2015 10:38 PM, Takashi Iwai wrote:
> > On Thu, 12 Nov 2015 21:13:57 +0100,
> > Dan Williams wrote:
> >>
> >> There are several sound drivers that 'select ZONE_DMA'. This is
> >> backwards as ZONE_DMA is an architecture
From: Markus Elfring
Date: Mon, 16 Nov 2015 08:20:36 +0100
The mempool_destroy() function tests whether its argument is NULL
and then returns immediately. Thus the test around the calls is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
Jiang Liu wrote on 16/11/15 14:57:
From: Liu Jiang
Commit 4d6b4e69a245 ("x86/PCI/ACPI: Use common interface to support
PCI host bridge") converted x86 to use the common interface
acpi_pci_root_create, but the conversion missed on code piece in
arch/x86/pci/bus_numa.c, which causes regression
It dose not work when we want to use the usb-to-serial port based
on one usb gadget as a console. Thus this patch adds the console
initialization to support this request.
Signed-off-by: Baolin Wang
---
drivers/usb/gadget/Kconfig |6 +
drivers/usb/gadget/function/u_serial.c |
On 15 November 2015 23:11:51 GMT+00:00, Nizam Haider
wrote:
>structure iio_buffer_setup_ops is never modified, so declare it as
>const.
>
>Signed-off-by: Nizam Haider
Sometimes it feels like there is something in the air...
Julia Lawal posted a patch for this yesterday.
Thanks
Jonathan
This patch makes is_file_hugepages return bool to improve
readability due to this particular function only using either
one or zero as its return value.
This patch also removed the if condition to make is_file_hugepages
return directly.
No functional change.
Signed-off-by: Yaowei Bai
---
This patchset only performs some small improvement to mm. First, make
several functions return bool to improve readability, and then remove
unused is_unevictable_lru function and refactor memmap_valid_within
for simplicity.
No functional change.
Yaowei Bai (7):
ipc/shm: is_file_shm_hugepages
This patch makes memblock_is_memory/reserved return bool to improve
readability due to this particular function only using either
one or zero as its return value.
No functional change.
Signed-off-by: Yaowei Bai
---
include/linux/memblock.h | 4 ++--
mm/memblock.c| 4 ++--
2 files
This patch makes gfp_zonelist return bool due to this
particular function only using either one or zero as its return
value.
This patch also makes gfp_zonelist return directly by removing if.
No functional change.
Signed-off-by: Yaowei Bai
---
include/linux/gfp.h | 7 ++-
1 file changed,
Since commit a0b8cab3 ("mm: remove lru parameter from __pagevec_lru_add
and remove parts of pagevec API") there's no user of this function anymore,
so remove it.
Signed-off-by: Yaowei Bai
---
include/linux/mmzone.h | 5 -
1 file changed, 5 deletions(-)
diff --git a/include/linux/mmzone.h
This patch makes page_is_file_cache return bool to improve
readability due to this particular function only using either
one or zero as its return value.
No functional change.
Signed-off-by: Yaowei Bai
---
include/linux/mm_inline.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
This patch makes memmap_valid_within return bool due to this
particular function only using either one or zero as its return
value.
This patch also refactors memmap_valid_within for simplicity.
No functional change.
Signed-off-by: Yaowei Bai
---
include/linux/mmzone.h | 6 +++---
mm/mmzone.c
This patch makes is_file_shm_hugepages return bool to improve
readability due to this particular function only using either
one or zero as its return value.
No functional change.
Signed-off-by: Yaowei Bai
---
include/linux/shm.h | 6 +++---
ipc/shm.c | 2 +-
2 files changed, 4
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
When the usb gadget supporting for usb charger is ready, the usb charger
should get the type by the 'get_charger_type' callback which is implemented
by the usb gadget operations, and get the usb charger pointer from struct
'usb_gadget'.
Signed-off-by: Baolin Wang
---
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Introduce a callback 'get_charger_type' which
On 9/21/2015 5:32 PM, Andy Shevchenko wrote:
> On Mon, 2015-09-21 at 14:51 +0800, Fu, Zhonghui wrote:
>> Now, PM core supports asynchronous suspend/resume mode for devices
>> during system suspend/resume, and the power state transition of one
>> device may be completed in separate kernel thread.
Please review the latest version: "[PATCH v3] mmc/sdhci-acpi: enable sdhci-acpi
device to suspend/resume asynchronously"
Thanks,
Zhonghui
On 9/21/2015 2:51 PM, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the
Now, PM core supports asynchronous suspend/resume mode for devices
during system suspend/resume, and the power state transition of one
device may be completed in separate kernel thread. PM core ensures
all power state transition timing dependency between devices. This
patch enables sdhci-acpi
Hi Paolo,
Any comments about this patch, thanks in advance!
Thanks,
Feng
> -Original Message-
> From: Wu, Feng
> Sent: Monday, November 9, 2015 10:47 AM
> To: pbonz...@redhat.com
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; Wu, Feng
>
> Subject: [PATCH] KVM: x86: Add
On Mon, 2015-11-16 at 13:03 +1100, Stephen Rothwell wrote:
> Hi Nicholas,
>
> On Fri, 13 Nov 2015 12:06:05 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the target-merge tree got conflicts in
> > several files. It looks like a newer version of all the commits in the
> >
Hi Thomas,
Thanks for your help.
I have tested your patch this morning, it seems well.
Could you tell me when will you send your formal patch? And please CC me
when you send your patch.
Regards!
Yanjiang
On 2015年11月15日 19:05, Thomas Gleixner wrote:
On Sun, 15 Nov 2015, Thomas Gleixner
On Sun, Nov 15, 2015 at 05:24:37PM -0800, Linus Torvalds wrote:
> So it's Sunday, two weeks has passed, and so 4.4-rc1 is out there and
> the merge window is closed.
>
> As usual, the full shortlog is much too big to post, so appended is
> the usual shortlog of just my merges, which just shows
On Sun, Nov 15, 2015 at 05:24:37PM -0800, Linus Torvalds wrote:
> So it's Sunday, two weeks has passed, and so 4.4-rc1 is out there and
> the merge window is closed.
>
[...]
>
> Go out and test.
>
> Linus
>
After what I picked up during the 4.3 cycle, I tried using 'xzcat |
Hi Brian Norris,
Thanks for your information and the documents shared by you.
It's very helpful for me to understand the regmap.
But I think if we use:
static void qspi_writel(struct fsl_qspi *q, u32 val, void __iomem
*addr) {
if (q->big_endian)
iowrite32be(val, addr);
From: Liu Jiang
Commit 4d6b4e69a245 ("x86/PCI/ACPI: Use common interface to support
PCI host bridge") converted x86 to use the common interface
acpi_pci_root_create, but the conversion missed on code piece in
arch/x86/pci/bus_numa.c, which causes regression on some legacy
AMD platforms as
On Wed, 2015-11-11 at 12:58 +0100, Christoph Hellwig wrote:
> Can you try the patch below?
Acked-by: Don Fry
--
Since pci_set_dma_mask() returns the opposite of pci_dma_supported(),
this fix is required for proper operation. The original patch in
October was faulty.
>
> diff --git
On Mon, Nov 16, 2015 at 04:08:39AM +, Yao Yuan wrote:
> It looks like easier to read, use and change.
> Is it?
It looks fine either way, IMO.
> And David Woodhouse, Xu Han, Mark Brown
> is there any other comments from you?
FYI, Mark Brown doesn't really have much to do with this. Though he
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8005c49d9aea74d382f474ce11afbbc7d7130bec
commit: ec2f1b67f526ee0b314103f7bf2846289fa0f435 dmaengine: hsu: make the UART
driver in control of selecting this driver
date: 4 weeks ago
config:
On Fri, Nov 13, 2015 at 12:46:00PM +0100, Julia Lawall wrote:
> The dca_ops structure is never modified, so declare it as const.
>
> Done with the help of Coccinelle.
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Thu, Nov 12, 2015 at 03:18:22PM +0100, Arnd Bergmann wrote:
> dma_addr_t may be defined as 32 or 64 bit depending on configuration,
> so it cannot be printed using the normal format strings, as
> gcc correctly warns:
>
> drivers/dma/at_hdmac.c: In function 'atc_prep_dma_interleaved':
>
On Thu, Nov 12, 2015 at 03:16:53PM +0100, Arnd Bergmann wrote:
> dma_addr_t may be defined as 32 or 64 bit depending on configuration,
> so it cannot be printed using the normal format strings, as
> gcc correctly warns:
>
> drivers/dma/at_xdmac.c: In function 'at_xdmac_interleaved_queue_desc':
>
On Wed, Nov 11, 2015 at 05:20:49PM +0800, Jason Liu wrote:
> The sdma_probe function will call sdma_event_remap, but sdma_event_remap
> marked with the __init annotation which make the kbuild complains as the
> following log:
>
> WARNING: drivers/dma/built-in.o(.text+0x56fc): Section mismatch in
Hi Linus
2015-11-05 22:40 GMT+09:00 Linus Walleij :
> On Thu, Nov 5, 2015 at 12:15 PM, Masahiro Yamada
> wrote:
>
>> ARCH_SUNXI selects RESET_CONTROLLER.
>> The dependency "depends on RESET_CONTROLLER" is already met.
>>
>> Signed-off-by: Masahiro Yamada
>
> NACK, this pin controller needs that
Guten Tag,
Wir sind OCEAN FINANCE Darlehen Unternehmen geben Kredite per Post
Anzeige. Wir bieten verschiedene Arten von Krediten (kurz- und langfristige
Darlehen, persönliche Darlehen, Kredite an Unternehmen etc.) um 3% Zins. Wir
geben Kredite an Menschen in Not nicht unabhängig
On 2015/11/14 7:08, Marcelo Tosatti wrote:
On Thu, Nov 12, 2015 at 08:53:43PM +0900, Takuya Yoshikawa wrote:
At some call sites of rmap_get_first() and rmap_get_next(), BUG_ON is
placed right after the call to detect unrelated sptes which must not be
found in the reverse-mapping list.
Move
This patch simply adds a missing newline in the error string printed
by the toshiba_bluetooth_present function.
This is just a cosmetic change, no functionality was changed.
Signed-off-by: Azael Avalos
---
drivers/platform/x86/toshiba_bluetooth.c | 2 +-
1 file changed, 1 insertion(+), 1
The driver uses genetlink to inform userspace of events generated by
the system, but the data passed is always zero as there is no data to
pass, except for the hotkey event.
This patch propagates the hotkey value via genetlink so userspace can
make use of it.
Signed-off-by: Azael Avalos
---
If transflective backlight is supported and the brightness is zero
(lowest brightness level), the set_lcd_brightness function will activate
the transflective backlight, making the LCD appear to be turned off.
This patch fixes the issue by incrementing the brightness level, and
by doing so,
On Tue, Nov 03, 2015 at 03:00:57PM +0100, Arnd Bergmann wrote:
> During the edma rework, a build error was introduced for the
> case that CONFIG_OF is disabled:
>
> drivers/built-in.o: In function `edma_tc_set_pm_state':
> :(.text+0x43bf0): undefined reference to `of_find_device_by_node'
>
> As
On Tue, Nov 03, 2015 at 12:28:10PM +0200, Peter Ujfalusi wrote:
> of_dma_request_slave_channel should return either pointer for valid
> dma_chan or ERR_PTR() error code, NULL is not expected to be returned.
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe
These two patches add WWAN support to the driver, the first adds the actual
support functions and the second adds RFKill handler functions to set the
device status according to the killswitch.
Azael Avalos (2):
toshiba_acpi: Add support for WWAN devices
toshiba_acpi: Add WWAN RFKill support
Toshiba laptops with WWAN devices installed cannot use the device unless
it is attached and powered, similar to how Toshiba Bluetooth devices
work.
This patch adds support to WWAN devices, introducing three functions,
one to query the overall status of the wireless devices (RFKill, WLAN,
BT,
A previuos patch added WWAN support to the driver, allowing to query
and set the device status.
This patch adds RFKill support for the recently introduced WWAN device,
making use of the WWAN and *wireless_status functions to query the
killswitch and (de)activate the device accordingly to its
On Fri, Oct 16, 2015 at 03:59:15PM +0200, M'boumba Cedric Madianga wrote:
> This patch adds STM32 DMA bindings for STM32F429.
I need an ACK from ARM folks on this one, and I suspect this might need
rebase on 4.4-rc1
>
> Signed-off-by: M'boumba Cedric Madianga
> ---
>
On Fri, Oct 16, 2015 at 03:59:16PM +0200, M'boumba Cedric Madianga wrote:
> This patch adds STM32 DMA support in stm32_defconfig file
This seems okay, so went ahead and applied
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Fri, Oct 16, 2015 at 03:59:14PM +0200, M'boumba Cedric Madianga wrote:
> This patch adds support for the STM32 DMA controller.
>
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Fri, Oct 16, 2015 at 03:59:13PM +0200, M'boumba Cedric Madianga wrote:
> This patch adds documentation of device tree bindings for the STM32 dma
> controller.
>
Applied, thanks
--
~Vinod
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
> On Nov 16, 2015, at 10:13, Minchan Kim wrote:
>
> On Fri, Nov 13, 2015 at 11:46:07AM -0800, Andy Lutomirski wrote:
>> On Fri, Nov 13, 2015 at 12:13 AM, Daniel Micay wrote:
>>> On 13/11/15 02:03 AM, Minchan Kim wrote:
On Fri, Nov 13, 2015 at 01:45:52AM -0500, Daniel Micay wrote:
>>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 8005c49d9aea74d382f474ce11afbbc7d7130bec
commit: d9eda9bab237259b06690652b145d19e0ce37a77 serial: 8250_pci: Intel MID
UART support to its own driver
date: 4 weeks ago
config: x86_64-randconfig-s1-11161029
Hi all,
Changes since 20151115:
Dropped tree: target-merge (many conflicts)
Non-merge commits (relative to Linus' tree): 556
489 files changed, 22652 insertions(+), 7062 deletions(-)
I have created today's linux
In another patch kvm_is_visible_gfn is maken return bool due to this
function only returns zero or one as its return value, let's also make
kvmppc_visible_gpa return bool to keep consistent.
No functional change.
Signed-off-by: Yaowei Bai
---
arch/powerpc/kvm/book3s_pr.c | 4 ++--
1 file
Hi,
On 2015년 11월 16일 10:36, Krzysztof Kozlowski wrote:
> Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
> so it is built also on ARMv7. This does not bring any kind of benefit.
> There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like
> multi_v7 for ARMv7).
>
drivers/regulator/pv88090-regulator.c:471:3-8: No need to set .owner here. The
core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: James Ban
Signed-off-by: Fengguang Wu
---
drivers/regulator/pv88090-regulator.c:291:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: James Ban
Signed-off-by: Fengguang Wu
---
pv88090-regulator.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
Hi James,
[auto build test WARNING on: regulator/for-next]
[also build test WARNING on: v4.4-rc1 next-20151115]
url:
https://github.com/0day-ci/linux/commits/James-Bans/regulator-pv88090-new-regulator-driver/20151116-102239
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie
Hi,
On 2015년 11월 16일 10:36, Krzysztof Kozlowski wrote:
> The ARMv8 Exynos family SoCs in Linux kernel are currently:
> - Exynos5433 (controlled by ARCH_EXYNOS),
> - Exynos7 (controlled by ARCH_EXYNOS7).
>
> It duplicates Kconfig symbols unnecessarily, so consolidate them into
> one
On 2015/11/14 18:20, Marcelo Tosatti wrote:
The actual issue is this: a higher level page that had, under its children,
no out of sync pages, now, due to your addition, a child that is unsync:
initial state:
level1
final state:
level1 -x-> level2 -x-> level3
Where -x-> are
On Sat, Nov 14, 2015 at 06:07:51PM +0800, Amos Jianjun Kong wrote:
> On Sat, Nov 14, 2015 at 11:21 AM, Yaowei Bai
> wrote:
> > This patch makes kvm_is_visible_gfn return bool due to this particular
> > function only using either one or zero as its return value.
> >
> > No functional change.
> >
>
Move node_id zone_idx shrink flags into trace function,
so thay we don't need caculate these args if the trace is disabled,
and will make this function have less arguments.
Signed-off-by: yalin wang
---
include/trace/events/vmscan.h | 14 +++---
mm/vmscan.c | 7
> On Nov 13, 2015, at 21:16, Vlastimil Babka wrote:
>
> zone_to_nid
make sense,
i will send V2 patch ,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: James Ban
This is the driver for the Powerventure PV88090 BUCKs and LDOs regulator.
It communicates via an I2C bus to the device.
Signed-off-by: James Ban
---
This patch applies against linux-next and next-20151110
.../devicetree/bindings/regulator/pv88090.txt | 65 +++
Hi,
On 11/13/2015 11:34 PM, Dmitry Malkin wrote:
On Mon, 9 Nov 2015 15:38:33 +0800, Lu Baolu wrote:
On Intel platform, if the debug target is connected with debug
host, enabling DCE bit in command register leads to a hung bus
state. In the hung state, the host system will not see a port
On Fri, Nov 13, 2015 at 11:46:07AM -0800, Andy Lutomirski wrote:
> On Fri, Nov 13, 2015 at 12:13 AM, Daniel Micay wrote:
> > On 13/11/15 02:03 AM, Minchan Kim wrote:
> >> On Fri, Nov 13, 2015 at 01:45:52AM -0500, Daniel Micay wrote:
> And now I am thinking if we use access bit, we could
Hi Nicholas,
On Fri, 13 Nov 2015 12:06:05 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the target-merge tree got conflicts in
> several files. It looks like a newer version of all the commits in the
> target-merge tree has been applied to the scsi tree, so I just dropped
> the
Hi fengguang,
This was fixed on staging-testing branch but not yet merged.
8224ec3e05b626b1b18ed0c107f2a2b1da979553 fixes this error also.
regards,
glen lee.
On 2015년 11월 15일 08:15, kbuild test robot wrote:
Hi Glen,
FYI, the error/warning still remains.
tree:
On 11/15/15 at 09:38am, Joe Perches wrote:
> On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually printing
> > once is acceptable but sometimes it will print again and again, it looks
> > very annoying. It is better to change these
Hi,
On 11/15/15 at 07:25pm, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-11-15, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually printing
> > once is acceptable but sometimes it will print again and again, it looks
> > very annoying. It is better to change
On 2015年11月15日 06:41, Heiko Stuebner wrote:
> Hi Zain,
>
> Am Freitag, 13. November 2015, 14:44:43 schrieb Zain:
>> On 2015年11月12日 20:32, Heiko Stuebner wrote:
>>> Hi Zain,
>>>
>>> I was able to sucessfully test your crypto-driver, but have found some
>>> improvements below that should probably
On Thu, Nov 12, 2015 at 09:36:14AM +0900, Minchan Kim wrote:
> > > mmotm-2015-10-15-15-20-no-madvise_free, IOW it means git head for
> > > 54bad5da4834 arm64: add pmd_[dirty|mkclean] for THP so there is no
> > > MADV_FREE code in there
> > > + pte_mkdirty patch
> > > + freeze/unfreeze patch
>
> On Nov 13, 2015, at 23:36, Michal Hocko wrote:
>
> On Fri 13-11-15 13:01:16, Vlastimil Babka wrote:
>> On 11/13/2015 12:47 PM, yalin wang wrote:
>>> Add page_is_file_cache() for __GFP_FS check,
>>> otherwise, a Pageswapcache() && PageDirty() page can always be write
>>> back if the gfp flag
Currently the Exynos5433 (ARMv8 SoC) clock driver depends on ARCH_EXYNOS
so it is built also on ARMv7. This does not bring any kind of benefit.
There won't be a single kernel image for ARMv7 and ARMv8 SoCs (like
multi_v7 for ARMv7).
Instead build clock drivers only for respective SoC's
The ARMv8 Exynos family SoCs in Linux kernel are currently:
- Exynos5433 (controlled by ARCH_EXYNOS),
- Exynos7 (controlled by ARCH_EXYNOS7).
It duplicates Kconfig symbols unnecessarily, so consolidate them into
one ARCH_EXYNOS. Future SoCs could fall also under the ARCH_EXYNOS
symbol.
The
> On Nov 13, 2015, at 22:01, Steven Rostedt wrote:
>
> On Fri, 13 Nov 2015 19:54:11 +0800
> yalin wang wrote:
>
> TP_fast_assign(
> __entry->mm = mm;
> - __entry->pfn = pfn;
> + __entry->pfn = page_to_pfn(page);
Instead of the
Hi,
We don't need ARCH_EXYNOS7 symbol because all ARMv8 platforms should
fall under generic ARCH_EXYNOS. In the same time there is no sense
in building clocks for these ARMv8 SoCs on ARMv7 builds. In future
this will also influence PMU [1] driver.
Patch 2 *depends* on patch 1. With ack from
On 2015년 11월 13일 18:17, Arnd Bergmann wrote:
On Friday 13 November 2015 16:49:22 glen lee wrote:
Hi arnd,
I found this. These should be like this. It works fine.
+ .hif_block_tx_ext = sdio_write,
+ .hif_block_rx_ext = sdio_read,
also, wilc_hif_spi need to be fixed together like
So it's Sunday, two weeks has passed, and so 4.4-rc1 is out there and
the merge window is closed.
As usual, the full shortlog is much too big to post, so appended is
the usual shortlog of just my merges, which just shows who I did pulls
from, with a very short comment on each merge.
Just looking
Hi Enric,
[auto build test ERROR on: robh/for-next]
[also build test ERROR on: v4.3 next-20151115]
[cannot apply to: drm/drm-next]
url:
https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/Add-initial-support-for-slimport-anx78xx/20151113-200502
base: https://git.kernel.org/pub
Hi Kishon,
Any more concern on the PHY part of this series?
Thanks!
On Mon, Nov 9, 2015 at 10:56 AM, Alim Akhtar wrote:
> This patch-set introduces UFS (Universal Flash Storage) host support
> for Samsung Exynos SoC. Mostly, it consists of UFS PHY and host specific
> driver.
> And it also
On Sun, Nov 15, 2015 at 2:28 PM, Kyle Sanderson wrote:
> [] BUG: unable to handle kernel paging request at e8ff7fc1
> [] IP: [] kstat_irqs+0x4f/0x90
> [] CPU: 2 PID: 1078 Comm: usage.pl Not tainted 4.1.7-hardened-r1 #1
> [] Hardware name: Supermicro Super Server/X10SRi-F, BIOS 1.0b
Hi Patrick,
Have you tried the two patches Eric mentioned? One of my 4.1.11 server
just hanged with very similar stack trace and I am wondering whether the
aforementioned patches would help.
Thanks,
Grant
On 23/09/2015 09:31, Eric Dumazet wrote:
On Wed, 2015-09-23 at 10:25 +0200, Patrick
Hi Laura,
On Thu, 2015-11-12 at 13:39 -0800, Laura Abbott wrote:
> Hi,
> There seem to be section mismatches coming from head_64.S
>
> WARNING: vmlinux.o(.text+0x8994): Section mismatch in reference from the
> variable __boot_from_prom to the function .init.text:prom_init()
> The function
On 11/15/2015 03:54 PM, Niklas Cassel wrote:
I think that Guenter's patch should be merged asap.
Right now the bug it fixes stops us from boot testing in qemu.
I'll send out a build (failure) report after -rc1 is out.
Maybe that will create enough visibility to get the patch accepted
(or
So this patch swaps that use out for kmalloc_array instead.
Signed-off-by Nizam Haider
---
drivers/iio/adc/at91_adc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/at91_adc.c b/drivers/iio/adc/at91_adc.c
index 7b40925..f284cd6 100644
---
I think that Guenter's patch should be merged asap.
Right now the bug it fixes stops us from boot testing in qemu.
For the broken mctrl irq handling part, when Uwe
has converted mxs-auart to use the generic irq init,
I can do the same for etraxfs + make sure that it gets tested
properly on real
Device Tree bindings for the Camera Adaptation Layer (CAL) driver
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/ti-cal.txt
diff --git
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data lanes.
The driver implements the required API/ioctls to be V4L2
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
This camera engine is currently found on DRA72xx family of devices.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data
structure iio_buffer_setup_ops is never modified, so declare it as const.
Signed-off-by: Nizam Haider
---
drivers/iio/adc/xilinx-xadc-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/xilinx-xadc-core.c
b/drivers/iio/adc/xilinx-xadc-core.c
index
Device Tree bindings for the Camera Adaptation Layer (CAL) driver
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++
1 file changed, 70 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/ti-cal.txt
diff --git
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data lanes.
The driver implements the required API/ioctls to be V4L2
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
This camera engine is currently found on DRA72xx family of devices.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data
1 - 100 of 492 matches
Mail list logo
