On Thu, Dec 20, 2018 at 08:56:33AM +, Anson Huang wrote:
> Add i.MX8QXP system controller RTC support.
>
> Signed-off-by: Anson Huang
Different from arm32 dts patches, we use prefix 'arm64: ...' for arm64
ones. I fixed it up and applied the patch.
Shawn
On Thu, Dec 20, 2018 at 08:56:25AM +, Anson Huang wrote:
> This patch enables CONFIG_RTC_DRV_IMX_SC as module by default.
>
> Signed-off-by: Anson Huang
Applied, thanks.
On Sun, Jan 13, 2019 at 12:05:45PM +0100, Borislav Petkov wrote:
>On Sun, Jan 13, 2019 at 05:47:04PM +0800, Chao Fan wrote:
>> 'acpi_physical_address' could be define as u64 or u32.
>
>And when can acpi_physical_address be a u32?
>
According to the code, I saw:
#ifdef ACPI_ASL_COMPILER
#define
Hi all,
Here's a series of patches to add initial serdev support to n_gsm
TS 27.010 line discipline.
This allows handling vendor specific protocols on top of TS 27.010 and
allows creating simple serdev drivers where it makes sense. So far I've
tested it with droid 4 for it's modem to provide
We can make use of serdev drivers to do simple device drivers for
TS 27.010 chanels, and we can handle vendor specific protocols on top
of TS 27.010 with serdev drivers.
Serdev device drivers can be done for channel specific features, such
as GNSS framework and Alsa ASoC voice call audio mixer
In order to prepare for adding serdev driver support, let's constify
the use of u8 and unsigned char for n_gsm.
Note that gsm_control_modem() gsm_control_rls() read the data for tty
control characters and then call gsm_control_reply() that allocates a
new reply and copies the data.
Cc:
For supporting serdev drivers, we need to be able to configure n_gsm
from drivers. Let's prepare for that by adding copy_config() and
gsm_config() helper functions by moving the code around a bit.
Let's also unify the comments to keep checkpatch happy while at it.
Cc:
Hi all,
After merging the mali-dp tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from
drivers/gpu/drm/arm/display/komeda/komeda_framebuffer.c:11:
drivers/gpu/drm/arm/display/komeda/komeda_framebuffer.h:13:25: error: field
'base' has incomplete type
On Fri, Jan 11, 2019 at 05:57:30AM +, Anson Huang wrote:
> This patch adds cpuidle support for i.MX7ULP, 3 cpuidle
> states supported as below:
>
> 1. WFI, just ARM wfi;
> 2. WAIT mode, mapped to SoC's partial stop mode #3;
> 3. STOP mode, mapped to SoC's partial stop mode #1.
>
> In WAIT
Samuel Holland writes:
> Hello all,
>
> On 09/27/18 02:05, Christophe Leroy wrote:
> [..snip..]
>> diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
>> index 07d9dce7eda6..45b8eb4d8fe7 100644
>> --- a/arch/powerpc/Makefile
>> +++ b/arch/powerpc/Makefile
>> @@ -112,6 +112,9 @@
Hello,
this is RE the patch 8515b9edf7a0c9dcf1ad218ccc783700db217336 (Upstream commit
a9ad01bc759df79b0012f43ee52164391e31cd96) in 4.18.20.
I have an issue with UDF. I used to be able to create a UDF fs in a way that is
very similar to this:
`# mkudffs --label= -m dvd -b 512
On Sun, Jan 13, 2019 at 10:32 AM Olof Johansson wrote:
>
> Since we now build with -Wvla, any use of VLA throws a warning.
> Including this test, so... maybe we should just remove the test?
>
> lib/test_ubsan.c: In function 'test_ubsan_vla_bound_not_positive':
> lib/test_ubsan.c:48:2: warning:
Hi Liviu,
Commits
31849148cb41 ("drm/komeda: Add komeda_framebuffer")
b347a024e10b ("drm/komeda: Add komeda_format_caps for format handling")
274d16527e45 ("drm/komeda: Add DT parsing")
f20978344694 ("drm/komeda: Build komeda to be a platform module")
f8eff4b21a16 ("drm/arm: Delete
Geert Uytterhoeven writes:
> Below is the list of build error/warning regressions/improvements in
> v5.0-rc1[1] compared to v4.20[2].
>
> Summarized:
> - build errors: +12/-4
> - build warnings: +405/-350
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
kernel/cgroup/cgroup-v1.c
between commit:
61aa329d0762 ("cgroup: saner refcounting for cgroup_root")
from the vfs-fixes tree and commit:
b3678086951a ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
from the
Greg Kroah-Hartman writes:
> On Sat, Jan 12, 2019 at 10:35:59PM +0100, Christoph Biedl wrote:
>> Greg Kroah-Hartman wrote...
>>
>> > 4.20-stable review patch. If anyone has any objections, please let me
>> > know.
>> >
>> > --
>> >
>> > From: Greg Kroah-Hartman
>> >
>> > This
On Mon, Jan 14, 2019 at 10:29:02AM +1100, Dave Chinner wrote:
> Until you have images (and hence host page cache) shared between
> multiple guests. People will want to do this, because it means they
> only need a single set of pages in host memory for executable
> binaries rather than a set of
On Fri, Jan 11, 2019 at 02:45:04AM -0500, Pankaj Gupta wrote:
>
> >
> > On Wed, Jan 09, 2019 at 08:17:31PM +0530, Pankaj Gupta wrote:
> > > This patch series has implementation for "virtio pmem".
> > > "virtio pmem" is fake persistent memory(nvdimm) in guest
> > > which allows to bypass the
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
kernel/cgroup/cgroup-internal.h
between commit:
61aa329d0762 ("cgroup: saner refcounting for cgroup_root")
from the vfs-fixes tree and commit:
b3678086951a ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
from
Hi Sebastien,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v5.0-rc1 next-20190111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Mon, 14 Jan 2019, Pavel Machek wrote:
> That one really is Intel-specific (not even all x86s are affectd). Same
> for Meltdown.
At least for Meltdown, your claim is simply not correct.
--
Jiri Kosina
SUSE Labs
On Wed 2019-01-09 07:20:18, Lee Jones wrote:
> Good morning Linus,
>
> Please accept my apologies for the lateness.
I'd say that for 5.1, you are pretty early :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
Hi!
I just want to note that while these may not be high-priority, they
are still security holes to be fixed.
> > When writing the attached file to /dev/uhid, a NULL dereference occurs
> > in kernel. As I understand, the problem is not UHID-specific, but is
> > related to HID subsystem.
>
>
Hi!
> >>
> >> Signed-off-by: Andi Kleen
> >> Signed-off-by: Tim Chen
> >> ---
> >> Documentation/admin-guide/spectre.rst | 502
> >> ++
> >> 1 file changed, 502 insertions(+)
> >> create mode 100644 Documentation/admin-guide/spectre.rst
> >
> > I only saw
On Wed 2019-01-09 10:43:36, Keith Busch wrote:
> Add descriptions for memory class initiator performance access attributes.
>
> +What:/sys/devices/system/node/nodeX/classY/read_latency
> +Date:December 2018
> +Contact: Keith Busch
> +Description:
> +
So the merge window had somewhat unusual timing with the holidays, and
I was afraid that would affect stragglers in rc2, but honestly, that
doesn't seem to have happened much. rc2 looks pretty normal.
Were there some missing commits that missed the merge window? Yes. But
no more than usual.
Hi Sebastien,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v5.0-rc1 next-20190111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
The pull request you sent on Sun, 13 Jan 2019 10:48:25 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
> tags/armsoc-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/dbc3c09b819f2bd42460b148e55ac5a9d83aaeaf
Thank you!
--
Deet-doot-dot, I
Hi Vijay,
Sorry for providing an opinion so late, however:
On Sat, 12 Jan 2019, at 11:03, Vijay Khemka wrote:
> Joel,
> Please merge these patches as it is required by facebook platform.
>
> Regards
> -Vijay
>
> On 1/7/19, 11:25 AM, "Linux-aspeed on behalf of Vijay Khemka"
1) Fix regression in multi-SKB responses to RTM_GETADDR, from Arthur
Gautier.
2) Fix ipv6 frag parsing in openvswitch, from Yi-Hung Wei.
3) Unbounded recursion in ipv4 and ipv6 GUE tunnels, from Stefano
Brivio.
4) Use after free in hns driver, from Yonglong Liu.
5) icmp6_send() needs
Hi Douglas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robclark/msm-next]
[also build test ERROR on v5.0-rc1 next-20190111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Sun, Jan 13, 2019 at 08:43:07PM +0100, Christophe Leroy wrote:
> Le 13/01/2019 à 19:16, Jonathan Neuschäfer a écrit :
> > I just tested the whole series on my Wii (I didn't test any intermediate
> > steps). Without CONFIG_STRICT_KERNEL_RWX, it seems to work fine, but
> > with it, I get the
CC: OMAP list for good measure
On 1/13/19 2:49 PM, David Lechner wrote:
This reverts commit b682cffa3ac6d9d9e16e9b413c45caee3b391fab.
That commit breaks displays using tinydrm drivers, such as ili9225.
It causes corruption in the image that is displayed (it looks like only
1/2 of the
On Thu, 10 Jan 2019 13:02:28 +0100
Johan Hovold wrote:
> On Sun, Dec 09, 2018 at 08:51:46PM +0100, Andreas Kemnade wrote:
> > The api forbids writing data there otherwise. Prepare for the
> > serdev_open()/close() being a part of runtime pm.
> >
> > Signed-off-by: Andreas Kemnade
> > ---
> >
This reverts commit b682cffa3ac6d9d9e16e9b413c45caee3b391fab.
That commit breaks displays using tinydrm drivers, such as ili9225.
It causes corruption in the image that is displayed (it looks like only
1/2 of the framebuffer data is sent, the other half of the display
remains blank.)
The
Add maintainers and reviewers for VKMS driver
Signed-off-by: Rodrigo Siqueira
---
Changes in v2:
- Insert the section in alphabetical order
Resend:
- Update patch due to changes in MAINTAINER file
MAINTAINERS | 10 ++
1 file changed, 10 insertions(+)
diff --git a/MAINTAINERS
--
Hi friend
I am a banker in B.O.A BANK. I want to transfer an abandoned sum of
USD27.5Million to your Bank account. 40/percent will be your share.
Further details of the transaction shall be forward to you as soon as I
receive your response indicating your interest in handling the
Hi,
I resend this patch for CI via “intel-...@lists.freedesktop.org” as
Daniel suggested, and I got a feedback that reported an issue as can be
seen here:
https://patchwork.freedesktop.org/series/51147/
After a careful analysis of what happened, I concluded that the problem
is related to the
Since we now build with -Wvla, any use of VLA throws a warning.
Including this test, so... maybe we should just remove the test?
lib/test_ubsan.c: In function 'test_ubsan_vla_bound_not_positive':
lib/test_ubsan.c:48:2: warning: ISO C90 forbids variable length array 'buf'
[-Wvla]
For the
On Thu, Jan 10, 2019 at 3:15 AM Anders Roxell wrote:
>
> The warning got introduced by commit 930507c18304 ("arm64: add basic
> Kconfig symbols for i.MX8"). Since it got enabled for arm64. The warning
> haven't been seen before since size_t was 'unsigned int' when built on
> arm32.
>
>
Am Sonntag, 13. Januar 2019, 09:47:43 CET schrieb Julia Lawall:
> The device node iterators perform an of_node_get on each iteration, so a
> jump out of the loop requires an of_node_put.
>
> The semantic patch that fixes this problem is as follows
> (http://coccinelle.lip6.fr):
>
> //
> @@
>
The Kconfig for this option is currently:
config HTC_I2CPLD
bool "HTC I2C PLD chip support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doubt it is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_AAT2870_CORE
drivers/mfd/Kconfig:bool "AnalogicTech AAT2870"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_TPS65910
drivers/mfd/Kconfig-bool "TI TPS65910 Power Management chip"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM831X
drivers/mfd/Kconfig:bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading the driver
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM831X_I2C
drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with I2C"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM831X_SPI
drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM831x/2x PMICs with SPI"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_TPS65090
drivers/mfd/Kconfig:bool "TI TPS65090 Power Management chips"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_DB8500_PRCMU
drivers/mfd/Kconfig:bool "ST-Ericsson DB8500 Power Reset Control Management
Unit"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_RC5T583
drivers/mfd/Kconfig:bool "Ricoh RC5T583 Power Management system device"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_STA2X11
drivers/mfd/Kconfig:bool "STMicroelectronics STA2X11"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM8350_I2C
drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8350 with I2C"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_TPS80031
drivers/mfd/Kconfig:bool "TI TPS80031/TPS80032 Power Management chips"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM8400
drivers/mfd/Kconfig:bool "Wolfson Microelectronics WM8400"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned,
The Makefile/Kconfig currently controlling compilation of this code is:
drivers/mfd/Makefile:obj-$(CONFIG_PMIC_ADP5520) += adp5520.o
drivers/mfd/Kconfig:config PMIC_ADP5520
drivers/mfd/Kconfig:bool "Analog Devices ADP5520/01 MFD PMIC Core Support"
...meaning that it currently is not being
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_SYSCON
drivers/mfd/Kconfig:bool "System Controller Register R/W Based on Regmap"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_WM8350
drivers/mfd/Kconfig:bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular infrastructure use, so that
when reading the driver
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_AS3711
drivers/mfd/Kconfig:bool "AMS AS3711"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading
[v4 --> v5: add more acks, re-do build tests on newest linux-next after
the 5.0 merge window closed.]
[v3 --> v4: delete now unused exit fcn from wm835x core; add more acks
now all in chrono order, re-test.]
[v2 --> v3: drop diasemi commits as they will be modularized; delete
now unused exit
The Kconfig currently controlling compilation of this code is:
drivers/mfd/Kconfig:config MFD_MAX8925
drivers/mfd/Kconfig:bool "Maxim Semiconductor MAX8925 PMIC Support"
...meaning that it currently is not being built as a module by anyone.
Lets remove the couple traces of modular
There is possibility, that when probing driver, regulators are not yet
initialized. In this case we should return EPROBE_DEFER and wait till
they're initialized, since they're required currently for cpufreq driver
to work. Also move regulator initialization code at beginning of probe,
so we can
On niedziela, 13 stycznia 2019 14:16:24 CET Krzysztof Kozlowski wrote:
> On Fri, Jan 11, 2019 at 08:42:44PM +0100, Paweł Chmiel wrote:
> > There is possibility, that when probing driver, regulators are not yet
> > initialized. In this case we should return EPROBE_DEFER and wait till
> > they're
On Fri 11-01-19 14:54:32, Shakeel Butt wrote:
> Hi Johannes,
>
> On Fri, Jan 11, 2019 at 12:59 PM Johannes Weiner wrote:
> >
> > Hi Shakeel,
> >
> > On Thu, Jan 10, 2019 at 09:44:32AM -0800, Shakeel Butt wrote:
> > > If a memcg is over high limit, memory reclaim is scheduled to run on
> > >
Le 13/01/2019 à 19:16, Jonathan Neuschäfer a écrit :
On Thu, Jan 10, 2019 at 03:11:38PM +, Christophe Leroy wrote:
The purpose of this serie is to:
- use BATs with STRICT_KERNEL_RWX on book3s (See patch 12 for details.)
- use LTLBs with STRICT_KERNEL_RWX on 8xx (See patch 14 for a few
Hi Linus,
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
Override the dr_mode from "host" to "peripheral" for dwc2
usb_phy0->usb0 initialization of OTG Micro-B type.
Changes fix the below warning for phy poweron failed --> -22
This fix the initialization of c904.usb phy.
[1.639706] phy phy-c1108800.phy.0: USB ID detect failed!
[1.643850]
Add missing vbus-supply link to phy controller for usb_phy0
and usb_phy1 nodes, this changes fixed the power issue
on usb ports usb, changes help fix usb reset warning.
[ 821.991470] usb 1-1.2: reset high-speed USB device number 3 using dwc2
[ 825.243385] usb 1-1.2: reset high-speed USB device
On Thu, Jan 10, 2019 at 03:11:38PM +, Christophe Leroy wrote:
> The purpose of this serie is to:
> - use BATs with STRICT_KERNEL_RWX on book3s (See patch 12 for details.)
> - use LTLBs with STRICT_KERNEL_RWX on 8xx (See patch 14 for a few details.)
Hi,
I just tested the whole series on my
The pull request you sent on Sun, 13 Jan 2019 11:23:42 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
> tags/staging-5.0-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f7c1038bc7597af5d6809c5b3e0352627cef5c07
Thank you!
--
The pull request you sent on Sun, 13 Jan 2019 11:24:07 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
> driver-core-5.0-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/72d657dd2115804b93bde4b77e426cc2de70eebf
Thank you!
--
The pull request you sent on Sun, 13 Jan 2019 11:22:52 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git tags/usb-5.0-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1dd8a3f6c619723ab442d6a27247d2f2153f3b11
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 13 Jan 2019 17:39:38 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.0-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6b529fb0a3eabf9c4cc3e94c11477250379ce6d8
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 13 Jan 2019 11:23:16 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.0-rc2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/437e878a6c48028273e4b06be7e09d235b189e62
Thank you!
--
Deet-doot-dot, I am a
On Sat 12-01-19 19:52:50, Tetsuo Handa wrote:
> On 2019/01/12 1:45, Michal Hocko wrote:
> >>> Anyway, could you update your patch and abstract
> >>> if (unlikely(tsk_is_oom_victim(current) ||
> >>>fatal_signal_pending(current) ||
> >>>current->flags &
On Sat 12-01-19 15:56:38, Anshuman Khandual wrote:
> All architectures have been defining their own PGALLOC_GFP as (GFP_KERNEL |
> __GFP_ZERO) and using it for allocating page table pages. This causes some
> code duplication which can be easily avoided. GFP_KERNEL allocated and
> cleared out pages
From: Andy Shevchenko Sent: Thursday,
January 10, 2019 6:26 AM
>
> There are new types and helpers that are supposed to be used in new code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> Cc: "K. Y. Srinivasan"
> Cc: Haiyang Zhang
> Cc:
On Sun, 2019-01-13 at 08:56 +0100, Stephan Müller wrote:
> The question may arise why to plug the KDFs into RNGs. The answer is
> quite simple: KDFs are a form of random number generator. In that
> they take some input for initialization (aka seed, salt, key,
> personalization string). Then they
On Thu, Jan 10, 2019 at 11:48:13PM +, Jason Gunthorpe wrote:
> +The Linux kernel bool type is an alias for the C99 _Bool type. bool values
> can
> +only evaluate to 0 or 1, and implicit or explicit conversion to bool
> +automatically converts the value to true or false. When using bool types
Hi,
please pull the following branch to get:
- 2 regression fixes in clone/dedupe ioctls, the generic check callback
needs to lock extents properly and wait for io to avoid problems with
writeback and relocation
- fix deadlock when using free space tree due to block group creation
- a
On Thu, 2019-01-10 at 18:59 +0200, Sakari Ailus wrote:
> Hi Lubomir,
>
> On Wed, Nov 28, 2018 at 12:29:33PM +0100, Lubomir Rintel wrote:
> > On Thu, 2018-11-22 at 14:21 +0200, Sakari Ailus wrote:
> > > Hi Lubomir,
> > >
> > > On Tue, Nov 20, 2018 at 11:03:08AM +0100, Lubomir Rintel wrote:
> > >
Hi Vesa,
On 1/9/19 8:11 AM, Vesa Jääskeläinen wrote:
Hi Pavel,
On 09/01/2019 0.59, Pavel Machek wrote:
Hi!
Grab yourself an RGB LED and play with it; you'll see what the
problems are. It is hard to explain colors over email...
Video [0] gives some overview of lp5024 capabilities.
I don't
Hi Vesa,
On 1/9/19 7:46 AM, Vesa Jääskeläinen wrote:
Hi Jacek,
On 07/01/2019 23.13, Jacek Anaszewski wrote:
Hi Vesa,
On 1/5/19 1:39 AM, Vesa Jääskeläinen wrote:
Hi Jacek,
On 04/01/2019 23.37, Jacek Anaszewski wrote:
But, aside from that hypothetic issue, we need a solution for
This typo inverted the meaning of the comment, but the rest of the
comment and the code reveal that the regulator in question needs to be
on at all times.
Signed-off-by: Jonathan Neuschäfer
---
arch/arm64/boot/dts/allwinner/sun50i-a64-teres-i.dts | 2 +-
1 file changed, 1 insertion(+), 1
On Sun, Jan 13, 2019 at 04:41:52PM +0100, Stefan Agner wrote:
> Hi,
>
> On 12.01.2019 02:01, Jeremy Fertic wrote:
> > I'm having a problem with the ftrace function graph tracer on a 32 bit arm
> > board (orangepi pc). A bisect points to the following commit:
> >
> > f9b58e8c7d03 ("ARM: 8800/1:
On Sun, Jan 13, 2019 at 03:15:59PM +0200, Joel Nider wrote:
> -A way to get rid of that is to use a different version than the one shipped
> -on your distributions. In order to do that, it is recommended to install
> +A way to avoid that is to use a different version than the one shipped
> +on
On 2019-01-11 00:48, Jason Gunthorpe wrote:
There has been some confusion since checkpatch started warning about
bool
use in structures, and people have been avoiding using it.
Many people feel there is still a legitimate place for bool in
structures,
so provide some guidance on bool usage
spmi-gpio did not have any irqchip support so consumers of this in
device tree would need to call gpio[d]_to_irq() in order to get the
proper IRQ on the underlying PMIC. IRQ chips in device tree should
be usable from the start without the consumer having to make an
additional call to get the
Convert the spmi-pmic-arb IRQ code to use the version 2 IRQ interface
in order to support hierarchical IRQ chips. This is necessary so that
spmi-gpio can be setup as a hierarchical IRQ chip with pmic-arb as the
parent. IRQ chips in device tree should be usable from the start without
the consumer
Add support for the PMI8998 GPIO variant to the Qualcomm PMIC GPIO
binding document.
Signed-off-by: Brian Masney
---
This is a new patch introduced in V4.
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
This adds the two new functions gpiochip_irq_domain_activate and
gpiochip_irq_domain_deactivate that can be used as the activate and
deactivate functions in the struct irq_domain_ops. This is for
situations where only gpiochip_{lock,unlock}_as_irq needs to be called.
SPMI and SSBI GPIO are two
Check to see if the hwirq is already associated with another virq on
this IRQ domain. If so, then disassociate it before associating the
hwirq with the new virq.
This is a temporary hack that is needed in order to not break git
bisect for existing boards. The next patch in this series converts
The probing of this driver calls platform_irq_count, which will
setup all of the IRQs that are configured in device tree. In
preparation for converting this driver to be a hierarchical IRQ
chip, hardcode the IRQ count based on the hardware type so that all
the IRQs are not configured immediately
Now that spmi-gpio is a proper hierarchical IRQ chip, and all in-tree
users of device tree have been updated, we can now drop the hack that
was introduced to disassociate the old Linux virq if a hwirq mapping
already exists. That patch was introduced to not break git bisect for
any existing
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it.
This change was not tested on any hardware but the same change was
tested on qcom-pm8941.dtsi using a LG Nexus 5 (hammerhead) phone with
no issues.
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it.
This change was not tested on any hardware but the same change was
tested on qcom-pm8941.dtsi using a LG Nexus 5 (hammerhead) phone with
no issues.
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it. Code was tested on the LG Nexus 5 (hammerhead) phone.
Signed-off-by: Brian Masney
Reviewed-by: Stephen Boyd
---
Changes since v3:
- None
Changes
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it.
This change was not tested on any hardware but the same change was
tested on qcom-pm8941.dtsi using a LG Nexus 5 (hammerhead) phone with
no issues.
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it.
This change was not tested on any hardware but the same change was
tested on qcom-pm8941.dtsi using a LG Nexus 5 (hammerhead) phone with
no issues.
Add interrupt controller properties now that spmi-gpio is a proper
hierarchical IRQ chip. The interrupts property is no longer needed so
remove it.
This change was not tested on any hardware but the same change was
tested on qcom-pm8941.dtsi using a LG Nexus 5 (hammerhead) phone with
no issues.
Add support for qcom,pm8005-gpio, qcom,pm8998-gpio, and
qcom,pmi8998-gpio. These three variants are already in use in some
arm64 dtsi files. Those boards work since the generic binding
qcom,spmi-gpio is also specified.
Signed-off-by: Brian Masney
---
This is a new patch introduced in V4.
101 - 200 of 260 matches
Mail list logo
