The simple_write_to_buffer() returns ssize_t type value,
which is either positive or negative.
However 'res' is declared as size_t(unsigned int)
which contains non-negative type.
So 'res < 0' statement is always false,
this cannot execute execptional-case handling.
To prevent this case,
update
> Am 11.09.2019 um 07:13 schrieb H. Nikolaus Schaller :
>
> Hi Adam,
>
>> Am 11.09.2019 um 02:41 schrieb Adam Ford :
>
>
> The error message looks as if we have to enable multi_regulator.
>
That will enable both vdd and vbb regulators from what I can tell in the
* Mike Travis wrote:
> @@ -1596,7 +1687,7 @@ static void __init uv_system_init_hub(vo
> uv_nmi_setup();
> uv_cpu_init();
> uv_scir_register_cpu_notifier();
> - proc_mkdir("sgi_uv", NULL);
> + uv_setup_proc_files(0);
This slipped through previously: platform drivers
On Mon, Aug 19, 2019 at 08:13:01PM -0700, Andrey Smirnov wrote:
> LPUART driver does not support specifying "rs485-rts-delay"
> property. Drop it.
>
> Signed-off-by: Andrey Smirnov
> Cc: Shawn Guo
> Cc: Chris Healy
> Cc: Fabio Estevam
> Cc: linux-arm-ker...@lists.infradead.org
> Cc:
* Mike Travis wrote:
> +/* Initialize UV hubless systems */
> +static __init int uv_system_init_hubless(void)
> +{
> + int rc;
> +
> + /* Setup PCH NMI handler */
> + uv_nmi_setup_hubless();
> +
> + /* Init kernel/BIOS interface */
> + rc = uv_bios_init();
> +
> +
Hi,
Richard Cochran writes:
> On Mon, Sep 09, 2019 at 10:59:39AM +0300, Felipe Balbi wrote:
>
>> case PTP_PEROUT_REQUEST:
>> +case PTP_PEROUT_REQUEST2:
>
> ...
>
>> +if (((req.perout.flags & ~PTP_PEROUT_VALID_FLAGS) ||
>> +req.perout.rsv[0] ||
The current version of the IOCTL have a small problem which prevents us
from extending the API by making use of reserved fields. In these new
IOCTLs, we are now making sure that flags and rsv fields are zero which
will allow us to extend the API in the future.
Reviewed-by: Richard Cochran
Some controllers allow for a one-shot output pulse, in contrast to
periodic output. Now that we have extensible versions of our IOCTLs, we
can finally make use of the 'flags' field to pass a bit telling driver
that if we want one-shot pulse output.
Signed-off-by: Felipe Balbi
---
Changes since
On 2019/9/11 13:33, Michal Hocko wrote:
> On Tue 10-09-19 14:53:39, Michal Hocko wrote:
>> On Tue 10-09-19 20:47:40, Yunsheng Lin wrote:
>>> On 2019/9/10 19:12, Greg KH wrote:
On Tue, Sep 10, 2019 at 01:04:51PM +0200, Michal Hocko wrote:
> On Tue 10-09-19 18:58:05, Yunsheng Lin wrote:
I found another panic ...
This testcase is testing the corner case where hugepage migration fails
by allocation failure on destination numa node which is caused by the
condition that all remaining free hugetlb are reserved.
[ 2610.711713] ===> testcase
strcpy was used multiple times in strcpy to write into dev->name.
I replaced them with strscpy.
Signed-off-by: Sandro Volery
---
drivers/staging/octeon/ethernet.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/octeon/ethernet.c
On Wed, Aug 21, 2019 at 10:37:42PM -0400, Anson Huang wrote:
> Select CONFIG_IMX7ULP_WDT by default to support i.MX7ULP watchdog.
>
> Signed-off-by: Anson Huang
Patch #4 and #5 look good to me, and I will pick them up once the first
3 get applied by Guenter.
Shawn
、>
> Caution: EXT Email
>
> On Fri, Sep 6, 2019 at 11:03 AM Biwen Li wrote:
> >
> > From: Chuanhua Han
> >
> > Enable NXP i2c controller to boot with ACPI
> >
>
> Thanks, the code looks good to me,
> Reviewed-by: Andy Shevchenko
>
> though...
>
> > Signed-off-by: Meenakshi Aggarwal
> >
Hi rafael, wolfram
Any comments about this?
>
> Enable NXP i2c controller to boot with ACPI
>
> Signed-off-by: Meenakshi Aggarwal
> Signed-off-by: Udit Kumar
> Signed-off-by: Chuanhua Han
> Signed-off-by: Biwen Li
> ---
> Change in v2:
> - Simplify code
> - Adjust header
Hi Daniel,
Are any other patches required prior to this series ? I have tried to
apply it on later powerpc/merge branch without success:
[root@localhost linux-powerpc]# git am
/root/Downloads/kasan-support-backing-vmalloc-space-with-real-shadow-memory\(1\).patch
Applying: kasan: support
On Tue, 10 Sep 2019 at 17:52, Maciej Falkowski wrote:
>
> Convert Samsung Exynos IOMMU H/W, System Memory Management Unit
> to newer dt-schema format.
>
> Update clock description.
>
> Signed-off-by: Maciej Falkowski
> Signed-off-by: Andrzej Hajda
> ---
> Hi Krzysztof,
>
> Thank you for
Hi Shengjiu,
Your mail is dated in the future, its time is 16:42 (GMT+2) whereas it
is still the morning.
Please fix your clock or timezone for future mails.
Thanks
Christophe
Le 11/09/2019 à 16:42, Shengjiu Wang a écrit :
Add the DT binding documentation for NXP MQS driver
Signed-off-by:
On Tue, Aug 27, 2019 at 09:16:39PM +0300, Vladimir Oltean wrote:
> On Tue, 27 Aug 2019 at 21:13, Mark Brown wrote:
> >
> > On Tue, Aug 27, 2019 at 09:06:14PM +0300, Vladimir Oltean wrote:
> > > On Tue, 27 Aug 2019 at 21:05, Mark Brown wrote:
> > > > On Mon, Aug 26, 2019 at 04:10:51PM +0300,
On 2019-09-11 08:22, Naoya Horiguchi wrote:
I found another panic ...
Hi Naoya,
Thanks for giving it a try. Are these testcase public?
I will definetely take a look and try to solve these cases.
Thanks!
This testcase is testing the corner case where hugepage migration fails
by allocation
From: Eugen Hristev
The PLL input range needs to be able to allow 24 Mhz crystal as input
Update the range accordingly in plla characteristics struct
Signed-off-by: Eugen Hristev
---
drivers/clk/at91/sama5d2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Boris Krasnovskiy
When removing the ohci-at91 module, the fact of not running complete shutdown
of all the ports was keeping additional analog cells consuming power for no
reason.
Doing Reset (OHCI_HCR) to HcCommandStatus register is the way to go, but using
the OHCI controller shutdown
Following a set of experiments we found areas of improvement for OHCI power
consumption (and associated USB analog cells).
This enhances the shutdown of residual power consumption in case of Linux
suspend/resume and removal of the driver (when compiled as a module).
Best regards,
Nicolas
Boris
From: Boris Krasnovskiy
There is a clock enable counter run away problem in resume ohci_at91. Code
enables clock that was never disabled in case of non wakeup interface. That
would make clock unstoppable in future.
Use proper alternative to start clocks only if they were stopped before.
In order to completely remove marginal power consumption in PM suspend,
we need to let the controller settle down before being stopped.
In ohci_hcd_at91_drv_suspend() function, one additional delay is needed before
to stop the clocks.
Reported-by: Boris Krasnovskiy
Signed-off-by: Nicolas Ferre
On Fri, Aug 23, 2019 at 12:37:30AM +, Fancy Fang wrote:
> According to the IMX7ULP reference manual, the mipi pll
> clock comes from the MIPI PHY PLL output. So it should
> not be defined as a fixed clock. So remove this clock
> node and all the references to it.
>
> Signed-off-by: Fancy Fang
On Tue 10-09-19 22:27:53, Nitin Gupta wrote:
[...]
> > On Tue 10-09-19 13:07:32, Nitin Gupta wrote:
> > > For some applications we need to allocate almost all memory as
> > > hugepages.
> > > However, on a running system, higher order allocations can fail if the
> > > memory is fragmented. Linux
On Fri, Aug 23, 2019 at 12:37:35AM +, Fancy Fang wrote:
> The mipi pll clock comes from the MIPI PHY PLL output, so
> it should not be a fixed clock.
>
> MIPI PHY PLL is in the MIPI DSI space, and it is used as
> the bit clock for transferring the pixel data out and its
> output clock is
On Wed 11-09-19 14:15:51, Yunsheng Lin wrote:
> On 2019/9/11 13:33, Michal Hocko wrote:
> > On Tue 10-09-19 14:53:39, Michal Hocko wrote:
> >> On Tue 10-09-19 20:47:40, Yunsheng Lin wrote:
> >>> On 2019/9/10 19:12, Greg KH wrote:
> On Tue, Sep 10, 2019 at 01:04:51PM +0200, Michal Hocko wrote:
> Am 11.09.2019 um 08:03 schrieb H. Nikolaus Schaller :
>
>
>> Am 11.09.2019 um 07:13 schrieb H. Nikolaus Schaller :
>>
>> Hi Adam,
>>
>>> Am 11.09.2019 um 02:41 schrieb Adam Ford :
>>
>>
>> The error message looks as if we have to enable multi_regulator.
>>
>
> That will
On Wed, Sep 11, 2019 at 8:34 AM Shawn Guo wrote:
> On Tue, Aug 27, 2019 at 09:16:39PM +0300, Vladimir Oltean wrote:
> > On Tue, 27 Aug 2019 at 21:13, Mark Brown wrote:
> > > On Tue, Aug 27, 2019 at 09:06:14PM +0300, Vladimir Oltean wrote:
> > > > On Tue, 27 Aug 2019 at 21:05, Mark Brown wrote:
On Mon, Aug 26, 2019 at 12:58:28PM +0300, Ilie Halip wrote:
> A previous commit removed __init from weim_probe(), but this attribute is
> still present for other functions called from it. Thus, these warnings
> are triggered:
> WARNING: Section mismatch in reference from the function
On 11/09/2019 at 08:39, Eugen Hristev - M18282 wrote:
> From: Eugen Hristev
>
> The PLL input range needs to be able to allow 24 Mhz crystal as input
> Update the range accordingly in plla characteristics struct
>
> Signed-off-by: Eugen Hristev
Acked-by: Nicolas Ferre
Thanks Eugen!
Best
From: Christoph Fink
Signed-off-by: Christoph Fink
---
drivers/mtd/spi-nor/spi-nor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index 8cc4b04..7fd52fa 100644
--- a/drivers/mtd/spi-nor/spi-nor.c
+++
Hi,
I would like to know if something extra needs to be done other than copying
compressed kernel image, when making tar package for riscv architecture. Please
see the attached patch.
--
Thanks and Regards,
Aurabindo Jayamohanan
From 86feb93c62daa61314df0bbe1a11272c23b1eadb Mon Sep 17
v3:
- check fatal signals in __get_user_page_locked() [Linus]
- add r-bs
v2:
- resent previous version, rebase only
This series is split out of userfaultfd-wp series to only cover the
general page fault changes, since it seems to make sense itself.
Basically it does two things:
(a) Allows
Although there're tons of arch-specific page fault handlers, most of
them are still sharing the same initial value of the page fault flags.
Say, merely all of the page fault handlers would allow the fault to be
retried, and they also allow the fault to respond to SIGKILL.
Let's define a default
The idea comes from a discussion between Linus and Andrea [1].
Before this patch we only allow a page fault to retry once. We
achieved this by clearing the FAULT_FLAG_ALLOW_RETRY flag when doing
handle_mm_fault() the second time. This was majorly used to avoid
unexpected starvation of the
This is the gup counterpart of the change that allows the
VM_FAULT_RETRY to happen for more than once. One thing to mention is
that we must check the fatal signal here before retry because the GUP
can be interrupted by that, otherwise we can loop forever.
Signed-off-by: Peter Xu
---
mm/gup.c
There's plenty of places around __get_user_pages() that has a parameter
"nonblocking" which does not really mean that "it won't block" (because
it can really block) but instead it shows whether the mmap_sem is
released by up_read() during the page fault handling mostly when
VM_FAULT_RETRY is
handle_userfaultfd() is currently the only one place in the kernel
page fault procedures that can respond to non-fatal userspace signals.
It was trying to detect such an allowance by checking against USER &
KILLABLE flags, which was "un-official".
In this patch, we introduced a new flag
The idea comes from the upstream discussion between Linus and Andrea:
https://lkml.org/lkml/2017/10/30/560
A summary to the issue: there was a special path in handle_userfault()
in the past that we'll return a VM_FAULT_NOPAGE when we detected
non-fatal signals when waiting for userfault
The idea comes from the upstream discussion between Linus and Andrea:
https://lkml.org/lkml/2017/10/30/560
A summary to the issue: there was a special path in handle_userfault()
in the past that we'll return a VM_FAULT_NOPAGE when we detected
non-fatal signals when waiting for userfault
Changes since v2:
- Addressed Stephen's review comment
- Moved the dt-bindings to yaml (This throws up some new warnings in various
QCOM
devicetrees. I'll send out a separate series to fix them up)
- Collected reviews and acks
- Added the dt-bindings to MAINTAINERS
Changes since v1:
- Collected
There are two fields - id and hw_id - to track what sensor an action was
to performed on. This was because the sensors connected to a TSENS IP
might not be contiguous i.e. 1, 2, 4, 5 with 3 being skipped.
This causes confusion in the code which uses hw_id sometimes and id
other times
msm8974 has 11 sensors connected to a single TSENS IP. Define a thermal
zone for each of those sensors to expose the temperature of each zone.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
Reviewed-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 90
msm8916 uses sensors 0, 1, 2, 4 and 5. Sensor 3 is NOT used. Fixup the
device tree so that the correct sensor ID is used and as a result we can
actually check the temperature for the cpu2_3 sensor.
Signed-off-by: Amit Kucheria
Reviewed-by: Daniel Lezcano
Reviewed-by: Stephen Boyd
---
Move platform_set_drvdata up to avoid an extra 'if (ret)' check after
the call to tsens_register.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 60 ++-
1 file changed, 32 insertions(+), 28 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Document interrupt support in the tsens driver by converting over to a
YAML schema.
Suggested-by: Stephen Boyd
Signed-off-by: Amit Kucheria
---
.../bindings/thermal/qcom-tsens.txt | 55 --
.../bindings/thermal/qcom-tsens.yaml | 174 ++
MAINTAINERS
Dump some basic version info and sensor details into debugfs. Example
from qcs404 below:
--(/sys/kernel/debug) $ ls tsens/
4a9000.thermal-sensor version
--(/sys/kernel/debug) $ cat tsens/version
1.4.0
--(/sys/kernel/debug) $ cat tsens/4a9000.thermal-sensor/sensors
max: 11
num: 10
id
Printing the function name when enabling debugging makes logs easier to
read.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens-common.c | 8
drivers/thermal/qcom/tsens.c| 6 +++---
2 files changed, 7
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 88 +++-
1 file changed, 46 insertions(+), 42 deletions(-)
diff --git
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 42 +++-
1 file changed, 22 insertions(+), 20 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 82 ++-
1 file changed, 42 insertions(+), 40 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 36 +++--
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
Hide the details of how to convert values read from TSENS HW to mCelsius
behind a function. All versions of the IP can be supported as a result.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens-common.c | 50 +
1 file changed, 36 insertions(+), 14
Depending on the IP version, TSENS supports upper, lower and critical
threshold interrupts. We only add support for upper and lower threshold
interrupts for now.
TSENSv2 has an irq [status|clear|mask] bit tuple for each sensor while
earlier versions only have a single bit per sensor to denote
> Subject: Re: [PATCH] dt-bindings: arm: Convert Realtek board/soc bindings to
> json-schema
>
> On Thu, Sep 5, 2019 at 9:19 AM wrote:
> >
> > From: "james.tai"
> >
> > Convert Realtek SoC bindings to DT schema format using json-schema.
> >
> > Signed-off-by: james.tai
> > ---
> >
From: Ben Chuang
The patches modify internal clock setup to match SD Host Controller
Simplified Specifications 4.20 and support Genesys Logic GL9750/GL9755
chipsets.
v9:
- refine gli_set_9750_rx_inv()
- modify comments in sdhci_gli_voltage_switch()
v8:
refine codes in sdhci-gli-pci.c
-
From: Ben Chuang
According to section 3.2.1 internal clock setup in SD Host Controller
Simplified Specifications 4.20, the timeout of loop for checking
internal clock stable is defined as 150ms.
Signed-off-by: Ben Chuang
Co-developed-by: Michael K Johnson
Signed-off-by: Michael K Johnson
On Wed, Sep 11, 2019 at 08:35:26AM +0200, osalva...@suse.de wrote:
> On 2019-09-11 08:22, Naoya Horiguchi wrote:
> > I found another panic ...
>
> Hi Naoya,
>
> Thanks for giving it a try. Are these testcase public?
> I will definetely take a look and try to solve these cases.
It's available on
From: Ben Chuang
The GL9750 and GL9755 chipsets, and possibly others, require PLL Enable
setup as part of the internal clock setup as described in 3.2.1 Internal
Clock Setup Sequence of SD Host Controller Simplified Specification
Version 4.20.
Signed-off-by: Ben Chuang
Co-developed-by: Michael
From: Ben Chuang
Add the Genesys Logic, Inc. vendor ID to pci_ids.h.
Signed-off-by: Ben Chuang
Co-developed-by: Michael K Johnson
Signed-off-by: Michael K Johnson
Acked-by: Adrian Hunter
---
include/linux/pci_ids.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
Hi Andreas,
On Thu, Aug 15, 2019 at 12:37 AM Andreas Schwab wrote:
> On Aug 14 2019, Palmer Dabbelt wrote:
> > On Wed, 14 Aug 2019 13:32:50 PDT (-0700), Paul Walmsley wrote:
> >> On Wed, 14 Aug 2019, Vincent Chen wrote:
> >>> Make the __fstate_clean() function correctly set the
> >>> state of
From: Ben Chuang
Export sdhci_abort_tuning() function symbols which are used by other SD Host
controller driver modules.
Signed-off-by: Ben Chuang
Co-developed-by: Michael K Johnson
Signed-off-by: Michael K Johnson
Acked-by: Adrian Hunter
---
drivers/mmc/host/sdhci.c | 3 ++-
From: Ben Chuang
Add support for the GL9750 and GL9755 chipsets.
Enable v4 mode and wait 5ms after set 1.8V signal enable for GL9750/
GL9755. Fix the value of SDHCI_MAX_CURRENT register and use the vendor
tuning flow for GL9750.
Co-developed-by: Michael K Johnson
Signed-off-by: Michael K
On 2019/9/11 14:49, Michal Hocko wrote:
> On Wed 11-09-19 14:15:51, Yunsheng Lin wrote:
>> On 2019/9/11 13:33, Michal Hocko wrote:
>>> On Tue 10-09-19 14:53:39, Michal Hocko wrote:
On Tue 10-09-19 20:47:40, Yunsheng Lin wrote:
> On 2019/9/10 19:12, Greg KH wrote:
>> On Tue, Sep 10,
On Wed, Sep 11, 2019 at 12:33:06AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> fd3f7275826f ("software node: Initialize the return value in
> software_node_find_by_name()")
>
> Fixes tag
>
> Fixes: 1666faedb567 ("software node: Add
> software_node_get_reference_args()")
>
Hi
Am Mittwoch, 11. September 2019, 04:37:46 CEST schrieb Masahiro Yamada:
> - Does the SOCFPGA boot ROM support the NAND boot mode?
Cyclone V HPS TRM Section "A3 Booting and Configuration" lists QSPI, SD/MMC and
Nand as bootsource.
> - If so, which value does it use for SPARE_AREA_SKIP_BYTES?
On Sep 11 2019, Geert Uytterhoeven wrote:
> Hi Andreas,
>
> On Thu, Aug 15, 2019 at 12:37 AM Andreas Schwab wrote:
>> On Aug 14 2019, Palmer Dabbelt wrote:
>> > On Wed, 14 Aug 2019 13:32:50 PDT (-0700), Paul Walmsley wrote:
>> >> On Wed, 14 Aug 2019, Vincent Chen wrote:
>> >>> Make the
On Wed 11-09-19 15:22:30, Yunsheng Lin wrote:
[...]
> It seems that there is no protection that prevent setting the node
> of device to an invalid node.
> And the kernel does have a few different check now:
> 1) some does " < 0" check;
> 2) some does "== NUMA_NO_NODE" check;
> 3) some does ">=
When numvfs is being updated, reply to numvfs queries with EAGAIN.
As drivers may notify changes on numvfs before they are implemented,
it is advisable to not reply rather than giving back an outdated value.
Clients will notice that the value is still unknown and will retry
to get it.
The patch
Hi,
On 10/09/2019 15:47, Claudiu Beznea wrote:
> From: Alexandre Belloni
>
> Some timer drivers may behave either as clocksource or clockevent
> or both. Until now, in case of platforms with multiple hardware
> resources of the same type, the drivers were chosing the first
> registered hardware
Hi Martin,
On 2019/9/10 1:24, Martin Blumenstingl wrote:
> Hi Jianxin,
>
> On Mon, Sep 9, 2019 at 2:03 PM Jianxin Pan wrote:
>>
>> Hi Martin,
>>
>> On 2019/9/7 23:02, Martin Blumenstingl wrote:
>>> Hi Jianxin,
>>>
>>> On Fri, Sep 6, 2019 at 7:58 AM Jianxin Pan wrote:
>>> [...]
> also I'm a
On 9/10/19 6:22 PM, Sami Tolvanen wrote:
> On Tue, Sep 10, 2019 at 08:37:19AM +, Yonghong Song wrote:
>> You did not mention BPF_BINARY_HEADER_MAGIC and added member
>> of `magic` in bpf_binary_header. Could you add some details
>> on what is the purpose for this `magic` member?
>
> Sure,
> Subject: Re: [PATCH] ARM: Add support for Realtek SOC
>
> On Thu, Sep 5, 2019 at 7:48 AM wrote:
> >
> > From: "james.tai"
> >
> > This patch adds the basic machine file for the Realtek RTD16XX
> > platform.
> >
> > Signed-off-by: james.tai
>
> Hi James,
>
> Thanks a lot for your
Hi, Andy.
On 9/11/19 6:18 AM, Andy Lutomirski wrote:
On Tue, Sep 10, 2019 at 12:26 PM Thomas Hellström (VMware)
wrote:
On 9/10/19 6:11 PM, Andy Lutomirski wrote:
On Sep 5, 2019, at 8:24 AM, Christoph Hellwig wrote:
On Thu, Sep 05, 2019 at 05:21:24PM +0200, Thomas Hellström (VMware) wrote:
devm_fwnode_get_index_gpiod_from_child() is too long, besides the fwnode
in question does not have to be a child of device node. Let's rename it
to devm_fwnode_gpiod_get_index() and keep the old name for compatibility
for now.
Also let's add a devm_fwnode_gpiod_get() wrapper as majority of the
This introduces fwnode_gpiod_get_index() that iterates through common gpio
suffixes when trying to locate a GPIO within a given firmware node.
We also switch devm_fwnode_gpiod_get_index() to call
fwnode_gpiod_get_index() instead of iterating through GPIO suffixes on
its own.
Signed-off-by:
The old Arizona binding did not use -gpio or -gpios suffix, so
devm_gpiod_get() does not work for it. As it is the one of a few users
of devm_gpiod_get_from_of_node() API that I want to remove, I'd rather
have a small quirk in the gpiolib OF handler, and switch Arizona
driver to devm_gpiod_get().
Tease apart of_find_gpio() into common function that works on the
firmware node, and a fallback handler that works on the device
structure, so that we can later use of_find_gpio() in
fwnode_gpiod_get_index().
Signed-off-by: Dmitry Torokhov
---
drivers/gpio/gpiolib-of.c | 149
Instead of fwnode_get_named_gpiod() that I plan to hide away, let's use
the new fwnode_gpiod_get_index() that mimics gpiod_get_index(), bit
works with arbitrary firmware node.
Signed-off-by: Dmitry Torokhov
---
drivers/net/phy/mdio_bus.c | 4 ++--
1 file changed, 2 insertions(+), 2
Ensure that all paths to obtain/look up GPIOD from generic
consumer-visible APIs go through the new fwnode_locate_gpiod(), so that
we can easily extend the support for new firmware mechanisms.
Signed-off-by: Dmitry Torokhov
---
drivers/gpio/gpiolib-acpi.c | 88 +++
Tease apart acpi_find_gpio() into common function that works on the
firmware node, and a fallback handler that works on the ACPI device
structure, so that we can later use acpi_find_gpio() in
fwnode_gpiod_get_index().
Signed-off-by: Dmitry Torokhov
---
drivers/gpio/gpiolib-acpi.c | 77
Instead of fwnode_get_named_gpiod() that I plan to hide away, let's use
the new fwnode_gpiod_get_index() that mimics gpiod_get_index(), bit
works with arbitrary firmware node.
Signed-off-by: Dmitry Torokhov
---
drivers/net/phy/phylink.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Instead of fwnode_get_named_gpiod() that I plan to hide away, let's use
the new fwnode_gpiod_get_index() that mimics gpiod_get_index(), bit
works with arbitrary firmware node.
Signed-off-by: Dmitry Torokhov
---
drivers/gpu/drm/bridge/ti-tfp410.c | 4 ++--
1 file changed, 2 insertions(+), 2
Now that there are no external users of fwnode_get_named_gpiod() we can
make it static.
Signed-off-by: Dmitry Torokhov
---
drivers/gpio/gpiolib.c| 108 ++
include/linux/gpio/consumer.h | 13
2 files changed, 43 insertions(+), 78 deletions(-)
diff
Now that static device properties understand notion of child nodes and
references, let's teach gpiolib to handle them:
- GPIOs are represented as a references to software nodes representing
gpiochip
- references must have 2 arguments - GPIO number within the chip and
GPIO flags
If userspace doesn't set KVM_MEM_LOG_DIRTY_PAGES on memslot before calling
kvm_s390_vm_start_migration(), kernel will oops with:
Unable to handle kernel pointer dereference in virtual kernel address space
Failing address: TEID: 0483
Fault in home space mode
This series attempts to add support for software nodes to gpiolib, using
software node references that were introduced recently. This allows us
to convert more drivers to the generic device properties and drop
support for custom platform data:
static const struct software_node gpio_bank_b_node =
On Mon, Sep 09, 2019 at 05:28:08PM +0100, Jarkko Sakkinen wrote:
On Sat, Sep 07, 2019 at 06:04:48PM -0400, Sasha Levin wrote:
On Sat, Sep 07, 2019 at 09:55:18PM +0300, Jarkko Sakkinen wrote:
> On Tue, 2019-09-03 at 15:43 -0400, Sasha Levin wrote:
> > Right. I gave a go at backporting a few
From: "Enke Chen (enkechen)"
Date: Tue, 10 Sep 2019 23:55:59 +
> Do you still have concerns about backward compatibility of the fix?
I'm not convinced by your arguments and I am also completely swamped at
LPC2019 running the networking track this week.
On 11.09.19 09:52, Igor Mammedov wrote:
> If userspace doesn't set KVM_MEM_LOG_DIRTY_PAGES on memslot before calling
> kvm_s390_vm_start_migration(), kernel will oops with:
>
> Unable to handle kernel pointer dereference in virtual kernel address space
> Failing address:
> Subject: Re: [PATCH] ARM: config: Add Realtek RTD16XX defconfig
>
> On Thu, Sep 5, 2019 at 10:14 AM wrote:
> >
> > From: "james.tai"
> >
> > Add a defconfig for Realtek RTD16XX platform.
> >
> > Signed-off-by: james.tai
> > ---
> > arch/arm/configs/rtd16xx_defconfig | 427
> >
> Subject: Re: [PATCH] ARM: dts: realtek: Add support for Realtek RTD16XX
> evaluation board
>
> On Thu, Sep 5, 2019 at 10:10 AM wrote:
>
> > +
> > +/ {
> > + model= "Realtek Mjolnir Evaluation Board";
> > + model_hex= <0x0653>;
>
> The 'mode_hex' property is rather unusual,
On 9/11/19 7:59 AM, Ingo Molnar wrote:
* Thomas Hellström (VMware) wrote:
With SEV and sometimes with SME encryption, The dma api coherent memory is
typically unencrypted, meaning the linear kernel map has the encryption
bit cleared. However, default page protection returned from
From: Huazhong Tan
Date: Wed, 11 Sep 2019 10:40:32 +0800
> This patch-set includes a VF feature, bugfixes and cleanups for the HNS3
> ethernet controller driver.
Series applied.
From: Navid Emamdoost
Date: Tue, 10 Sep 2019 18:01:40 -0500
> In i2400m_op_rfkill_sw_toggle cmd buffer should be released along with
> skb response.
>
> Signed-off-by: Navid Emamdoost
Applied.
Good thing nobody uses wimax.
From: Navid Emamdoost
Date: Tue, 10 Sep 2019 19:37:45 -0500
> In qrtr_tun_write_iter the allocated kbuf should be release in case of
> error happening.
>
> Signed-off-by: Navid Emamdoost
Shouldn't it also be freed in case of success too?
1 - 100 of 798 matches
Mail list logo
