On Wed, Nov 29, 2017 at 12:38:52AM +0200, Jarkko Sakkinen wrote:
> On Sat, Nov 25, 2017 at 09:29:25PM +0200, Jarkko Sakkinen wrote:
> > This commits implements the in-kernel launch enclave. It is wrapped into
> > a user space program that reads SIGSTRUCT instances from stdin and
> > outputs launch
Since Ralf havn't appear for a long time, I resend this patch.
Btw: Why linux-mips wiki and patchwork down for so long time?
The GKTW70SDAE4SE is an LVDS display panel.
Their bindings are modelled on the the LVDS panel bindings.
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
.../bindings/display/panel/sgd,gktw70sdae4se.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644
D
To operate EC from platform driver, this head file need able to be include
from anywhere. This patch just move ec_kb3310b.h to include dir and
clean up ec_kb3310b.h.
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/ec_kb3310b.h | 170 +++
arch/mips/loongson64/
This patch just add pdev during boot to load the platform driver
Signed-off-by: Jiaxun Yang
---
arch/mips/loongson64/lemote-2f/Makefile | 2 +-
arch/mips/loongson64/lemote-2f/platform.c | 27 +++
2 files changed, 28 insertions(+), 1 deletion(-)
create mode 100644 arch
Yeeloong is a laptop with a MIPS Loongson 2F processor, AMD CS5536
chipset, and KB3310B controller.
This yeeloong_laptop module enables access to sensors, battery,
video camera switch, external video connector event, and some
additional buttons.
This driver was orginally from linux-loongson-commu
On Sun, Dec 03, 2017 at 07:19:53PM +0200, Dan Aloni wrote:
> Hi all,
>
> [[ CC'ed: folks relating to the original __*_refok family of attributes,
> deferred probing, Open Firmware maintainer, drivers/base/ maintainer,
> kernel harderning, LKML ]]
>
> It seems that it is possible to cause a use-af
Since lemote-2f/marchtype.c need to get cmdline from loongson.h
this patch simply copy kernel command line from arcs_cmdline
to fix that issue
Signed-off-by: Jiaxun Yang
---
arch/mips/include/asm/mach-loongson64/loongson.h | 6 ++
arch/mips/loongson64/common/cmdline.c| 7 +++
On Mon, Dec 04, 2017 at 09:18:05AM +0100, Dmitry Vyukov wrote:
> On Mon, Dec 4, 2017 at 9:14 AM, Dan Carpenter
> wrote:
> > On Sun, Dec 03, 2017 at 12:16:08PM -0800, Eric Biggers wrote:
> >> Looks like BLKTRACESETUP doesn't limit the '.buf_nr' parameter, allowing
> >> anyone
> >> who can open a
On Mon, 2017-12-04 at 10:17 +0100, Jerome Brunet wrote:
> On Mon, 2017-12-04 at 14:00 +0800, Yixun Lan wrote:
> > From: Jian Hu
> >
> > Add PWM DT info for the Amlogic's Meson-Axg SoC.
> >
> > Signed-off-by: Jian Hu
> > Signed-off-by: Yixun Lan
> > ---
> > arch/arm64/boot/dts/amlogic/meson-ax
On 12/04/17 at 08:36am, Greg Kroah-Hartman wrote:
> On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Young wrote:
> > +#define __ATTR_IRUSR(_name) {
> > \
> > + .attr = { .name = __stringify(_name), .mode = S_IRUSR }, \
> > + .show = _name##_
This patch introduces an eBPF based queue selection method. With this,
the policy could be offloaded to userspace completely through a new
ioctl TUNSETSTEERINGEBPF.
Signed-off-by: Jason Wang
---
Changes from V2:
- call rtnl during netdev free
- switch to use call_rcu() to prevent DOS from userspa
On Fri 01-12-17 08:29:53, Dan Williams wrote:
> On Fri, Dec 1, 2017 at 8:02 AM, Jason Gunthorpe wrote:
> >
> > On Fri, Dec 01, 2017 at 11:12:18AM +0100, Michal Hocko wrote:
> > > On Thu 30-11-17 12:01:17, Jason Gunthorpe wrote:
> > > > On Thu, Nov 30, 2017 at 10:32:42AM -0800, Dan Williams wrote:
On Mon, Dec 04, 2017 at 05:29:28PM +0800, Dave Young wrote:
> On 12/04/17 at 08:36am, Greg Kroah-Hartman wrote:
> > On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Young wrote:
> > > +#define __ATTR_IRUSR(_name) {
> > > \
> > > + .attr = { .name = __stri
Hi,
On 04-12-17 10:01, Javier Martinez Canillas wrote:
Hi Hans,
Thanks a lot for your feedback.
On 12/04/2017 09:29 AM, Hans de Goede wrote:
Hi,
On 01-12-17 12:10, Javier Martinez Canillas wrote:
The driver doesn't have a struct of_device_id table but supported devices
are registered via De
On Sun, Dec 03, 2017 at 01:58:12PM +, Gilad Ben-Yossef wrote:
> The ccree drivers was marking a lot of big functions in C file as
> static inline for no good reason. Remove the inline qualifier from
> any but the few truly single line functions.
>
The compiler is free to ignore inline hints..
Dear All,
For O2micro/Bayhubtech SD Host DeviceID 8620, eMMC HS200 mode is working at
1.8v and it uses hardware tuning. The hardware tuning only needs to send one
tuning command instead of multiple tuning commands with software tuning.
Signed-off-by: ernest.zhang
---
drivers/mmc/host/sdhci-pc
On Mon, 04 Dec 2017, Stephen Rothwell wrote:
> Hi Lee,
>
> After merging the mfd tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/staging/rts5208/sd.o: In function `.sd_power_off_card3v3':
> (.text+0x5760): multiple definition of `.sd_power_off_card3v3'
> dri
Hi, Pali,
It does not work in my test result.
BTW, other some functions also use both of "struct psmouse" and "struct
alps_data" argument.
I just followed it.
Best Regards,
Masaki Ota
-Original Message-
From: Pali Rohár [mailto:pali.ro...@gmail.com]
Sent: Monday, December 04, 2017 6:12
Looks good. Thanks!
regards,
dan carpenter
Hi Maxime,
I just noticed that you are using the second iteration?
Have you received my third iteration?
On Sat, 25 Nov 2017 17:02:33 +0100
Maxime Ripard wrote:
> On Thu, Nov 23, 2017 at 09:14:44AM +0800, Yong wrote:
> > > On Wed, Nov 22, 2017 at 09:33:06AM +0800, Yong wrote:
> > > > > On Thu,
Hi,
On 04-12-17 10:44, Jonathan Cameron wrote:
On Mon, 4 Dec 2017 09:29:38 +0100
Hans de Goede wrote:
Hi,
On 01-12-17 12:10, Javier Martinez Canillas wrote:
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assu
On 02/12/17 12:10, Linus Walleij wrote:
On Wed, Nov 29, 2017 at 12:36 PM, Richard Fitzgerald
wrote:
On 29/11/17 10:18, Linus Walleij wrote:
On Thu, Nov 23, 2017 at 6:13 PM, Richard Fitzgerald
wrote:
+config MFD_MADERA_I2C
+ bool "Cirrus Logic Madera codecs with I2C"
+ select MF
The new preempt enable/disable events introduced by:
d59158162 tracing: Add support for preempt and irq enable/disable events
are defined only for CONFIG_DEBUG_PREEMPT kernels when the
CONFIG_PREEMPTIRQ_EVENTS support, introduced by the above patch, is
enabled.
These events are generated within
On Mon, 4 Dec 2017 10:00:54 +0100
SF Markus Elfring wrote:
> > Why would you compile the kernel without optimization?
>
> Can another reason be occasionally still relevant?
No.
>
> Will the compilation be a bit quicker when extra data processing
> could be omitted?
Why would you care more
On 4 December 2017 at 09:34, Greg Kroah-Hartman
wrote:
> On Mon, Dec 04, 2017 at 05:29:28PM +0800, Dave Young wrote:
>> On 12/04/17 at 08:36am, Greg Kroah-Hartman wrote:
>> > On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Young wrote:
>> > > +#define __ATTR_IRUSR(_name) {
All,
This pull-request v2 contains a fix-up symbol clash when built for PPC.
(Thanks to Stephen Rothwell for the patch)
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git
On Monday 04 December 2017 09:40:04 Masaki Ota wrote:
> Hi, Pali,
>
> It does not work in my test result.
Hm.. that is strange, we have dangling pointers in struct alps_data?
Otherwise I have no idea why does not work.
> BTW, other some functions also use both of "struct psmouse" and "struct
>
All,
This pull-request v2 contains a fix-up symbol clash when built for PPC.
(Thanks to Stephen Rothwell for the patch)
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git
Hello!
On 12/4/2017 6:21 AM, David Lechner wrote:
This adds optional nvmem consumer properties to the ti,wlink-st device tree
bindings to allow specifying the Bluetooth MAC address.
Signed-off-by: David Lechner
---
Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4
1 file cha
On Mon, 4 Dec 2017 10:07:57 +0100
Juri Lelli wrote:
> On 04/12/17 03:09, Steven Rostedt wrote:
> > On Mon, 4 Dec 2017 08:45:17 +0100
> > Juri Lelli wrote:
> >
> > > Right. I was wondering however if for the truly UP case we shouldn't be
> > > initiating/queueing callbacks (pull/push) at all?
>> Can the software areas distinguished where such special handling matters?
>
> No idea.
I would like to point another example out.
> That's something you are going to have to figure out on your own.
How do you think about information from an other clarification request
for the topic “caif: U
Correct the broken uapi for the BPF_PROG_TYPE_PERF_EVENT program type
by exporting the user_pt_regs structure instead of the pt_regs structure
that is in-kernel only.
Signed-off-by: Hendrik Brueckner
Reviewed-by: Thomas Richter
Acked-by: Alexei Starovoitov
Cc: Will Deacon
Cc: Mark Rutland
Cc:
Perf tool bpf selftests revealed a broken uapi for s390 and arm64.
With the BPF_PROG_TYPE_PERF_EVENT program type the bpf_perf_event
structure exports the pt_regs structure for all architectures.
This fails for s390 and arm64 because pt_regs are not part of the
user api and kept in-kernel only. T
On Sat, Dec 02, 2017 at 12:19:27PM +, Jonathan Cameron wrote:
> On Wed, 29 Nov 2017 22:31:12 +
> Jeremy Cline wrote:
>
> > Some BOSC0200 acpi_device-s describe two accelerometers in a single ACPI
> > device. Check for a companion device and handle a second i2c_client
> > if it is present.
The regs_query_register_offset() helper function converts
register name like "%r0" to an offset of a register in user_pt_regs
It is required by the BPF prologue generator.
The user_pt_regs structure was recently added to "asm/ptrace.h".
Hence, update tools/perf/check-headers.sh to keep the header
On 12/02/2017 07:48 PM, Al Viro wrote:
> On Fri, Dec 01, 2017 at 09:47:00PM +0100, Daniel Borkmann wrote:
>>> Might want to replace security_path_mknod() with something saner, while we
>>> are
>>> at it.
>>>
>>> Objections?
>>
>> No, thanks for looking into this, and sorry for this fugly hack! :(
Correct whitespace and coding style issues in the s390 asm/ptrace.h
uapi header file. This is preparatory work to copy it to the tools/
directory for inclusion by selftests and perf.
Signed-off-by: Hendrik Brueckner
---
arch/s390/include/uapi/asm/ptrace.h | 118 -
Am Mittwoch, 29. November 2017, 15:35:41 CET schrieb Brian Norris:
> We've documented this one already, but we didn't add it to the DTSI yet.
>
> Suggested-by: Nickey Yang
> Signed-off-by: Brian Norris
applied for 4.16
Thanks
Heiko
Synchronize the uapi kernel header files which solves the broken
uapi export of pt_regs. Because of arch-specific uapi headers,
extended the include path in the Makefile.
With this change, the test_verifier program compiles and runs successfully
on s390.
Signed-off-by: Hendrik Brueckner
Reviewe
To mitigate and correct the broken uapi for the BPF_PROG_TYPE_PERF_EVENT
program type, introduce a user_pt_regs structure (similar to arm64) that
exports parts from the beginnig of the pt_regs structure.
The export must start with the beginning of the pt_regs structure because
to correctly calcula
Commit 0515e5999a466dfe ("bpf: introduce BPF_PROG_TYPE_PERF_EVENT
program type") introduced the bpf_perf_event_data structure which
exports the pt_regs structure. This is OK for multiple architectures
but fail for s390 and arm64 which do not export pt_regs. Programs
using them, for example, the b
On Mon, Dec 04, 2017 at 09:48:37AM +, Ard Biesheuvel wrote:
> On 4 December 2017 at 09:34, Greg Kroah-Hartman
> wrote:
> > On Mon, Dec 04, 2017 at 05:29:28PM +0800, Dave Young wrote:
> >> On 12/04/17 at 08:36am, Greg Kroah-Hartman wrote:
> >> > On Mon, Dec 04, 2017 at 10:02:16AM +0800, Dave Yo
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: 04 December 2017 09:10
> To: Stephen Rothwell
> Cc: Linux-Next Mailing List ; Linux Kernel Mailing
> List ; Xingyu Chen ;
> Jonathan Cameron ; Martin Blumenstingl
>
> Subject: Re: linux-next: manual merge of the stagin
Am Mittwoch, 29. November 2017, 17:11:27 CET schrieb Brian Norris:
> From: Nickey Yang
>
> This patch adds the information for the secondary MIPI DSI controller,
> e.g., interrupts, grf, clocks, ports and so on. Mirrors the existing
> definition for dsi0.
>
> Signed-off-by: Nickey Yang
> Signed
Vincent Legoll writes:
> The following patch makes it easier to disable all SSB config
> options without entering the submenu. It will also enable one
> to see that en-disabled state from the outside menu.
>
> This is only intended to change menuconfig UI, not change
> the config dependencies.
S
On 4 December 2017 at 09:59, Greg Kroah-Hartman
wrote:
> On Mon, Dec 04, 2017 at 09:48:37AM +, Ard Biesheuvel wrote:
>> On 4 December 2017 at 09:34, Greg Kroah-Hartman
>> wrote:
>> > On Mon, Dec 04, 2017 at 05:29:28PM +0800, Dave Young wrote:
>> >> On 12/04/17 at 08:36am, Greg Kroah-Hartman w
On 03-12-2017 05:20, Nick Bowler wrote:
>
> Your patch changes things. With this applied on top of 4.15-rc1
> it is failing 100% of the time instead of only half of the time.
Ok, it was a long shot anyway.
>
> I brought the original test equipment back to the setup so I can
> see the video and p
On Sun, Dec 03, 2017 at 06:49:40PM +0200, Marcus Wolf wrote:
>
> Hi Simon,
Hi,
>
> thanks for your effort.
>
> I have two questions:
> * According to my practical experiance, enums were always written in lower
> case. Does kernel style guide ask for upper case for enums?
Yes. From Documentation
Correct the interrupt number assigned to the Realtek PHY in the q200
Fixes: b94d22d94ad2 ("ARM64: dts: meson-gx: add external PHY interrupt on some
platforms")
Reported-by: Martin Blumenstingl
Signed-off-by: Jerome Brunet
---
This change depends on the related series from Martin [0]
Thanks f
Am Mittwoch, 29. November 2017, 10:47:55 CET schrieb Brian Norris:
> From: Nickey Yang
>
> We might include additional ports in derivative device trees, so the
> 'port' node should have an address, and the parent 'ports' node needs
> /#{addres,size}-cells.
>
> v4:
> * keep #{address,size}-cells
Dear all,
Add register definition for eMMC HS200 mode.
Add hardware tuning for eMMC HS200 mode.
Signed-off-by: ernest.zhang
---
drivers/mmc/host/sdhci-pci-o2micro.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/mmc/host/sdhci-pci-o2micro.h
b/drivers/mmc/host/sdhci-pci-o2micro.
On 12/4/2017 12:54 PM, Sergei Shtylyov wrote:
This adds optional nvmem consumer properties to the ti,wlink-st device tree
bindings to allow specifying the Bluetooth MAC address.
Signed-off-by: David Lechner
---
Documentation/devicetree/bindings/net/ti,wilink-st.txt | 4
1 file changed,
Dear all,
Don't clear transfer mode register in sdhci_set_transfer_mode().
In sdhci_set_transfer_mode(), clear transfer mode quirk2 will clear SD host
transfer mode register for non-data commands. This quirk is used for the bug of
O2micro/Bayhubtech devices. In eMMC HS200 tuning case, the tunin
On Mon, Dec 04, 2017 at 10:03:19AM +, Ard Biesheuvel wrote:
> On 4 December 2017 at 09:59, Greg Kroah-Hartman
> wrote:
> > On Mon, Dec 04, 2017 at 09:48:37AM +, Ard Biesheuvel wrote:
> >> On 4 December 2017 at 09:34, Greg Kroah-Hartman
> >> wrote:
> >> > On Mon, Dec 04, 2017 at 05:29:28PM
On Mon, Dec 04, 2017 at 06:20:06AM +0100, Linus Lüssing wrote:
> On Mon, Dec 04, 2017 at 05:53:35AM +0100, Linus Lüssing wrote:
> > And so, no I do not have this patch. I looked at it now, but it
> > does not seem to have any relation with .matchinfo, does it?
>
> Relation between .usersize and .c
On Sun, Dec 03, 2017 at 04:17:24PM +0100, Simon Sandström wrote:
> Renames the enum optionOnOff and its values optionOn, optionOff to enum
> option_on_off and OPTION_ON, OPTION_OFF. Fixes checkpatch.pl warnings:
> "Avoid CamelCase: , , ".
>
> Signed-off-by: Simon Sandström
> ---
> drivers/stagin
>> Will the compilation be a bit quicker when extra data processing
>> could be omitted?
>
> Why would you care more about the time it takes to compile the kernel,
> than the time it takes for executing it?
I am also interested in the evolution of compilation time frames.
> Benchmarks are all a
On Mon, 2017-12-04 at 19:21 +1100, Tobin C. Harding wrote:
> On Mon, Dec 04, 2017 at 10:51:53AM +0530, Kaiwan N Billimoria wrote:
> > > ---
> > diff --git a/scripts/leaking_addresses.pl b/scripts/leaking_addresses.pl
> > index 9906dcf8b807..260b52e456f1 100755
> > --- a/scripts/leaking_addresses.pl
From: Juri Lelli
Since SCHED_DEADLINE doesn't track utilization signal (but reserves a
fraction of CPU bandwidth to tasks admitted to the system), there is no
point in evaluating frequency changes during each tick event.
Move frequency selection triggering points to where running_bw changes.
Co
Hi,
v2 of the RFC set implementing frequency/cpu invariance and OPP selection for
SCHED_DEADLINE [1]. The set is based on mainline as of today (ae64f9bd1d36).
Patches high level description:
o [01-02]/08 add the necessary links to start accounting DEADLINE contribution
to OPP sele
On Sun, Dec 03, 2017 at 04:17:25PM +0100, Simon Sandström wrote:
> Renames enum dataMode and its values packet, continuous, continuousNoSync
> to enum data_mode and PACKET, CONTINUOUS, CONTINUOUS_NO_SYNC. Fixes
> checkpatch.pl warnings: "Avoid CamelCase: , ".
These names are too generic. Delete t
Hello Jonathan,
On 12/04/2017 10:44 AM, Jonathan Cameron wrote:
> On Mon, 4 Dec 2017 09:29:38 +0100
> Hans de Goede wrote:
>
>> Hi,
>>
>> On 01-12-17 12:10, Javier Martinez Canillas wrote:
>>> The driver doesn't have a struct of_device_id table but supported devices
>>> are registered via Device
From: Juri Lelli
Apply frequency and cpu scale-invariance correction factor to bandwidth
enforcement (similar to what we already do to fair utilization tracking).
Each delta_exec gets scaled considering current frequency and maximum
cpu capacity; which means that the reservation runtime paramete
From: Juri Lelli
To be able to treat utilization signals of different scheduling classes
in different ways (e.g., CFS signal might be stale while DEADLINE signal
is never stale by design) we need to split sugov_cpu::util signal in two:
util_cfs and util_dl.
This patch does that by also changing
From: Juri Lelli
Currently, frequency and cpu capacity scaling is only performed on
CONFIG_SMP systems (as CFS PELT signals are only present for such
systems). However, other scheduling classes want to do freq/cpu scaling,
and for !CONFIG_SMP configurations as well.
arch_scale_freq_capacity is u
From: Juri Lelli
sd parameter is never used in arch_scale_freq_capacity (and it's hard to
see where information coming from scheduling domains might help doing
frequency invariance scaling).
Remove it; also in anticipation of moving arch_scale_freq_capacity
outside CONFIG_SMP.
Signed-off-by: Ju
From: Juri Lelli
No assumption can be made upon the rate at which frequency updates get
triggered, as there are scheduling policies (like SCHED_DEADLINE) which
don't trigger them so frequently.
Remove such assumption from the code, by always considering
SCHED_DEADLINE utilization signal as not s
From: Juri Lelli
Worker kthread needs to be able to change frequency for all other
threads.
Make it special, just under STOP class.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Rafael J. Wysocki
Cc: Viresh Kumar
Cc: Luca Abeni
Cc: Claudio Scordino
---
Changes from RFC
From: Juri Lelli
SCHED_DEADLINE tracks active utilization signal with a per dl_rq
variable named running_bw.
Make use of that to drive cpu frequency selection: add up FAIR and
DEADLINE contribution to get the required CPU capacity to handle both
requirements (while RT still selects max frequency
Hi Cherian,
Your patch 'ACPI / CPPC: Make CPPC ACPI driver aware of PCC subspace IDs'
introduced a out-of-bounds BUG in kernel. The code need to check
cpu_pcc_subspace_idx before use it since it can be -1. Thanks.
[ 15.113449]
==
[
On 03/12/17 23:21, Shanker Donthineni wrote:
> As per MADT specification, it's perfectly valid firmware can pass
> MADT table to OS with disabled GICC entries. ARM64-SMP code skips
> those cpu cores to bring online. However the current GICv3 driver
> probe bails out in this case on systems where re
Hi,
On 04-12-17 10:58, Mika Westerberg wrote:
On Sat, Dec 02, 2017 at 12:19:27PM +, Jonathan Cameron wrote:
On Wed, 29 Nov 2017 22:31:12 +
Jeremy Cline wrote:
Some BOSC0200 acpi_device-s describe two accelerometers in a single ACPI
device. Check for a companion device and handle a se
On Sun, Dec 03, 2017 at 12:12:45PM -0800, Kevin Cernekee wrote:
> The capability check in nfnetlink_rcv() verifies that the caller
> has CAP_NET_ADMIN in the namespace that "owns" the netlink socket.
> However, nfnl_cthelper_list is shared by all net namespaces on the
> system.
Right, we need per-
Hi Steven,
On 12/02/2017 07:04 PM, Steven Rostedt wrote:
> Daniel Wagner reported a crash on the beaglebone black. This is a
> single CPU architecture, and does not have a functional:
> arch_send_call_function_single_ipi() and can crash if that is called.
>
> As it only has one CPU, it shouldn't
On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
> diff --git a/drivers/staging/pi433/pi433_if.h
> b/drivers/staging/pi433/pi433_if.h
> index 34ff0d4807bd..bcfe29840889 100644
> --- a/drivers/staging/pi433/pi433_if.h
> +++ b/drivers/staging/pi433/pi433_if.h
> @@ -63,7 +63,7 @@ stru
Hi David, Andrew, Florian, Simon, Magnus,
This patch series adds optional PHY reset support to phylib.
The first two patches are destined for David's net-next tree. They add
core PHY reset code, and update a driver that currently uses its own
reset code.
The last two patches are destined
Describe the GPIO used to reset the Ethernet PHY for EthernetAVB.
This allows the driver to reset the PHY during probe and after system
resume.
On ULCB, the enable pin of the regulator providing PHY power is always
pulled high, but the driver may still need to reset the PHY if this
wasn't done by
From: Sergei Shtylyov
With the phylib now being aware of the "reset-gpios" PHY node property,
there should be no need to frob the PHY reset in this driver anymore...
Signed-off-by: Sergei Shtylyov
Acked-by: Nicolas Ferre
Reviewed-by: Florian Fainelli
Signed-off-by: Geert Uytterhoeven
---
v4:
On Friday 24 November 2017 13:28:59 Oleksandr Natalenko wrote:
> On pátek 24. listopadu 2017 12:25:43 CET Pali Rohár wrote:
> > On Friday 24 November 2017 12:17:30 Oleksandr Natalenko wrote:
> > > > There are two patches waiting to be tested in
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=19
Describe the GPIO used to reset the Ethernet PHY for EthernetAVB.
This allows the driver to reset the PHY during probe and after system
resume.
This fixes Ethernet operation after resume from s2ram on Salvator-XS,
where the enable pin of the regulator providing PHY power is connected
to PRESETn, a
From: Sergei Shtylyov
The PHY devices sometimes do have their reset signal (maybe even power
supply?) tied to some GPIO and sometimes it also does happen that a boot
loader does not leave it deasserted. So far this issue has been attacked
from (as I believe) a wrong angle: by teaching the MAC dri
On Mon, 2017-11-27 at 16:17 -0600, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
I have to say I'm totally not sold on regexps matching comment
contents. Was something more explicit ever considered? Like:
On Mon, Dec 04, 2017 at 01:17:37PM +0300, Dan Carpenter wrote:
> Perhaps choose different function names if you want? You could do it
> as several patches:
>
> patch 1: change types to bool
> patch 2: sed -e '/ == optionOn//'
> patch 3: split the functions into two functions
> patch 4: delete opt
On 30.11.2017 13:04, Colin King wrote:
> From: Colin Ian King
>
> The array audit_point_name is local to the source and does not need to
> be in global scope, so make it static.
>
> Cleans up sparse warning:
> arch/x86/kvm/mmu_audit.c:22:12: warning: symbol 'audit_point_name' was
> not declared.
On 1 December 2017 at 12:03, Yoshihiro Shimoda
wrote:
> Hi,
>
>> From: Ulf Hansson, Sent: Friday, December 1, 2017 6:22 PM
>>
>> + Kishon
>>
>> On 30 November 2017 at 13:51, Yoshihiro Shimoda
>> wrote:
>> > Hi,
>> >
>> >> From: Ulf Hansson, Sent: Wednesday, November 29, 2017 6:59 PM
>> >>
>> >> O
On Mon, Dec 04, 2017 at 11:29:31AM +0100, Hans de Goede wrote:
> i2c_new_secondary_device() is for a different purpose, this is for when
> a single i2c device listens on multiple addresses and the driver wants
> separate i2c_client-s to use to talk to each address.
>
> In this case there are 2 sep
Commit a33801e8b473 ("block, bfq: move debug blkio stats behind
CONFIG_DEBUG_BLK_CGROUP") introduced two batches of confusing ifdefs:
one reported in [1], plus a similar one in another function. This
commit removes both batches, in the way suggested in [1].
[1] https://www.spinics.net/lists/linux-
Hi!
> Label property was imposed a uniqueness requirement, which was erroneous,
> since ePAPR defines it to "a human readable string describing a device".
>
> Also the binding description misleadingly suggested direct usage of label
> for LED class device name, whereas it should only define a LED
Change 0 to NULL in lov_object_fiemap() in order to fix warning produced
by sparse
Signed-off-by: Andrii Vladyka
Signed-off-by: Andreas Dilger
---
diff --git a/drivers/staging/lustre/lustre/lov/lov_object.c
b/drivers/staging/lustre/lustre/lov/lov_object.c
index 105b707..897cf2c 100644
--- a/
James Morris wrote:
> On Sun, 3 Dec 2017, Tetsuo Handa wrote:
>
> > Tetsuo Handa wrote:
> > > which will allow strcmp() to trigger out of bound read when "size" is
> > > larger than strlen(initial_sid_to_string[i]).
> >
> > Oops. "smaller" than.
> >
> > >
> > > Thus, I guess the simplest fix is
Hi Stephen,
I have addressed the comments given on previous patch versions. Could
you please review the patch series ?
Thanks
Tirupathi
On 11/21/2017 2:41 PM, Tirupathi Reddy wrote:
The SPMI_PMIC clock divider driver configures the clkdiv modules present
on Qualcomm Technologies, Inc. SPMI
When a need raise up to use JTAG interface for system's devices
programming or CPU debugging, usually the user layer
application implements jtag protocol by bit-bang or using a
proprietary connection to vendor hardware.
This method can be slow and not generic.
We propose to implement general JTA
Added document that describe the ABI for JTAG class drivrer
Signed-off-by: Oleksandr Shamray
Acked-by: Arnd Bergmann
---
v12->v13
v11->v12
Tobias Klauser
- rename /Documentation/ABI/testing/jatg-dev -> jtag-dev
- Typo: s/interfase/interface
v10->v11
v9->v10
Fixes added by Oleksandr:
- change jt
It has been tested on Mellanox system with BMC equipped with
Aspeed 2520 SoC for programming CPLD devices.
Signed-off-by: Oleksandr Shamray
Signed-off-by: Jiri Pirko
Acked-by: Rob Herring
---
v12->v13
v11->v12
v10->v11
v9->v10
v8->v9
v7->v8
Comments pointed by pointed by Joel Stanley
- Change
Tetsuo Handa wrote:
> James Morris wrote:
> > On Sun, 3 Dec 2017, Tetsuo Handa wrote:
> >
> > > Tetsuo Handa wrote:
> > > > which will allow strcmp() to trigger out of bound read when "size" is
> > > > larger than strlen(initial_sid_to_string[i]).
> > >
> > > Oops. "smaller" than.
> > >
> > > >
Initial patch for JTAG driver
JTAG class driver provide infrastructure to support hardware/software
JTAG platform drivers. It provide user layer API interface for flashing
and debugging external devices which equipped with JTAG interface
using standard transactions.
Driver exposes set of IOCTL to
Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller.
Driver implements the following jtag ops:
- freq_get;
- freq_set;
- status_get;
- idle;
- xfer;
It has been tested on Mellanox system with BMC equipped with
Aspeed 2520 SoC for programming CPLD devices.
Signed-off-by: Ole
Hi!
I know that we are not touching the rest of the existing description for
MAP_FIXED however the second sentence in the manual page says that "addr
must be a multiple of the page size." Which however is misleading as
this is not enough on some architectures. Code in the wild seems to
(mis)use SHM
£1.5 Million Has Been Granted To You As A Donation Visit
www.bbc.co.uk/news/uk-england-19254228 Sendname Address Phone for more info
901 - 1000 of 1242 matches
Mail list logo
