Because hp300_read_clk() never checks the timer interrupt flag it may
fail to notice that the timer has wrapped, allowing the clock to jump
backwards. This is not a new problem.
This is resolved by checking the interrupt flag and, if need be,
taking wrap-around into account. The interrupt handler
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Normally the MFP timer C interrupt flag would be used to check for
timer counter wrap-around. Unfortunately, that flag gets cleared by the
MFP itself (due to automatic End-of-Interrupt mode). This means that
The functions that implement arch_gettimeoffset are re-used by
new clocksource drivers in subsequent patches.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
arch/m68k/Kconfig | 1 -
arch/m68k/amiga/config.c| 3 ---
arch/m68k/atari/config.c| 2 --
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
Changed since v2:
- Don't check for timer interrupt in amiga_read_clk() when the timer is
about to be reloaded.
Changed since v1:
- Moved clk_total
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
Changed since v2:
- Don't check for timer interrupt in bvme6000_read_clk() when the timer is
about to be reloaded.
Changed since v1:
- Moved clk_total
These dummy implementations are no better than
default_arch_gettimeoffset() so remove them.
Signed-off-by: Finn Thain
---
arch/m68k/apollo/config.c | 7 ---
arch/m68k/q40/config.c| 9 -
arch/m68k/sun3/config.c | 2 --
arch/m68k/sun3/intersil.c | 7 ---
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
Tested-by: Stan Johnson
---
Changed since v2:
- Drop unneeded 'clk_offset' variable.
Changed since v1:
- Moved clk_total access to within the irq lock.
-
Reading the timer counter races with timer overflow (and the
corresponding interrupt). This is resolved by reading the overflow
register and taking this value into account. The interrupt handler
must clear the overflow register when it eventually executes.
Suggested-by: Thomas Gleixner
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
Changed since v1:
- Moved clk_total access to within the irq lock.
---
arch/m68k/mvme16x/config.c | 37 +++--
1 file
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
Changed since v1:
- Moved clk_total access to within the irq lock.
- Use type u32 for tick counter.
---
arch/m68k/hp300/time.c | 37
Add a platform clocksource by adapting the existing arch_gettimeoffset
implementation.
Signed-off-by: Finn Thain
Acked-by: Linus Walleij
---
Changed since v1:
- Moved clk_total access to within the irq lock.
- Use type u32 for tick counter.
---
arch/m68k/include/asm/mvme147hw.h | 1 -
This series removes "select ARCH_USES_GETTIMEOFFSET" from arch/m68k
and converts users of arch_gettimeoffset to the clocksource API.
Various bugs are fixed along the way.
Those platforms which do not actually implement arch_gettimeoffset
(apollo, q40, sun3, sun3x) use the "jiffies" clocksource by
On 11/21/18 11:16 AM, Linus Torvalds wrote:
> On Wed, Nov 21, 2018 at 9:27 AM Linus Torvalds
> wrote:
>>
>> It would be interesting to know exactly which copy it is that matters
>> so much... *inlining* the erms case might show that nicely in
>> profiles.
>
> Side note: the fact that Jens'
> On Nov 22, 2018, at 4:56 PM, Thomas Gleixner wrote:
>
> On Tue, 20 Nov 2018, Qian Cai wrote:
>
> Looking deeper at that.
>
>> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
>> index 70935ed91125..140571aa483c 100644
>> --- a/lib/debugobjects.c
>> +++ b/lib/debugobjects.c
>> @@ -23,9
On 11/22/18 3:56 AM, Andy Shevchenko wrote:
On Wed, Nov 21, 2018 at 11:17:41PM +0100, Takashi Iwai wrote:
On Wed, 21 Nov 2018 18:38:41 +0100, Andy Shevchenko wrote:
Compare:
/* CFL */
{ PCI_DEVICE(0x8086, 0xa348),
.driver_data = (unsigned
On Thu, Nov 15, 2018 at 7:17 AM Mike Rapoport wrote:
>
> On Tue, Nov 06, 2018 at 05:36:42PM +0530, Souptick Joarder wrote:
> > Page fault handlers are supposed to return VM_FAULT codes,
> > but some drivers/file systems mistakenly return error
> > numbers. Now that all drivers/file systems have
On 11/23/2018 11:30 AM, Mimi Zohar wrote:
> On Fri, 2018-11-23 at 11:03 -0800, Casey Schaufler wrote:
>> On 11/22/2018 7:49 AM, Roberto Sassu wrote:
>>> Although rootfs (tmpfs) supports xattrs, they are not set due to the
>>> limitation of the cpio format. A new format called 'newcx' was proposed
On Sat, Oct 13, 2018 at 10:59:46AM -0700, Randy Dunlap wrote:
> 4.19-rc7, on x86_64:
>
> modprobe test_kmod; rmmod test_kmod
>
> [ 199.033143] calling test_kmod_init+0x0/0x1000 [test_kmod] @ 1704
> [ 199.034636] misc test_kmod0: interface ready
> [ 199.035468] initcall
We double free the misc device string twice on rmmod, fix this.
Without this we cannot remove the module without crashing.
Cc: # for v4.12 and up
Reported-by: Randy Dunlap
Signed-off-by: Luis Chamberlain
---
lib/test_kmod.c | 1 -
1 file changed, 1 deletion(-)
diff --git
On Sat, Nov 24, 2018 at 2:37 AM Steven Rostedt wrote:
>
> On Fri, 23 Nov 2018 09:01:18 +0900
> Namhyung Kim wrote:
>
> > Acked-by: Namhyung Kim
>
> Thanks Namhyung!
It'd be nice if you cc me for the whole patchset (and other tracing
patches) next time.
Thanks,
Namhyung
On Wed, Nov 14, 2018 at 06:49:38PM +0100, Stefan Agner wrote:
> The ipg clock only needs to be unprepared in case preparing
> per clock fails. The ipg clock has already disabled at the point.
>
> Fixes: 1cf93e0d5488 ("serial: imx: remove the uart_console() check")
> Signed-off-by: Stefan Agner
>
On Wed, Nov 14, 2018 at 06:49:39PM +0100, Stefan Agner wrote:
> Currently imx_uart_console_setup() prepares clocks which do not
> get unprepared anywhere. Check whether the console has been used
> by testing if index is set and unprepare clocks in this case.
>
> This makes sure that clocks are
Hi Linus,
here are a few collected GPIO fixes for the v4.20 series.
Minor stuff except the IDA leak which was kind of important
to fix. Also new maintainers, yay.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux
On Thu, 22 Nov 2018 at 00:36, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.4 release.
> There are 42 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.
>
>
Hello Robert,
Do you have any comments about this patch?
Thanks.
Cheers
Dongsheng
On 2018/11/13 18:46, Wang, Dongsheng wrote:
> The new naming rule is added in acpica version 20180427.
> So the dsdt aml code name changes from "AmlCode" to "dsdt_aml_code".
>
> The patch that introduces naming
Hi Miquel,
On Thu, Nov 22, 2018 at 09:19:09PM +0100, Miquel Raynal wrote:
> Rename the mvebu_comhy_conf structure to be mvebu_comphy_conf, which is
> probably what the original author meant.
>
> Fixes: d0438bd6aa09 ("phy: add the mvebu cp110 comphy driver")
Could you drop the Fixes tag and send
On Thu, Nov 22, 2018 at 12:41 PM Roger Quadros wrote:
> +
> + if (IS_ERR_OR_NULL(rproc))
> + return ERR_PTR(-EINVAL);
Any usage of IS_ERR_OR_NULL() tends to be an indication of a badly
designed API. Please change this to allow only one of the two to be passed
around.
On 23/11/2018 2:51 PM, Daniel Lezcano wrote:
>
> Hi wei,
>
> On 23/11/2018 07:15, Wei Ni wrote:
>>
>>
>> On 22/11/2018 9:07 PM, Daniel Lezcano wrote:
>>> On 22/11/2018 08:10, Wei Ni wrote:
On 21/11/2018 8:51 PM, Daniel Lezcano wrote:
> On 21/11/2018 11:23, Wei Ni wrote:
Contact UPS for your Donation visa card of 1 million usd
/commits/Miquel-Raynal/Link-consumer-with-clock-driver/20181123-113833
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: sh-titan_defconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https
Hello,
+ Adding people concerned by this driver that I forgot when initially
sending the driver, will update the Cc: list if there is a v2.
One question below.
Miquel Raynal wrote on Thu, 22 Nov 2018
22:04:16 +0100:
> Add a driver to support COMPHY, a hardware block providing shared
>
This patch series intends to add CAN self wakeup support. The CAN controller
can parse "fsl,stop-mode" property from device tree to enable self wakeup
feature.
Aisheng Dong (2):
Documentation: can: flexcan: add stop mode property to device tree
can: flexcan: add self wakeup support
From: Aisheng Dong
The FlexCAN controller can parse the stop mode property to enable CAN
self wakeup feature.
Signed-off-by: Aisheng Dong
Signed-off-by: Joakim Zhang
---
ChangeLog:
V1->V2:
*add a vendor prefix in property (stop-mode -> fsl,stop-mode).
V2->V6:
*no change.
---
From: Aisheng Dong
If wakeup is enabled, enter stop mode, else enter disabled mode. Self wake
can only work on stop mode.
Starting from IMX6, the flexcan stop mode control bits is SoC specific,
move it out of IP driver and parse it from devicetree.
Signed-off-by: Aisheng Dong
Signed-off-by:
Am Freitag, 23. November 2018, 08:47:31 schrieb Greg KH:
> I'm announcing the release of the 4.9.139 kernel.
>
> All users of the 4.9 kernel series must upgrade.
>
> The updated 4.9.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
> -Original Message-
> From: Joakim Zhang
> Sent: Friday, November 23, 2018 4:35 PM
> To: linux-...@vger.kernel.org; m...@pengutronix.de; robh...@kernel.org
> Cc: w...@grandegger.com; mark.rutl...@arm.com; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; dl-linux-imx ; Joakim
>
On 23/11/2018 10:20, Arnd Bergmann wrote:
On Thu, Nov 22, 2018 at 12:41 PM Roger Quadros wrote:
+
+ if (IS_ERR_OR_NULL(rproc))
+ return ERR_PTR(-EINVAL);
Any usage of IS_ERR_OR_NULL() tends to be an indication of a badly
designed API. Please change this to allow only
://github.com/0day-ci/linux/commits/Charles-Keepax/regulator-lochnagar-Move-driver-to-binding-from-DT/20181123-133943
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: sh-allyesconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
The function hfs_bmap_free frees node via hfs_bnode_put(node). However,
it then reads node->this when dumping error message on an error path,
which may result in a use-after-free bug. This patch frees node only
when it is never used.
Fixes: d614267329f("hfs/hfsplus: convert printks to pr_")
HI Sasha,
On 23.11.18 08:30, Sasha Levin wrote:
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: 03274a3ffb44 tracing/fgraph: Adjust fgraph depth before calling
trace return callback.
The bot has tested the following trees: v4.19.3, v4.14.82, v4.9.138,
The i.MX GPT timer driver binding doc is out of date,
the "interrupts", "clocks" and "clock-names" do NOT match
current GPT driver implementation, update it and use i.MX6SX
as example.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/timer/fsl,imxgpt.txt | 22 +-
On 22-11-18, 11:38, Viresh Kumar wrote:
> So there are few complexities in the case where an OPP table points to itself
> in
> the required-opp field. I looked at solving it up in the opp core but that
> gets
> more and more messy.
>
> Now there is actually a assumption within the OPP core.
tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Miquel-Raynal/Link-consumer-with-clock-driver/20181123-113833
> base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
> config: sh-titan_def
On Fri, Nov 23, 2018 at 05:00:57PM +0800, kbuild test robot wrote:
> Hi Charles,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on ljones-mfd/for-mfd-next]
> [also build test ERROR on v4.20-rc3]
> [cannot apply to next-20181122]
> [if your patch is applied to the
Rename the mvebu_comhy_conf structure to be mvebu_comphy_conf, which is
probably what the original author meant.
Signed-off-by: Miquel Raynal
---
Changes since v1
* Removed the Fixes: tag after Antoine's request.
drivers/phy/marvell/phy-mvebu-cp110-comphy.c | 4 ++--
1 file
On Fri, Nov 23, 2018 at 09:55:47AM +0100, Rainer Fiebig wrote:
> Am Freitag, 23. November 2018, 08:47:31 schrieb Greg KH:
> > I'm announcing the release of the 4.9.139 kernel.
> >
> > All users of the 4.9 kernel series must upgrade.
> >
> > The updated 4.9.y git tree can be found at:
> >
Hi Charles,
On 2018-11-22 18:30, Charles Keepax wrote:
> This reverts commit 466affa06703 ("regulator: wm8994: Don't
> use devres for enable GPIOs"). Whilst that did work around the
> issue in question there are complications on the error paths of
> regulator_register. In the success case clearly
Hi Charles,
On 2018-11-22 18:30, Charles Keepax wrote:
> Currently, the regulator core will take ownership of any GPIO passed
> into it. Makes end driver code fairly error prone as the normal devm_
> patterns of allocation don't work. Update the regulator core to only
> free the GPIO if it
Hi Charles,
On 2018-11-22 18:30, Charles Keepax wrote:
> Currently, a GPIO can be requested multiple times when the
> NONEXCLUSIVE flag is set, however it must still be freed a single
> time. This makes client code rather complex, since multiple drivers
> may request the GPIO but only a single
Hi,
I made an attempt at implementing the
user_access_begin()/user_access_end() macros along with the
get/put_user_unsafe() for arm64 by toggling the status of PAN (more or
less similar to x86's STAC/CTAC).
With a small mistake in my patch, we realized that directly calling
function that
From: Maxime Ripard
The COEF_RDY bit isn't found in all the SoCs featuring some variant of the
frontend.
Add it to our quirks structure.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/sun4i/sun4i_frontend.c | 9 +
drivers/gpu/drm/sun4i/sun4i_frontend.h | 1 +
2 files changed, 6
This adds the appropriate device-tree compatible and quirk data for
hooking frontend support for the A20. It supports the FIR coefficients
ready bit but not the access control bit. It also takes different phase
values than the A33 for these coefficients.
The compatible is already used in the A20
This introduces support for packed YUV formats with 4:2:2 sampling using
the frontend. Definitions are introduced for the data format and pixel
sequence input format register values.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/sun4i/sun4i_frontend.c | 22 ++
Hi Vivek, Will,
On Fri, Nov 23, 2018 at 6:13 PM Vivek Gautam
wrote:
>
> Hi Will,
>
> On Wed, Nov 21, 2018 at 11:09 PM Will Deacon wrote:
> >
> > [+Thor]
> >
> > On Fri, Nov 16, 2018 at 04:54:30PM +0530, Vivek Gautam wrote:
> > > qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
> > >
Hi,
On Thu, 22 Nov 2018 at 21:05, Uwe Kleine-König
wrote:
>
> Hello Clément,
>
> On Wed, Nov 21, 2018 at 01:35:08PM +0100, Clément Péron wrote:
> > The Cygnus architecture use a Kona PWM. This is already present
> > in the device tree but can't be built actually. Hence, allow the
> > Kona PWM to
This adds a new helper to check whether the format described by its
fourcc code uses a YUV colorspace, by returning the is_yuv entry for
the DRM info entry matching that format.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/drm_fourcc.c | 19 +++
include/drm/drm_fourcc.h
This series implements support for YUV formats using the display engine
frontend in the sun4i DRM driver, with various fixes along the way.
Scaling is supported for every format handled by the frontend.
The tiling mode used by the VPU on Allwinner platforms is also supported
by this series and a
Hi Miquel,
On Fri, Nov 23, 2018 at 10:21:15AM +0100, Miquel Raynal wrote:
> Rename the mvebu_comhy_conf structure to be mvebu_comphy_conf, which is
> probably what the original author meant.
>
> Signed-off-by: Miquel Raynal
Acked-by: Antoine Tenart
Thanks!
Antoine
> ---
>
> Changes since
From: Linus Torvalds
> Sent: 22 November 2018 18:58
...
> Oh, and I just noticed that on x86 we expressly use our old "safe and
> sane" functions: see __inline_memcpy(), and its use in
> __memcpy_{from,to}io().
>
> So the "falls back to memcpy" was always a red herring. We don't
> actually do
The Cygnus architecture use a Kona PWM. This is already present
in the device tree but can't be built actually. Hence, allow the
Kona PWM to be built for Cygnus arch.
Signed-off-by: Clément Péron
Reviewed-by: Florian Fainelli
Reviewed-by: Scott Branden
Acked-by: Uwe Kleine-König
---
With Micrel KSZ8061 PHY, the link may occasionally not come up after
Ethernet cable connect. The vendor's (Microchip, former Micrel) errata
sheet 8688A.pdf describes the problem and possible workarounds in
detail, see below.
The patch implements workaround 1, which permanently fixes the issue.
On 23/11/18 10:20, Arnd Bergmann wrote:
> On Thu, Nov 22, 2018 at 12:41 PM Roger Quadros wrote:
>
>> +
>> + if (IS_ERR_OR_NULL(rproc))
>> + return ERR_PTR(-EINVAL);
>
>
> Any usage of IS_ERR_OR_NULL() tends to be an indication of a badly
> designed API. Please change this
On Thu, Nov 22, 2018 at 6:30 PM Charles Keepax
wrote:
> Currently, a GPIO can be requested multiple times when the
> NONEXCLUSIVE flag is set, however it must still be freed a single
> time. This makes client code rather complex, since multiple drivers
> may request the GPIO but only a single
Hi Phil,
Thanks for your patch!
On Mon, Nov 19, 2018 at 5:18 PM Phil Edworthy wrote:
> This fixes the check for unused mdio bus setting and the following static
> checker warning:
> drivers/pinctrl/pinctrl-rzn1.c:198 rzn1_pinctrl_mdio_select()
> warn: always true condition
te to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Roger-Quadros/Add-support-for-TI-PRU-ICSS/20181123-083903
> base:
> https://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
> next
> config: arm-allmodconfig (attac
Hello Tudor,
On 22/11/2018 13:36, tudor.amba...@microchip.com wrote:
> From: Tudor Ambarus
>
> Bug reported for the out-of-tree S25FS128S flash memory.
>
> BFPT table advertises all the erase types supported by all the
> possible map configurations. Update the erase_type array to indicate
>
Add missing Netwwork on chip for g3d bus node using VDD_INI
for Exynos542x SoC.
- CLK_DOUT_ACLK_G3D for G3D's AXI
Cc: Chanwoo Choi
Signed-off-by: Anand Moon
---
arch/arm/boot/dts/exynos5420.dtsi | 57 +--
arch/arm/boot/dts/exynos5422-odroid-core.dtsi | 5 ++
2
This allows changing the VPLL output frequency through the g3d subsystem
clock tree leaf clocks.
Cc: Andrzej Hajda
Cc: Chanwoo Choi
Signed-off-by: Anand Moon
---
drivers/clk/samsung/clk-exynos5420.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Marian Mihailescu
A specific clock rate table is added for VPLL so it is possible
to set frequency of the VPLL output clock that used by the g3d clock.
Cc: Andrzej Hajda
Cc: Chanwoo Choi
Signed-off-by: Marian Mihailescu
Signed-off-by: Anand Moon
---
On 2018-11-22 17:04:19 [+0800], zhe...@windriver.com wrote:
> From: He Zhe
>
> kmemleak_lock, as a rwlock on RT, can possibly be held in atomic context and
> causes the follow BUG.
>
> BUG: scheduling while atomic: migration/15/132/0x0002
…
> Preemption disabled at:
> []
On 23-11-18, 14:41, Viresh Kumar wrote:
> On 22-11-18, 11:38, Viresh Kumar wrote:
> > So there are few complexities in the case where an OPP table points to
> > itself in
> > the required-opp field. I looked at solving it up in the opp core but that
> > gets
> > more and more messy.
> >
> > Now
Hi,
On 19/11/18 4:38 PM, Shawn Guo wrote:
> It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs.
>
> Signed-off-by: Shawn Guo
> ---
> drivers/phy/qualcomm/Kconfig | 10 +
>
On 21/11/2018 19:06, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.139 release.
> There are 59 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.
>
> Responses
On Thu, Nov 22, 2018 at 9:38 PM Alexey Dobriyan wrote:
>
> On Thu, Nov 22, 2018 at 09:29:52PM +0800, Yafang Shao wrote:
> > On Thu, Nov 22, 2018 at 7:40 PM Alexey Dobriyan wrote:
> > >
> > > On Wed, Nov 21, 2018 at 07:28:44PM -0800, Andrew Morton wrote:
> > > > On Mon, 19 Nov 2018 19:17:52 +0800
On November 23, 2018 1:27:02 AM PST, Julien Thierry
wrote:
>Hi,
>
>I made an attempt at implementing the
>user_access_begin()/user_access_end() macros along with the
>get/put_user_unsafe() for arm64 by toggling the status of PAN (more or
>less similar to x86's STAC/CTAC).
>
>With a small
Hi Chanwoo Choi,
On 11/23/18 12:45 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> On 2018년 11월 22일 19:40, Lukasz Luba wrote:
>> Hi Chanwoo Choi
>>
>> On 11/22/18 3:52 AM, Chanwoo Choi wrote:
>>> On 2018년 11월 22일 03:01, Lukasz Luba wrote:
The refactoring is needed for the new client in devfreq:
On 21/11/2018 19:06, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.83 release.
> There are 21 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.
>
> Responses
The interrupt handler contains a workaround for RX hang applicable
to Zynq and AT91 only. Subsequent versions do not need this
workaround. This workaround unecessarily reset RX whenever RX used
bit read is observed, which can be often under heavy traffic.Hence
introduce an errata field and a check
When the kernel is compiled with -ffunction-sections and perf uses the
kernel debuginfo, perf fails the very first symbol lookup and ends up with
an hex offset inside [kernel.vmlinux]. It's due to how perf loads the maps.
Indeed only .text gets loaded by map_groups__find() into al->map.
Hi Chanwoo Choi,
On 11/23/18 12:54 AM, Chanwoo Choi wrote:
> Hi Lukasz,
>
> I add one more comment about devfreq_resume_device().
>
> On 2018년 11월 22일 20:00, Lukasz Luba wrote:
>>
>>
>> On 11/22/18 3:58 AM, Chanwoo Choi wrote:
>>> On 2018년 11월 22일 03:01, Lukasz Luba wrote:
The patch adds
Hi Geert,
On 23 November 2018 09:41 Geert Uytterhoeven wrote:
> Subject: Re: [PATCH] pinctrl: rzn1: Fix check for used MDIO bus
> On Mon, Nov 19, 2018 at 5:18 PM Phil Edworthy wrote:
> > This fixes the check for unused mdio bus setting and the following
> > static checker warning:
> >
On 22-11-18, 13:36, Daniel Lezcano wrote:
> In the case of asymmetric SoC with the same micro-architecture, we
> have a group of CPUs with smaller OPPs than the other group. One
> example is the 96boards dragonboard 820c. There is no dmips/MHz
> difference between both groups, so no need to
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-4.20-rc4
with top-most commit 1d50088ca3956e5dcd2751a658e7869b9af10bb4
Merge branches 'pm-cpufreq' and 'pm-sleep'
on top of commit 9ff01193a20d391e8dbce4403dd5ef87c7eaaca6
Linux
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-4.20-rc4
with top-most commit 2bbb5fa37475d7aa5fa62f34db1623f3da2dfdfa
ACPI / platform: Add SMB0001 HID to forbidden_id_list
on top of commit 9ff01193a20d391e8dbce4403dd5ef87c7eaaca6
From: David Laight
> Sent: 23 November 2018 09:35
> From: Linus Torvalds
> > Sent: 22 November 2018 18:58
> ...
> > Oh, and I just noticed that on x86 we expressly use our old "safe and
> > sane" functions: see __inline_memcpy(), and its use in
> > __memcpy_{from,to}io().
> >
> > So the "falls
Introduce vendor prefix for whwave, Inc.
for SD3078 rtc device.
Signed-off-by: zoro
---
.../devicetree/bindings/vendor-prefixes.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
The sd3078 is a combination RTC and SRAM device with I2C interface.
Signed-off-by: zoro
---
MAINTAINERS |6 ++
drivers/rtc/Kconfig |9 ++
drivers/rtc/Makefile |1 +
drivers/rtc/rtc-sd3078.c | 232 ++
4 files changed,
The devicetree documentation for the SD3078 device tree
binding is added with a short example.
Signed-off-by: zoro
---
.../devicetree/bindings/rtc/rtc-sd3078.txt | 13 +
1 file changed, 13 insertions(+)
create mode 100644
On 23/11/18 09:57, h...@zytor.com wrote:
On November 23, 2018 1:27:02 AM PST, Julien Thierry
wrote:
Hi,
I made an attempt at implementing the
user_access_begin()/user_access_end() macros along with the
get/put_user_unsafe() for arm64 by toggling the status of PAN (more or
less similar to
A double pointer is used in map__find() where a single pointer is enough
because the function doesn't affect the rbtree and the rbtree is locked.
Signed-off-by: Eric Saint-Etienne
---
tools/perf/util/map.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
On Fri, 23 Nov 2018 09:42:55 +
"Sverdlin, Alexander (Nokia - DE/Ulm)"
wrote:
> Hello Tudor,
>
> On 22/11/2018 13:36, tudor.amba...@microchip.com wrote:
> > From: Tudor Ambarus
> >
> > Bug reported for the out-of-tree S25FS128S flash memory.
> >
> > BFPT table advertises all the erase
On 20/11/2018 12:44, Vignesh R wrote:
On 20/11/18 4:07 PM, Tero Kristo wrote:
On 20/11/2018 12:09, Vignesh R wrote:
On 19/11/18 12:49 PM, Tero Kristo wrote:
On 17/11/2018 18:05, Nishanth Menon wrote:
On 11:31-20181113, Vignesh R wrote:
The dt-bindings header for TI K3 AM6 SoCs define a set
tl;dr automatic bisection reports are enabled for mainline and stable
In case you're not already familiar with it, the kernelci.org project
is a community effort to build and test upstream kernel trees on a
variety of hardware platforms. Reports are mostly sent to the
kernel-build-reports
Hello Clément,
On Fri, Nov 23, 2018 at 10:31:18AM +0100, Clément Péron wrote:
> On Thu, 22 Nov 2018 at 21:05, Uwe Kleine-König
> wrote:
> > Related to this driver I have a set of questions: If the disable
> > callback completed, does the hardware still drive the pin? If yes, would
> > it be
On Fri, 23 Nov 2018 11:17:29 +0100
Boris Brezillon wrote:
> On Fri, 23 Nov 2018 09:42:55 +
> "Sverdlin, Alexander (Nokia - DE/Ulm)"
> wrote:
>
> > Hello Tudor,
> >
> > On 22/11/2018 13:36, tudor.amba...@microchip.com wrote:
> > > From: Tudor Ambarus
> > >
> > > Bug reported for the
Hi Greg,
Please find the pull request for 4.20 -rc below.
It includes tuning parameter fix in qcom-qusb2 PHY driver, dt-bindings fix
for phy-qcom-qmp and a fix for randconfig error in uniphier-pcie.
Consider merging this in the -rc cycle.
Thanks
Kishon
The following changes since commit
On Fri, 23 Nov 2018, Manfred Rudigier wrote:
> Acked-by: Manfred Rudigier
Thanks Manfred! Very appreciated!
Thomas
On 23/11/2018 11:04, Viresh Kumar wrote:
> On 22-11-18, 13:36, Daniel Lezcano wrote:
>> In the case of asymmetric SoC with the same micro-architecture, we
>> have a group of CPUs with smaller OPPs than the other group. One
>> example is the 96boards dragonboard 820c. There is no dmips/MHz
>>
Hi, Alexander,
On 11/23/2018 11:42 AM, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> Hello Tudor,
>
> On 22/11/2018 13:36, tudor.amba...@microchip.com wrote:
>> From: Tudor Ambarus
>>
>> Bug reported for the out-of-tree S25FS128S flash memory.
>>
>> BFPT table advertises all the erase types
From: Rafael J. Wysocki
The venerable menu governor does some thigns that are quite
questionable in my view.
First, it includes timer wakeups in the pattern detection data and
mixes them up with wakeups from other sources which in some cases
causes it to expect what essentially would be a timer
401 - 500 of 840 matches
Mail list logo
