On Wed, Oct 16, 2019 at 12:15:39PM +0200, Thierry Reding wrote:
> On Tue, Oct 15, 2019 at 07:11:39PM -0700, Guru Das Srinagesh wrote:
> > Because period and duty cycle are defined as ints with units of
> > nanoseconds, the maximum time duration that can be set is limited to
> > ~2.147 seconds.
On 2019/10/17 9:51, Tan Xiaojun wrote:
> On 2019/10/16 18:12, James Clark wrote:
>> Hi Xiaojun,
>>
What do you mean when the user specifies "event:pp", if the SPE is
available, configure and record the spe data directly via the perf event
open syscall?
(perf.data itself
On Thu, Oct 17, 2019 at 09:00:48AM +1100, Michael Ellerman wrote:
> Christian Brauner writes:
> > On Wed, Oct 16, 2019 at 11:27:32PM +1100, Michael Ellerman wrote:
> >> On a machine with a 64K PAGE_SIZE, the nested for loops in
> >> test_check_nonzero_user() can lead to soft lockups, eg:
> >>
>
> -Original Message-
> From: Vladimir Murzin [mailto:vladimir.mur...@arm.com]
> Sent: Wednesday, October 16, 2019 7:46 PM
> To: Ooi, Joyce ; Catalin Marinas
> ; Will Deacon ; Dinh Nguyen
>
> Cc: Tan, Ley Foon ; Anson Huang
> ; Arnd Bergmann ; Ong, Hean Loong
> ; See, Chin Liang ;
>
Hi Vinod,
Thanks very much for your reply.
Best Regards,
Peng
>-Original Message-
>From: Vinod Koul
>Sent: 2019年10月17日 12:11
>To: Peng Ma
>Cc: dan.j.willi...@intel.com; Leo Li ;
>linux-kernel@vger.kernel.org; dmaeng...@vger.kernel.org
>Subject: [EXT] Re: [V5 1/2] dmaengine:
On 09:08 Wed 16 Oct 2019, Randy Dunlap wrote:
On 10/15/19 11:13 PM, Bhaskar Chowdhury wrote:
This patch will remove old kernel from the system in a selective way.
Signed-off-by: Bhaskar Chowdhury
---
Thanks, a bunch to Randy for the hand holding . :)
Hi Bhaskar,
First problem is that patch
On Thu, 17 Oct 2019 at 03:24, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.197 release.
> There are 92 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
This patch series does the following:
- Reorganize the Clock Handling in Arasan SD driver
- Adds new sampling clock in Arasan SD driver
- Adds support to set Clock Delays in SD Arasan Driver
- Add SDIO Tap Delay handling in ZynqMP firmware driver
- Add support for ZynqMP Tap Delays setting in
To improve the code readability, use two different structs, one for
clock provider data and one for mmc platform data.
Signed-off-by: Manish Narani
---
drivers/mmc/host/sdhci-of-arasan.c | 31 --
1 file changed, 21 insertions(+), 10 deletions(-)
diff --git
Apart from taps set by auto tuning, ZynqMP platform has feature to set
the tap values manually. Add support to set tap delay values in HW via
ZynqMP SoC framework.
Signed-off-by: Manish Narani
---
drivers/mmc/host/sdhci-of-arasan.c | 206 -
1 file changed, 204
Add support to read Clock Phase Delays from the DT and set it via
clk_set_phase() API from clock framework. Some of the controllers might
have their own handling of setting clock delays, for this keep the
set_clk_delays as function pointer which can be assigned controller
specific handling of the
Add optional propeties for Arasan SDHCI which are used to set clk delays
for different speed modes in the controller.
Signed-off-by: Manish Narani
---
.../devicetree/bindings/mmc/arasan,sdhci.txt | 15 +++
1 file changed, 15 insertions(+)
diff --git
Add documentation for an optional input clock which is essentially used
in sampling the input data coming from the card.
Signed-off-by: Manish Narani
---
Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
There are some operations like setting the clock delays may need to have
two clocks, one for output path and one for input path. Adding input
path clock for some phys to use.
Signed-off-by: Manish Narani
---
drivers/mmc/host/sdhci-of-arasan.c | 151 +
1 file changed,
Add tap delay nodes for setting SDIO Tap Delays on ZynqMP platform.
Signed-off-by: Manish Narani
---
include/linux/firmware/xlnx-zynqmp.h | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/include/linux/firmware/xlnx-zynqmp.h
dd documentation for 'xlnx,zynqmp-8.9a' SDHCI controller and optional
properties followed by example.
Signed-off-by: Manish Narani
Reviewed-by: Rob Herring
---
.../devicetree/bindings/mmc/arasan,sdhci.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git
On Thu, 17 Oct 2019 at 03:26, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.150 release.
> There are 65 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
For P2P output, the output divider should align with the output sample
rate, if use ideal sample rate, there will be a lot of overload, which
would cause underrun.
The maximum divider of asrc clock is 1024, but there is no judgement
for this limitaion in driver, which may cause the divider
This patch adds JFFS2 FS support and remove QSPI Sector 4K size force in
the default defconfig
Signed-off-by: Ooi, Joyce
---
v2: disable CONFIG_MTD_SPI_NOR_USE_4K_SECTORS using the correct syntax
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 16-10-19, 10:43, andrew-sh.cheng wrote:
> This is due to SVS feature need to fix Vproc for calibration.
> When SVS calibration, it want to disable all opp items, except one with
> voltae 1.0V. (SVS will change the voltage field of that opp item, if the
> corresponding voltage is not 1.0V)
> In
This patch will remove old kernel from the system in a selective way.
Signed-off-by: Bhaskar Chowdhury
---
For Randy :
✔ ~/git-linux/linux-kbuild [master|AM/REBASE ↑·8|✔]
11:42 $ ./scripts/checkpatch.pl -f
scripts/0001-Fix-all-the-concern-raised-by-Randy.patch
total: 0 errors, 0 warnings, 93
> On Oct 4, 2019, at 03:04, Alan Stern wrote:
>
> On Fri, 4 Oct 2019, Kai-Heng Feng wrote:
>
>> Dell WD15 dock has a topology like this:
>> /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
>>|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 5000M
>>|__
On 16.10.19 22:23, Andrew Lunn wrote:
On Mon, Oct 14, 2019 at 08:15:47AM +0200, Oleksij Rempel wrote:
Atheros AR9331 has built-in 5 port switch. The switch can be configured
to use all 5 or 4 ports. One of built-in PHYs can be used by first built-in
ethernet controller or to be used directly
On 10/15/19 11:47 AM, Prateek Sood wrote:
> [ 943.034988] Unable to handle kernel paging request at virtual address
> 003106f2003c
> [ 943.043653] Mem abort info:
> [ 943.046679] ESR = 0x9645
> [ 943.050428] Exception class = DABT (current EL), IL = 32 bits
> [ 943.056643] SET
Hi Shimoda-san, Simon,
On Thu, Oct 17, 2019 at 4:18 AM Yoshihiro Shimoda
wrote:
> > From: Simon Horman, Sent: Wednesday, October 16, 2019 9:27 PM
>
> > > diff --git a/drivers/usb/renesas_usbhs/common.c
> > > b/drivers/usb/renesas_usbhs/common.c
> > > index 4c3de777ef6c..a3c30b609433 100644
> >
Hi Stephen,
On Thu, Oct 17, 2019 at 1:23 AM Stephen Boyd wrote:
> Quoting Geert Uytterhoeven (2019-10-16 07:31:42)
> > diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c
> > index 9efae29722588a35..34da22f8b0660989 100644
> > --- a/drivers/of/unittest.c
> > +++ b/drivers/of/unittest.c
>
On Wed, Oct 16, 2019 at 10:00:59AM -0700, Dmitry Torokhov wrote:
> On Wed, Oct 16, 2019 at 10:53:00AM +0300, Andy Shevchenko wrote:
> > On Tue, Oct 15, 2019 at 11:12:11AM -0700, Dmitry Torokhov wrote:
> > > On Tue, Oct 15, 2019 at 03:07:26PM +0300, Andy Shevchenko wrote:
> > Yes, since
On 16/10/2019 15:53, Greg KH wrote:
> I can take this now, into my -next tree. I'll do so later this week
> unless you object.
Perfect, thanks.
--
Johannes ThumshirnSUSE Labs Filesystems
jthumsh...@suse.de+49 911 74053 689
SUSE
On 15.10.19 17:43, Ilya Leoshkevich wrote:
>> Am 15.10.2019 um 17:21 schrieb Jan Kiszka :
>>
>>> @@ -113,6 +113,12 @@ lx-symbols command."""
>>> if module_file:
>>> gdb.write("loading @{addr}: {filename}\n".format(
>>> addr=module_addr, filename=module_file))
On Wed, Oct 16, 2019 at 03:15:52PM -0400, Arvind Sankar wrote:
> > > Reported-by: Arvind Sankar
> > > Tested-by: Arvind Sankar
> > > Originally-by: Christoph Hellwig
> > > Signed-off-by: Christoph Hellwig
> > > Fixed-by: Arvind Sankar
> > > Signed-off-by: Arvind Sankar
> >
> > This patch
On Thu 17-10-19 10:44:41, Anshuman Khandual wrote:
[...]
> Does this add-on documentation look okay ? Should we also mention about the
> possible reduction in chances of success during pfn block search for the
> non-power-of-two cases as the implicit alignment will probably turn out to
> be bigger
On Tue, Oct 15, 2019 at 05:31:43AM -, tip-bot2 for Arnaldo Carvalho de Melo
wrote:
> The following commit has been merged into the perf/core branch of tip:
>
> Commit-ID: d4097f1937f2242d0aa0a7c654d2159a6895e5c8
> Gitweb:
>
From: Bartosz Golaszewski
Convert the binding document for MAX77650 regulator module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/regulator/max77650-regulator.txt | 41 ---
.../regulator/max77650-regulator.yaml | 31 ++
2 files changed, 31
From: Bartosz Golaszewski
This series converts all DT binding documents for MAX77650 PMIC to YAML.
v1 -> v2:
- use upper case for abbreviations in commit messages
v2 -> v3:
- pull all example fragments into the binding document for the core MFD module
- fix all dt_binding_check errors
- add
From: Bartosz Golaszewski
Convert the binding document for MAX77650 onkey module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/input/max77650-onkey.txt | 26 --
.../bindings/input/max77650-onkey.yaml| 35 +++
2 files changed, 35
From: Bartosz Golaszewski
Convert the binding document for MAX77650 charger module to YAML.
Signed-off-by: Bartosz Golaszewski
Acked-by: Sebastian Reichel
---
.../power/supply/max77650-charger.txt | 28 ---
.../power/supply/max77650-charger.yaml| 34
From: Bartosz Golaszewski
The DT bindings for MAX77650 MFD have now been converted to YAML.
Update the MAINTAINERS entry for this set of drivers.
Signed-off-by: Bartosz Golaszewski
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS
From: Bartosz Golaszewski
Convert the binding document for MAX77650 core MFD module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../devicetree/bindings/mfd/max77650.txt | 46 --
.../devicetree/bindings/mfd/max77650.yaml | 151 ++
2 files changed, 151
From: Bartosz Golaszewski
Convert the binding document for MAX77650 LED module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/leds/leds-max77650.txt | 57 --
.../bindings/leds/leds-max77650.yaml | 58 +++
2 files changed, 58
On Wed, Oct 16, 2019 at 03:06:25PM -0600, Tuowen Zhao wrote:
> Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> in MTRR. This will cause the system to hang during boot. If possible,
> this bug could be corrected with a firmware update.
>
> Previous version:
On Wed, Oct 16, 2019 at 09:54:30AM -0700, Dmitry Torokhov wrote:
> On Wed, Oct 16, 2019 at 10:59:40AM +0300, Andy Shevchenko wrote:
> > On Tue, Oct 15, 2019 at 11:22:06AM -0700, Dmitry Torokhov wrote:
> > > On Mon, Oct 14, 2019 at 10:37:20AM +0300, Andy Shevchenko wrote:
> > > > On Fri, Oct 11,
On 17.10.19 01:47, Naoya Horiguchi wrote:
On Wed, Oct 16, 2019 at 10:57:57AM +0200, David Hildenbrand wrote:
On 16.10.19 10:54, Naoya Horiguchi wrote:
On Wed, Oct 16, 2019 at 10:34:52AM +0200, David Hildenbrand wrote:
On 16.10.19 10:27, Naoya Horiguchi wrote:
On Wed, Oct 16, 2019 at
From: Daode Huang
Use the new helper that wraps the calls to platform_get_resource()
and devm_ioremap_resource() together
Signed-off-by: Daode Huang
---
drivers/irqchip/irq-mvebu-icu.c | 3 +--
drivers/irqchip/irq-mvebu-pic.c | 3 +--
drivers/irqchip/irq-stm32-exti.c | 3 +--
Hi Linus,
here are some GPIO fixes, pertaining to Intel SoCs.
Details in the signed tag as usual.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:
Linux 5.4-rc3 (2019-10-13 16:37:36 -0700)
are available in the Git
On Mon, 07 Oct 2019 20:49:56 +0200,
Kai-Heng Feng wrote:
>
> Hi Takashi,
>
> > On Sep 25, 2019, at 19:32, Kai-Heng Feng
> > wrote:
> >
> > Nvidia proprietary driver doesn't support runtime power management, so
> > when a user only wants to use the integrated GPU, it's a common practice
> > to
On Intel Lightning Mountain SoCs QSPI controller do not use auto-poll
and Direct Access Controller (DAC).
Thanks vignesh for your time to review the patch.
The following comments are addressed..
changes from v3:
- commit messages are updated in both the patches
- moved cqspi_disable_auto_poll()
From: Ramuthevar Vadivel Murugan
On Intel Lightning Mountain SoCs QSPI controller do not use auto-poll.
This patch disables auto polling when direct access mode is disabled
Signed-off-by: Ramuthevar Vadivel Murugan
---
drivers/mtd/spi-nor/cadence-quadspi.c | 22 ++
1 file
From: Ramuthevar Vadivel Murugan
On Intel Lightning Mountain(LGM) SoCs QSPI controller do not use
Direct Access Controller(DAC).
This patch adds a quirk to disable the Direct Access Controller
for data transfer instead it uses indirect data transfer.
Signed-off-by: Ramuthevar Vadivel Murugan
Our platforms with below registers(CHCFG0 - CHCFG15) of eDMA as follows:
*---*
| Offset |OTHERS | LS1028A |
|--||---|
| 0x0 |CHCFG0 |
The following commit has been merged into the ras/core branch of tip:
Commit-ID: 9c3bafaa1fd88e4dd2dba3735a1f1abb0f2c7bb7
Gitweb:
https://git.kernel.org/tip/9c3bafaa1fd88e4dd2dba3735a1f1abb0f2c7bb7
Author:Benjamin Berg
AuthorDate:Wed, 09 Oct 2019 17:54:24 +02:00
On 17.10.19 09:11, Michal Hocko wrote:
On Thu 17-10-19 10:44:41, Anshuman Khandual wrote:
[...]
Does this add-on documentation look okay ? Should we also mention about the
possible reduction in chances of success during pfn block search for the
non-power-of-two cases as the implicit alignment
On 10/17/19 3:17 AM, Joe Lawrence wrote:
> On 10/16/19 1:06 PM, Kamalesh Babulal wrote:
>> On 10/16/19 5:03 PM, Miroslav Benes wrote:
>>> From: Joe Lawrence
>>>
>>> Since livepatching depends upon ftrace handlers to implement "patched"
>>> code functionality, verify that the ftrace_enabled sysctl
Hi,
On Wed 16 Oct 19, 16:56, YueHaibing wrote:
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
This is still:
Acked-by: Paul Kocialkowski
Please collect the tag in your next version, if there's a need for one.
Cheers,
Paul
>
Add the new compatible string for ZynqMP SD Host Controller for its use
in the Arasan SDHCI driver for some of the ZynqMP specific operations.
Add required properties for the same.
Signed-off-by: Manish Narani
---
This patch depends on the below series of patches:
On Wed, 16 Oct 2019, Wen Su wrote:
> From: "wen.su"
Should be:
From: Wen Su
> This adds MediaTek PMIC MT6359 registers definition for the
> following sub modules:
>
> - Regulator
> - RTC
> - Interrupt
>
> Signed-off-by: wen.su
Same here. Please change your Git config.
> ---
>
On Thu, Oct 17, 2019 at 12:26:55PM +0900, Masami Hiramatsu wrote:
> Hi Peter,
>
> On Wed, 9 Oct 2019 14:31:06 +0200
> Peter Zijlstra wrote:
>
> > On Tue, Sep 17, 2019 at 03:14:03PM +0900, Masami Hiramatsu wrote:
> > > Hi Peter,
> > >
> > > Could you review this version?
> >
> > These look
--
Dear Friend (Assalamu Alaikum),
I came across your e-mail contact prior a private search while in need of
your assistance. My name is Aisha Al-Qaddafi a single Mother and a Widow
with three Children. I am the only biological Daughter of late Libyan
President (Late Colonel Muammar Gaddafi).
On Thu, 17 Oct 2019, Andy Shevchenko wrote:
> On Wed, Oct 16, 2019 at 03:06:25PM -0600, Tuowen Zhao wrote:
> > Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> > in MTRR. This will cause the system to hang during boot. If possible,
> > this bug could be corrected with a
ping..., this issue still in linux-next 20191017
On 2019/9/28 16:16, YueHaibing wrote:
> when do randbuilding, I got this error:
>
> sound/soc/atmel/atmel_ssc_dai.o: In function `atmel_ssc_set_audio':
> (.text+0x12f6): undefined reference to `atmel_pcm_pdc_platform_register'
>
&g
On Thu 17-10-19 09:21:24, David Hildenbrand wrote:
> On 17.10.19 09:11, Michal Hocko wrote:
> > On Thu 17-10-19 10:44:41, Anshuman Khandual wrote:
> > [...]
> > > Does this add-on documentation look okay ? Should we also mention about
> > > the
> > > possible reduction in chances of success
On 10/9/19 7:16 pm, Christophe Leroy wrote:
+#if defined(CONFIG_VMAP_STACK) && CONFIG_THREAD_SHIFT < PAGE_SHIFT
+#define THREAD_SHIFT PAGE_SHIFT
+#else
#define THREAD_SHIFT CONFIG_THREAD_SHIFT
+#endif
#define THREAD_SIZE (1 << THREAD_SHIFT)
Looking at 64-bit
On 17.10.19 09:34, Michal Hocko wrote:
On Thu 17-10-19 09:21:24, David Hildenbrand wrote:
On 17.10.19 09:11, Michal Hocko wrote:
On Thu 17-10-19 10:44:41, Anshuman Khandual wrote:
[...]
Does this add-on documentation look okay ? Should we also mention about the
possible reduction in chances
On 16/10/2019 21:28, David Miller wrote:
From: "Ben Dooks (Codethink)"
Date: Wed, 16 Oct 2019 09:22:05 +0100
The stmmac_pcs_ctrl_ane() expects a register address as
argument 1, but for some reason the mac_device_info is
being passed.
Fix the warning (and possible bug) from sparse:
On Thu, Oct 17, 2019 at 1:43 PM Mickael GUENE wrote:
>
> Hello Chuhong,
>
> Is this check necessary ?
> since looking into code it seems to me devm_gpiod_get_optional() can only
> return NULL in case of error due to following check in
> devm_gpiod_get_index_optional()
> if
Hi Thierry, Hi Rob, Hi Kishon,
Please let me know your thoughts of the below implementation.
1. Add a "bool disable_gen2" to "phy->attrs" structure.
2. In _of_phy_get() of phy-core.c to add the follow to parse a generic property.
phy->attrs.disable_gen2 = of_property_read_bool(args.np,
On Wednesday 16 October 2019 16:33:17 Sasha Levin wrote:
> On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote:
> > On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote:
> > > On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote:
> > > > On Friday 30 August 2019 09:56:47 Pali Rohár
On 10/16/19 9:28 PM, Jernej Skrabec wrote:
> Allwinner H3 SoC contains deinterlace unit, which has several modes of
> operation - bypass, weave, bob and mixed (advanced) mode. I don't know
> how mixed mode works, but according to Allwinner it gives best results,
> so they use it exclusively.
On Thu, Oct 17, 2019 at 09:16:42AM +0200, David Hildenbrand wrote:
> On 17.10.19 01:47, Naoya Horiguchi wrote:
> > On Wed, Oct 16, 2019 at 10:57:57AM +0200, David Hildenbrand wrote:
> > > On 16.10.19 10:54, Naoya Horiguchi wrote:
> > > > On Wed, Oct 16, 2019 at 10:34:52AM +0200, David Hildenbrand
On Wednesday 16 October 2019 17:53:43 Valdis Klētnieks wrote:
> and may cause problems if Linux says "currently using FAT 2", and the
> disk is next used on a Windows 10 box that only looks at FAT 1
You should use same algorithm which is used for FAT32. Primary FAT is
first. And all
USB_DR_MODE_UNKNOWN should be treated as error as it is done in
cdns3_drd_update_mode().
Fixes: 02ffc26df96b ("usb: cdns3: fix cdns3_core_init_role()")
Signed-off-by: Roger Quadros
---
drivers/usb/cdns3/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
On 17.10.19 09:50, Naoya Horiguchi wrote:
On Thu, Oct 17, 2019 at 09:16:42AM +0200, David Hildenbrand wrote:
On 17.10.19 01:47, Naoya Horiguchi wrote:
On Wed, Oct 16, 2019 at 10:57:57AM +0200, David Hildenbrand wrote:
On 16.10.19 10:54, Naoya Horiguchi wrote:
On Wed, Oct 16, 2019 at
On Thu, Oct 17, 2019 at 07:50:18AM +, Naoya Horiguchi wrote:
> Actually I guess that !pfn_valid() never happens when called from
> madvise_inject_error(), because madvise_inject_error() gets pfn via
> get_user_pages_fast() which only returns valid page for valid pfn.
>
> And we plan to remove
On Thu, Oct 17, 2019 at 08:31:16AM +0100, Lee Jones wrote:
> On Thu, 17 Oct 2019, Andy Shevchenko wrote:
> > On Wed, Oct 16, 2019 at 03:06:25PM -0600, Tuowen Zhao wrote:
> > > Some BIOS erroneously specifies write-combining BAR for intel-lpss-pci
> > > in MTRR. This will cause the system to hang
On 16.10.19 22:05, Dave Hansen wrote:
The memory hierarchy is getting more complicated and the kernel is
playing an increasing role in managing the different tiers. A few
different groups of folks described "migration" optimizations they were
doing in this area at LSF/MM earlier this year. One
On Wed, Oct 16, 2019 at 06:53:20PM +0200, Miguel Ojeda wrote:
> On Wed, Oct 16, 2019 at 10:24 AM Lars Poeschel wrote:
> >
> > charlcd.c contains lots of hd44780 hardware specific stuff. It is nearly
> > impossible to reuse the interface for other character based displays.
> > The current users of
On Wed, 2019-10-16 at 22:22 +0200, Stefan Agner wrote:
> On 2019-10-16 17:18, Philippe Schenker wrote:
> > Use UARTMODIR defines instead of UARTMODEM as it is a 32-bit
> > function
>
> This reads a bit strange at first. Also it is helpful for later to
> state
> that this does not make a
Hi Rui,
On 19-10-16 14:43, Rui Miguel Silva wrote:
> Hi Marco,
> On Wed 16 Oct 2019 at 10:06, Marco Felsch wrote:
> > Hi Chuhong,
> >
> > On 19-10-15 21:59, Chuhong Yuan wrote:
> >> devm_regulator_get may return an error but mipi_csis_phy_init misses
> >> a check for it.
> >> This may lead to
On Thu, Oct 17, 2019 at 10:03:21AM +0200, Oscar Salvador wrote:
> On Thu, Oct 17, 2019 at 07:50:18AM +, Naoya Horiguchi wrote:
> > Actually I guess that !pfn_valid() never happens when called from
> > madvise_inject_error(), because madvise_inject_error() gets pfn via
> > get_user_pages_fast()
Hi Frieder,
On 19-10-16 15:06, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> In order to support more of the i.MX6UL/ULL-based SoMs and boards by
> Kontron Electronics GmbH, we restructure the devicetrees to share common
> parts and add new devicetrees for the missing boards.
>
>
On Fri, 11 Oct 2019 19:19:36 +0200,
Szabolcs Szőke wrote:
>
> BOSS Katana amplifiers cannot be used for recording or playback if quirks
> are applied
>
> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=195223
> Signed-off-by: Szabolcs Szőke
Applied now. Thanks.
Takashi
>
> ---
>
On Thu, 17 Oct 2019, Andy Shevchenko wrote:
> On Thu, Oct 17, 2019 at 08:31:16AM +0100, Lee Jones wrote:
> > On Thu, 17 Oct 2019, Andy Shevchenko wrote:
> > > On Wed, Oct 16, 2019 at 03:06:25PM -0600, Tuowen Zhao wrote:
> > > > Some BIOS erroneously specifies write-combining BAR for
On 2019-10-17 08:13, Daode Huang wrote:
From: Daode Huang
Use the new helper that wraps the calls to platform_get_resource()
and devm_ioremap_resource() together
Signed-off-by: Daode Huang
---
drivers/irqchip/irq-mvebu-icu.c | 3 +--
drivers/irqchip/irq-mvebu-pic.c | 3 +--
HugeTLB helper alloc_gigantic_page() implements fairly generic allocation
method where it scans over various zones looking for a large contiguous pfn
range before trying to allocate it with alloc_contig_range(). Other than
deriving the requested order from 'struct hstate', there is nothing HugeTLB
Hi Marco,
On 17.10.19 10:14, Marco Felsch wrote:
> Hi Frieder,
>
> On 19-10-16 15:06, Schrempf Frieder wrote:
>> From: Frieder Schrempf
>>
>> In order to support more of the i.MX6UL/ULL-based SoMs and boards by
>> Kontron Electronics GmbH, we restructure the devicetrees to share common
>> parts
On Mon, Oct 14, 2019 at 05:16:02PM +0100, Douglas Raillard wrote:
> random idea: Since these things are much easier to understand by looking at a
> graph
> of util over time, we may agree on some mailing-list-friendly way to convey
> graphs.
I don't think that this patch warrants something
From: Min Guo
Add noirq type of dma create interface for platform which do not
have dedicated DMA interrupt line, move musbhsdma macro definition
to musb_dma.h
Signed-off-by: Min Guo
---
changes in v7:
1. no changes
changes in v6:
1. no changes
changes in v5:
1. no changes
new patch based
From: Min Guo
Add get/set toggle hooks in struct musb_io and struct musb_platform_ops
for special platform; remove function musb_save_toggle, use the set/get
callback to handle toggle.
Signed-off-by: Min Guo
---
changes in v7:
1. no changes
changes in v6:
1. no changes
changes in v5:
1. no
From: Min Guo
These patches introduce the MediaTek MUSB controller driver.
The driver can be configured as Dual-Role Device (DRD),
Peripheral Only and Host Only modes. This has beed tested on
MT2701 with a variety of devices in host mode and with the
f_mass gadget driver in peripheral mode,
In the format of synthetic events, the "gfp_t" is shown as "signed:1",
but in fact the "gfp_t" is "unsigned", should be shown as "signed:0".
The offset should be increased by the real size of each field, rather
than by the size of "u64".
The issue can be reproduced by the following commands:
From: Min Guo
This adds support for MediaTek musb controller in
host, peripheral and otg mode.
There are some quirk of MediaTek musb controller, such as:
-W1C interrupt status registers
-Private data toggle registers
-No dedicated DMA interrupt line
Signed-off-by: Min Guo
Signed-off-by:
From: Min Guo
Add musb nodes and usb2 phy nodes for MT2701
Signed-off-by: Min Guo
---
changes in v7:
1. Change usb connector child node compatible as "gpio-usb-b-connector"
changes in v6:
1. Modify usb connector child node
changes in v5:
1. Add usb connector child node
changes in v4:
1. no
From: Min Guo
This adds support for MediaTek musb controller in
host, peripheral and otg mode.
Signed-off-by: Min Guo
---
changes in v7:
1. Modify compatible as
- compatible : should be one of:
"mediatek,mt2701-musb"
...
followed by
From: Min Guo
Delete the const attribute of addr parameter in readb/w/l hooks, these
changes are for implementing clearing W1C registers.
Replace musb_readb/w with musb_clearb/w to clear the interrupt status.
Signed-off-by: Min Guo
---
changes in v7:
1. no changes
changes in v6:
1. no changes
Hi,
It would be good, if we can change the name of the script to more
explicit name ,which also tell us the purpose of the script by just
looking at it.
The present name "mkmakefile" is perfectly alright for the people ,who
are technically inclined not so with other, who wants to understand.
check drivers/irqchip with "make coccicheck M=drivers/irqchip/",
it will report unneeded semicolon like below, just remove them.
drivers/irqchip/irq-zevio.c:54:2-3: Unneeded semicolon
drivers/irqchip/irq-gic-v3.c:177:2-3: Unneeded semicolon
drivers/irqchip/irq-gic-v3.c:234:2-3: Unneeded semicolon
On Thu 10-10-19 21:09:24, Chengguang Xu wrote:
> It's not a functinal change, it's just for keeping
> consistent coding style.
>
> Signed-off-by: Chengguang Xu
Thanks. Applied.
Honza
> ---
> fs/quota/quota_v1.c | 1 -
> 1 file
On Tue 15-10-19 14:25:18, Ben Dooks wrote:
> Move fsnotify_mark_connector_cachep to fsnotify.h to properly
> share it with the user in mark.c and avoid the following warning
> from sparse:
>
> fs/notify/mark.c:82:19: warning: symbol 'fsnotify_mark_connector_cachep' was
> not declared. Should it
On Wed 16-10-19 10:59:55, Ben Dooks (Codethink) wrote:
> The call to exportfs_encode_inode_fh() takes an pointer
> as the 4th argument, so replace the integer 0 with the
> NULL pointer.
>
> This fixes the following sparse warning:
>
> fs/notify/fdinfo.c:53:87: warning: Using plain integer as
This patchset add support for mt2701 JPEG ENC support.
This is the compliance test result for jpeg dec and enc.
The JPEG dec log:
v4l2-compliance -d /dev/video0
Add jpeg enc device tree node document
Reviewed-by: Rob Herring
Signed-off-by: Xia Jiang
---
v4: no changes
v3: change compatible to SoC specific compatible
v2: no changes
---
.../bindings/media/mediatek-jpeg-encoder.txt | 37 +++
1 file changed, 37 insertions(+)
create
1 - 100 of 1059 matches
Mail list logo
