On Mon, Jan 14, 2019 at 4:11 PM Dmitry Vyukov wrote:
>
> On Wed, Jan 9, 2019 at 2:30 PM Jan Kara wrote:
> >
> > On Tue 08-01-19 12:49:08, Dmitry Vyukov wrote:
> > > On Tue, Jan 8, 2019 at 12:24 PM Jan Kara wrote:
> > > >
> > > > On Tue 08-01-19 19:04:06, Tetsuo Handa wrote:
> > > > > On
On Monday 14 January 2019 11:30:11 Jan Kara wrote:
> On Mon 14-01-19 01:33:30, Kevin Weidemann wrote:
> > 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 /dev/mapper/cryptdev1`
Hi Kevin! You
On Sun, Jan 13, 2019 at 10:57 AM Chen-Yu Tsai wrote:
> The new per-pin-bank regulator handling code in the sunxi pinctrl driver
> has mismatched conditions for enabling and disabling the regulator: it
> is enabled each time a pin is requested, but only disabled when the
> pin-bank's reference
On Wed, Jan 9, 2019 at 2:30 PM Jan Kara wrote:
>
> On Tue 08-01-19 12:49:08, Dmitry Vyukov wrote:
> > On Tue, Jan 8, 2019 at 12:24 PM Jan Kara wrote:
> > >
> > > On Tue 08-01-19 19:04:06, Tetsuo Handa wrote:
> > > > On 2019/01/03 2:26, Jan Kara wrote:
> > > > > On Thu 03-01-19 01:07:25, Tetsuo
On Mon, Jan 14, 2019 at 10:05:17AM +0100, Johan Hovold wrote:
> On Fri, Jan 11, 2019 at 09:03:16PM +0530, Nishad Kamdar wrote:
> > This patch series converts uses of the old GPIO API to the GPIO
> > descriptor API. It also converts the GPIO driver to use the
> > GPIO irqchip library
On Mon, Jan 14, 2019 at 08:25:07PM +0530, Nishad Kamdar wrote:
> This patch series converts uses of the old GPIO API to the GPIO
> descriptor API. It also converts the GPIO driver to use the
> GPIO irqchip library GPIOLIB_IRQCHIP instead of repimplementing
> the same.
>
> Chnages in v7:
> -
On Sat, 12 Jan 2019 12:05:33 +0800
Changbin Du wrote:
> Hi Steven, Have you checked this serias yet? :)
>
Not yet, I'll try to do it today.
-- Steve
Thank you for the explanation!
Best regards
Anatoly
пн, 14 янв. 2019 г. в 17:55, Benjamin Tissoires :
>
> On Mon, Jan 14, 2019 at 3:23 PM Anatoly Trosinenko
> wrote:
> >
> > > fuzzed data is hard to discriminate from valid data.
> >
> > Just in case it can be helpful... If it is about manually
On Mon 2019-01-14 17:05:22, Sergey Senozhatsky wrote:
> On (01/11/19 17:20), Petr Mladek wrote:
> > +static void warn_console(bool console_suppressed,
> > +int orig_log_level,
> > +struct sysrq_key_op *op_p)
> > +{
> > + static int warned;
> > +
> > + if
Use the gpiod interface instead of the deprecated old non-descriptor
interface while continuing to ignore gpio flags from device tree in
"svc_reset_onoff()" for now.
Reviewed-by: Johan Hovold
Signed-off-by: Nishad Kamdar
---
Changes in v7:
- No change.
Changes in v6:
- Make error messages
Use the gpiod interface instead of the deprecated old non-descriptor
interface while continuing to ignore gpio flags from device tree in
functions "deassert_reset()" and "assert_reset()" for now.
Reviewed-by: Johan Hovold
Signed-off-by: Nishad Kamdar
---
Changes in v7:
- No change.
Changes in
On Mon, 14 Jan 2019 15:09:58 +0100
Cornelia Huck wrote:
> On Thu, 3 Jan 2019 17:08:03 +0100
> Cornelia Huck wrote:
>
> > - get_features has returned 64 bits since commit d025477368792
> > ("virtio: add support for 64 bit features.")
> > - properly mark all optional callbacks
> >
> >
On Sat, Jan 12, 2019 at 04:28:43PM +0100, Willy Tarreau wrote:
> From: Silvio Cesare
>
> Change snprintf to scnprintf. There are generally two cases where using
> snprintf causes problems.
I don't have a cover letter or anything before this in the series.
What's going on with dependencies here?
Convert the GPIO driver to use the GPIO irqchip library
GPIOLIB_IRQCHIP instead of reimplementing the same.
Reviewed-by: Johan Hovold
Signed-off-by: Nishad Kamdar
---
Changes in v7:
- No change.
Changes in v5:
- Restore "struct irq_chip irqc" in "struct gb_gpio_controller"
This is because
On Mon, Jan 14, 2019 at 3:23 PM Anatoly Trosinenko
wrote:
>
> > fuzzed data is hard to discriminate from valid data.
>
> Just in case it can be helpful... If it is about manually "parsing"
> descriptors to understand what is wrong by hands, then maybe Kaitai
> Struct parser generator can help. I
This patch series converts uses of the old GPIO API to the GPIO
descriptor API. It also converts the GPIO driver to use the
GPIO irqchip library GPIOLIB_IRQCHIP instead of repimplementing
the same.
Chnages in v7:
- Combine the three patches together.
Changes in v6:
- Patchset now contains two
Martin,
On Mon 14 Jan 2019 at 14:44, Loys Ollivier wrote:
Commit 89a5e15bcba8 ("gpio/mmc/of: Respect polarity in the device tree")
changed the behavior of "cd-inverted" to follow the device tree bindings
specification:
According to SDHCI standard, CD lines are specified as "active low".
On 14/01/2019 14:53, Greg KH wrote:
Should all of these go into 5.0-final? backported to any older releases
as well? Or can we wait until 5.1-rc1?
We can wait until 5.1-rc1
thanks,
srini
thanks,
On Fri 11-01-19 19:06:08, John Hubbard wrote:
> On 1/11/19 6:46 PM, Jerome Glisse wrote:
> > On Fri, Jan 11, 2019 at 06:38:44PM -0800, John Hubbard wrote:
> > [...]
> >
> The other idea that you and Dan (and maybe others) pointed out was a
> debug
> option, which we'll certainly
On Mon, Jan 14, 2019 at 01:44:45PM +, Srinivas Kandagatla wrote:
> Here are some minor fixes to slimbus core for issues found while testing
> wcd9335.
> First one is make the slimbus core match full device id,
> second one is to avoid using big lock in status callback function,
> third one is
Hi Matthias,
On 2019-01-12 05:26, Matthias Kaehlcke wrote:
On Fri, Jan 11, 2019 at 08:37:12PM +0530, Balakrishna Godavarthi wrote:
Hi Matthias,
On 2019-01-11 07:07, Matthias Kaehlcke wrote:
> On Thu, Jan 10, 2019 at 08:22:12PM +0530, Balakrishna Godavarthi wrote:
> > Hi Johan,
> >
> > On
> -Original Message-
> From: Jorgen Hansen [mailto:jhan...@vmware.com]
> Sent: Friday, January 11, 2019 8:58 AM
> To: linux-kernel@vger.kernel.org; virtualizat...@lists.linux-foundation.org
> Cc: gre...@linuxfoundation.org; Pv-drivers ;
> Jorgen S. Hansen
> Subject: [PATCH] VMCI: Verify
On 2018-11-27 15:10:07 [+], Joe Korty wrote:
> Hi Clark,
Hi Clark,
> No I don't, sorry. I am attaching the LAG version, it is a few
> dozen lines shorter than the version I first sent out to the
> mailing list.
Did this make its way to rt-tests? I have some changes on top of it
while I was
On Mon 2019-01-14 14:51:27, Sergey Senozhatsky wrote:
> On (01/11/19 17:20), Petr Mladek wrote:
> > The commit 97f5f0cd8cd0a0544 ("Input: implement SysRq as a separate input
> > handler") added pr_fmt() definition. It caused a duplicated message
> > prefix in the sysrq header messages, for
Commit 89a5e15bcba8 ("gpio/mmc/of: Respect polarity in the device tree")
changed the behavior of "cd-inverted" to follow the device tree bindings
specification:
According to SDHCI standard, CD lines are specified as "active low".
Using the "cd-inverted" property means that the CD line is "active
The goal of this framework is to offer an interface for the
hardware blocks controlling bus accesses rights.
Bus domains controllers are typically used to control if a
hardware block can perform read or write operations on bus.
Smarter domains controllers could be able to define accesses
rights
Describe STM32 Extended TrustZone Protection bindings.
Signed-off-by: Benjamin Gaignard
---
.../devicetree/bindings/bus/domains/st,stm32-etzpc.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644
Documentation/devicetree/bindings/bus/domains/st,stm32-etzpc.txt
STM32 Extended TrustZone Protection Controller (ETZPC) got 3 domains:
- secure: hardware blocks are only accessible by software running on trust
zone.
- non-secure: hardware blocks are accessible by non-secure software (i.e.
linux kernel).
- coprocessor: hardware blocks are only accessible
Document commons domains controller bindings for controller
and client devices.
Signed-off-by: Benjamin Gaignard
---
.../bindings/bus/domains/domainsctrl.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644
Declare ETZPC device as a domains controller node for stm32mp157 SoC
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32mp157c.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157c.dtsi
index
Enable ETZPC and set configuration for CEC node
Signed-off-by: Benjamin Gaignard
---
arch/arm/boot/dts/stm32mp157c-ev1.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/stm32mp157c-ev1.dts
b/arch/arm/boot/dts/stm32mp157c-ev1.dts
index 063ee8ac5dcb..29142ca3d685 100644
The goal of this framework is to offer an interface for the
hardware blocks controlling bus accesses rights.
Bus domains controllers are typically used to control if a
hardware block can perform read or write operations on bus.
Smarter domains controllers could be able to define accesses
rights
To avoid modifying all the drivers call domainsctrl_set_default_config
before probe to apply the configuration define in device node (if any).
When unbinding the device try to apply configuration named "unbind".
Signed-off-by: Benjamin Gaignard
---
drivers/base/dd.c | 9 +
1 file
On 1/14/2019 5:06 AM, Jiri Kosina wrote:
On Mon, 14 Jan 2019, Pavel Machek wrote:
Frankly I'd not call it Meltdown, as it works only on data in the cache,
so the defense is completely different. Seems more like a l1tf
:-).
Meltdown on x86 also seems to work only for data in L1D, but the
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
On Mon 2019-01-14 14:36:42, Sergey Senozhatsky wrote:
> On (01/11/19 16:32), Petr Mladek wrote:
> > The same problem is with the sysrq header line. It uses the trick
> > with console_loglevel by intention. We want to show it but
> > it is not really an error message
>
> May be.
>
> I usually see
Hi Julia,
Thank you for the patch,
On 13/01/2019 09:44, Julia Lawall wrote:
> Add an of_node_put when the result of of_graph_get_remote_port_parent is
> not available.
>
> The semantic match that finds this problem is as follows
> (http://coccinelle.lip6.fr):
>
> //
> @r exists@
> local
On Mon 14-01-19 19:29:39, Arun KS wrote:
> On 2019-01-10 21:53, Alexander Duyck wrote:
[...]
> > Couldn't you just do something like the following:
> > if ((end - start) >= (1UL << (MAX_ORDER - 1))
> > order = MAX_ORDER - 1;
> > else
> >
[+cc Dou, Jens, Thomas, Christoph, linux-pci, LKML]
On Sun, Jan 13, 2019 at 11:24 PM fin4478 fin4478 wrote:
>
> Hi,
>
> A regression from the 4.20 kernel: I have the Asgard 256GB nvme drive
> and my custom non debug 1000Hz timer kernel 5.0 started to throw a
> couple of warning messages at boot.
> fuzzed data is hard to discriminate from valid data.
Just in case it can be helpful... If it is about manually "parsing"
descriptors to understand what is wrong by hands, then maybe Kaitai
Struct parser generator can help. I understand it is probably not
suited well for in-kernel binary
On Mon, 14 Jan 2019, Brian Starkey wrote:
> AFBC is a relatively well-established name, whereas arm-fbc is not a
> term anyone will be familiar with.
First time I ever heard of AFBC. ;)
> We could name the file "arm-afbc.rst", though I am slightly against
> namespacing it that way for the
On 11/01/2019 18:17, Christoph Hellwig wrote:
Use WARN_ON_ONCE to print a stack trace and return a proper error
code instead.
I was racking my brain to remember the reasoning behind BUG_ON() being
the only viable way to prevent errors getting through unhandled, but of
course that was before
Hi Jani,
On Mon, Jan 14, 2019 at 02:23:46PM +0200, Jani Nikula wrote:
> On Fri, 11 Jan 2019, Liviu Dudau wrote:
> > On Thu, Jan 03, 2019 at 05:44:26PM -0300, Ezequiel Garcia wrote:
> >> Hi Liviu,
> >>
> >> On Mon, 2018-12-03 at 11:31 +, Ayan Halder wrote:
> >> > From: Brian Starkey
> >> >
Modified NI devices class to PCI_CLASS_COMMUNICATION_MULTISERIAL.
The reason of doing this is because all NI multi port serial cards
use PCI_CLASS_COMMUNICATION_OTHER class and thus fail the
serial_pci_is_class_communication test added in the commit 7d8905d06405
("serial: 8250_pci: Enable device
On Thu, 3 Jan 2019 17:08:03 +0100
Cornelia Huck wrote:
> - get_features has returned 64 bits since commit d025477368792
> ("virtio: add support for 64 bit features.")
> - properly mark all optional callbacks
>
> Signed-off-by: Cornelia Huck
> ---
> include/linux/virtio_config.h | 8
On Mon, Jan 14, 2019 at 06:34:02PM +0800, Xin Long wrote:
> The similar issue as fixed in Commit 4a2eb0c37b47 ("sctp: initialize
> sin6_flowinfo for ipv6 addrs in sctp_inet6addr_event") also exists
> in sctp_inetaddr_event, as Alexander noticed.
>
> To fix it, allocate sctp_sockaddr_entry with
On Mon, Jan 14, 2019 at 01:49:17PM +0100, Anders Roxell wrote:
> Do you want me to resend it without " 1/3]... " in the subject?
No, that's fine.
signature.asc
Description: PGP signature
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
On Mon, Jan 14, 2019 at 1:59 PM David Hildenbrand wrote:
> The PG_reserved flag is cleared from memory that is part of the kernel
> image (and therefore marked as PG_reserved). Avoid using PG_reserved
> directly.
>
> Cc: Geert Uytterhoeven
> Cc: Andrew Morton
> Cc: Michal Hocko
> Cc: Matthew
On 2019-01-10 21:53, Alexander Duyck wrote:
On Thu, 2019-01-10 at 11:05 +0530, Arun KS wrote:
When freeing pages are done with higher order, time spent on
coalescing
pages by buddy allocator can be reduced. With section size of 256MB,
hot
add latency of a single section shows improvement from
On 1/14/19 7:44 AM, Juergen Gross wrote:
> Commit f94c8d11699759 ("sched/clock, x86/tsc: Rework the x86 'unstable'
> sched_clock() interface") broke Xen guest time handling across
> migration:
>
> [ 187.249951] Freezing user space processes ... (elapsed 0.001 seconds) done.
> [ 187.251137] OOM
Hi Peter,
On 14/01/2019 13:16, Peter Zijlstra wrote:
> On Fri, Jan 11, 2019 at 06:32:58PM +, James Morse wrote:
>> On 10/01/2019 20:12, Peter Zijlstra wrote:
>>> On Thu, Jan 10, 2019 at 06:25:57PM +, James Morse wrote:
>>> The thing is, everything non-maskable (NMI like) really should not
In process_response_list() invoke the callback handler after unmapping
the DMA buffers. It ensures DMA data is synced form device to cpu
before the client code access the data from callback handler.
Fixes: c9613335bf4f ("crypto: cavium/nitrox - Added AEAD cipher support")
Signed-off-by:
The documented way to build kselftest is to run
make -C tools/testing/selftests
with an optional "O=..." parameter to specify the output directory.
However, all of the above assume you run make from the source directory.
while other make commands can simply be run from the output directory,
When building kselftest in a separate output directory:
/tmp/cc44s4yX.o: In function `socket_send_fd':
tools/testing/selftests/android/ion/ionutils.c:221: undefined reference to
`sendtosocket'
/tmp/cc44s4yX.o: In function `socket_receive_fd':
Currently there are rules to compile and link one or more C or
assembler source files into a full executable, and to assemble a single
assembler source into an object file.
Add a generic rule to compile a single C source file into an object
file, for reuse of object files in multiple executables.
The intel_pstate test doesn't contain any header files, so there is no
need to declare a rule for header dependencies.
Signed-off-by: Geert Uytterhoeven
---
tools/testing/selftests/intel_pstate/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git
"all" and the generic %.c dependency are already handled by the included
lib.mk.
Signed-off-by: Geert Uytterhoeven
---
tools/testing/selftests/sparc64/drivers/Makefile | 4
1 file changed, 4 deletions(-)
diff --git a/tools/testing/selftests/sparc64/drivers/Makefile
When building kselftest in a separate output directory:
make[3]: *** No rule to make target 'common.o', needed by
'/tmp/kselftest/memfd/memfd_test'. Stop.
Fix this by explicitly listing common.o (in the output tree) in the
build targets (allowing the EXTRA_CLEAN rule to be dropped), and
When building kselftest in a separate output directory, the kernel
headers are still installed in the source directory, instead of in the
specified output directory.
Fix this by passing the expected path to the make subprocess.
Signed-off-by: Geert Uytterhoeven
---
Makefile | 2 +-
1 file
When building kselftest in a separate output directory, the individual
test directories end up in the root of the output directory, instead of
under tools/testing/selftests/.
Fix this by passing the expected path to the make subprocess.
Signed-off-by: Geert Uytterhoeven
---
Makefile | 4 ++--
When running "make kselftests":
make[3]: Entering directory 'tools/gpio'
Makefile:24: tools/build/Makefile.include: No such file or directory
make[3]: *** No rule to make target 'tools/build/Makefile.include'. Stop.
When building kselftest in a separate output directory, the gpio
Makefile:14: warning: overriding recipe for target 'clean'
../../lib.mk:137: warning: ignoring old recipe for target 'clean'
"all" and "clean" are already handled by the included lib.mk.
Signed-off-by: Geert Uytterhoeven
---
tools/testing/selftests/networking/timestamping/Makefile | 5
When building kselftest in a separate output directory, the seccomp_bpf
binary ends up in the source directory instead of in the output
directory, and the build of seccomp_benchmark fails:
make[5]: *** No rule to make target 'seccomp_benchmark', needed by 'all'.
Stop.
Fix this by declaring
Hi all,
This patch series contains several build fixes and cleanups for issues I
encountered when trying to cross-build an rtctest binary in a separate
output directory (like I use for all my kernel builds).
Most patches are independent. Exceptions are:
- Patch 3 depends on patch 2,
With gcc 7.3.0:
gpio-mockup-chardev.c: In function ‘get_debugfs’:
gpio-mockup-chardev.c:62:3: warning: ignoring return value of ‘asprintf’,
declared with attribute warn_unused_result [-Wunused-result]
asprintf(path, "%s/gpio", mnt_fs_get_target(fs));
On Fri, Jan 11, 2019 at 03:28:37PM -0800, Mike Kravetz wrote:
> Ok, I just wanted to ask the question. I've seen application code doing
> the 'mmap sufficiently large area' then unmap to get desired alignment
> trick. Was wondering if there was something we could do to help.
Application may
Hi Sam,
> -Original Message-
> From: Sam Ravnborg [mailto:sam.ravnb...@gmail.com] On Behalf Of Sam Ravnborg
> Sent: Saturday, January 12, 2019 10:33 PM
> To: Alex Deucher ; Alexey Brodkin
> ; Andrzej
> Hajda ; Benjamin Gaignard
> ; Chen Feng
> ; Christian Konig ; Daniel
> Vetter
> ;
On Mon, Jan 14, 2019 at 01:30:03PM +0100, Karoly Pados wrote:
> There is a bug in the current GPIO code for ftdi_sio: it failed to take USB
> autosuspend into account. If the device is in autosuspend, calls to
> usb_control_msg() fail with -EHOSTUNREACH. Because the standard value for
>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
match full slim device id instead of just product and manufacture code,
this will allow drivers to be much more specific to that device.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/core.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/slimbus/core.c
Here are some minor fixes to slimbus core for issues found while testing
wcd9335.
First one is make the slimbus core match full device id,
second one is to avoid using big lock in status callback function,
third one is to use status function rather than directly invoking the status
ops.
finally
Add missing spin lock intialization this also fixes the spinlock bad magic
warning.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/slimbus/core.c b/drivers/slimbus/core.c
index 8ffdc9876223..b2f07d2043eb 100644
---
use slim_device_update_status() instead of directly calling
the device_status() callback. Move slim_device_update_status() before
probe to avoid forward declaration too.
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/core.c | 37 ++---
1 file changed, 18
Calling device_status callback under a lock would prevent drivers
to do any slimbus trasactions which would invoke this lock like
get_laddr(). Remove this unnecessary lock!
Signed-off-by: Srinivas Kandagatla
---
drivers/slimbus/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
On 13/01/19 7:35 AM, Jens Axboe wrote:
> On 1/12/19 6:29 PM, john.hubb...@gmail.com wrote:
>> From: John Hubbard
>>
>> Commit 49e54187ae0b ("ata: libahci_platform: comply to PHY framework") uses
>> the PHY_MODE_SATA, but that enum had not yet been added. This caused a
>> build failure for me,
On 14/01/19 2:27 PM, Miquel Raynal wrote:
> Hi Olof,
>
> Olof Johansson wrote on Sat, 12 Jan 2019 19:57:12
> -0800:
>
>> On Sat, Jan 12, 2019 at 6:05 PM Jens Axboe wrote:
>>>
>>> On 1/12/19 6:29 PM, john.hubb...@gmail.com wrote:
From: John Hubbard
Commit 49e54187ae0b
On Mon, Jan 14, 2019 at 2:37 PM Peter Zijlstra wrote:
>
> On Thu, Jan 10, 2019 at 11:21:13AM +0100, Dmitry Vyukov wrote:
> > On Thu, Jan 10, 2019 at 5:04 AM Waiman Long wrote:
> > >
> > > Tetsuo Handa had reported he saw an incorrect "downgrading a read lock"
> > > warning right after a previous
This is a first attempt at implementing proper access to buffers
imported with dma-buf and used as reference frames for decoding
subsequent frames.
The main concern associated with this scenario was that memory could be
liberated while the buffer is not in a queued state. After careful
checking,
Because we need to request and release access to reference buffers
that are backed by a dma-buf import, keep track of the buffers used
as reference and add the appropriate calls in the device_run and
job_done m2m callbacks. The latter is introduced for this purpose.
Signed-off-by: Paul
Introduce helpers to request and release access to buffers that are
not currently selected as current output or capture buffers.
This is useful to ensure proper access to buffers imported via dma-buf
that are used as reference and thus require associated map/unmap calls
before access.
Introduce a new optional job_done operation, which allows calling back
to the driver when a job is done. Since the job might be completed
from interrupt context where some operations are not available, having
a callback from non-atomic context allows performing these operations
upon completion of
Access to reference frames that were imported from dma-buf was taken
care of and is no longer a pending item on the driver's TODO list.
Signed-off-by: Paul Kocialkowski
---
drivers/staging/media/sunxi/cedrus/TODO | 5 -
1 file changed, 5 deletions(-)
diff --git
On Thu, Jan 10, 2019 at 11:21:13AM +0100, Dmitry Vyukov wrote:
> On Thu, Jan 10, 2019 at 5:04 AM Waiman Long wrote:
> >
> > Tetsuo Handa had reported he saw an incorrect "downgrading a read lock"
> > warning right after a previous lockdep warning. It is likely that the
> > previous warning turned
On 1/10/19 7:17 PM, Marcos Paulo de Souza wrote:
> ping?
>
> On Sat, Dec 22, 2018 at 08:08:45AM -0200, Marcos Paulo de Souza wrote:
>> bio_alloc_bioset return a bio pointer or NULL, so we can avoid storing
>> the returned data into a new variable.
>>
>> Signed-off-by: Marcos Paulo de Souza
>>
to verify it, *
* and the root cause of the problem may be somewhere else. *
* Hope this helps! *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
next/master boot bisection: next-20190114 on sun8i-h2-plus-libretech-all-h3-cc
Hello,
On Fri 11 Jan 2019 at 19:55, Kevin Hilman wrote:
Martin Blumenstingl writes:
Hi,
some nit-picks as well as my Tested-by (in case it's not too late) below.
thank you for taking care of this!
You're welcome !
On Thu, Jan 10, 2019 at 4:40 PM Loys Ollivier
wrote:
Commit
I'm seeing series of e1000e resets (sometimes endless) at system boot
if something generates tx traffic at this time. In my case this is
netconsole who sends message "e1000e :02:00.0: Some CPU C-states
have been disabled in order to enable jumbo frames" from e1000e itself.
As result
Add devicetree binding documentation for PCIe in RC mode present in
AM654 SoC.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/pci/pci-keystone.txt | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Certain platforms like K2G reguires the outbound ATU window to be
aligned. The alignment size is already present in mem->page_size.
Use the alignment size present in mem->page_size to configre a
aligned ATU window. In order to raise an interrupt, CPU has to write
to address offset from the start
Explicitly set the PCIe mode to BOOTCFG_DEVCFG instead of always
relying on the default values. This is required when EP mode has to
be explicitly written to BOOTCFG_DEVCFG register.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/pci-keystone.c | 37 +++
Certain platforms like TI's AM654 doesn't have separate address space for
dbi2 instead they are accessed using the same address space as dbi
with some configuration bit set. In order to support such platforms,
add callbacks for accessing dbi2 address space.
Signed-off-by: Kishon Vijay Abraham I
Add const qualifier to struct dw_pcie_ep_ops member of
struct dw_pcie_ep.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/pci-dra7xx.c | 2 +-
drivers/pci/controller/dwc/pcie-artpec6.c | 2 +-
drivers/pci/controller/dwc/pcie-designware-plat.c | 2 +-
iatu_unroll_enabled flag is set only for Designware in host mode.
However iATU unroll can be applicable for endpoint mode too. Set
iatu_unroll_enabled flag in dw_pcie_setup which is common for
both host mode and endpoint mode.
Signed-off-by: Kishon Vijay Abraham I
---
Synopsys designware version >= 4.80 uses a separate register space
for programming ATU. The current code identifies if there exists a
separate register space by accessing the register address of ATUs
in designware version < 4.80. Accessing this address results in
abort in the case of K2G.
Fix it
TI's AM654x PCIe EP has a restriction that BAR_0 is mapped to
application registers. "PCIe Inbound Address Translation" section in
AM65x Sitara Processors TRM (SPRUID7 – April 2018) describes BAR0 is
reserved. Configure pci_endpoint_test to use BAR_2 instead.
Also set alignment to 64K since "PCIe
commit 834b9051992580ac8fd3966d023b ("misc: pci_endpoint_test: Add support
for PCI_ENDPOINT_TEST regs to be mapped to any BAR") while adding
test_reg_bar in order to map PCI_ENDPOINT_TEST regs to be mapped to any
BAR failed to update test_reg_bar in pci_endpoint_test. This results in
test_reg_bar
Add PCIe EP support for AM654x Platforms in pci-keystone.c
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/controller/dwc/Kconfig| 23 ++-
drivers/pci/controller/dwc/pci-keystone.c | 216 --
2 files changed, 223 insertions(+), 16 deletions(-)
diff --git
Configure RESBAR capability to advertise the smallest size (1MB) for
couple of reasons. A) Host side resource allocation of BAR fails for
larger sizes. B) Endpoint function driver does not allocate memory
for all supported sizes in RESBAR capability.
If and when there is a usecase required to add
SERDES connected to the PCIe controller in AM654 requires
power on reset enable (POR_EN) to be set in the SERDES. The
SERDES driver sets POR_EN in the reset ops and it has to be
invoked before init or enable ops. In order for SERDES driver
to set POR_EN, invoke phy_reset API in pci-keystone
701 - 800 of 1164 matches
Mail list logo
