On Wed, Jun 13, 2018 at 05:37:35PM +0100, Ben Hutchings wrote:
> On Wed, 2018-06-13 at 10:30 -0600, Keith Busch wrote:
> > Thank you very much the catching that. This particular patch is indeed
> > not correct without the following:
> >
> > 161b8be2bd6ab ("nvme-pci: initialize queue memory
The debug UART is very useful to have. I2C10 is enabled as an example
of a I2C port we can talk on for now. Eventually we'll want to put
peripherals under it.
Signed-off-by: Douglas Anderson
Reviewed-by: Bjorn Andersson
Tested-by: Bjorn Andersson
---
Changes in v2:
- Got rid of all sleep
This adds nodes to SDM845-dtsi for all the I2C ports, all the SPI
ports, and UART9. Note that I2C / SPI / UART are a bit strange on
sdm845 because each "serial engine" has 4 pins associated with it and
depending on which firmware has been loaded into the serial engine
(loaded by the BIOS) the
If rtsx_probe() fails to allocate dev->chip, then NULL pointer
dereference occurs at release_everything()->rtsx_release_resources().
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Vasilyev
---
v2: Add error handling into rtsx_probe based on Dan Carpenter's
> + } else {
> + while ((lsr & BOTH_EMPTY) != BOTH_EMPTY) {
> + lsr = serial_in(p, UART_LSR);
> + cpu_relax();
> + }
> + }
This still needs a timeout in case some kind of
On Wed, Jun 13, 2018 at 7:55 PM, Anton Vasilyev wrote:
> If rtsx_probe() fails to allocate dev->chip, then NULL pointer
> dereference occurs at release_everything()->rtsx_release_resources().
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
You forgot to adjust subject and
On Wed, Jun 13, 2018 at 06:47:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:73fcb1a370c7 Merge branch 'akpm' (patches from Andrew)
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16d7082780
> kernel
Hi Matt,
On 13/06/18 16:47, Matt Sealey wrote:
Hi Suzuki,
Why not use “unit”?
I believe we had this discussion years ago about numbering serial ports
and sdhci (i.e. how do you know it’s UART0 or UART1 from just the address?
Some SoC’s don’t address sequentially *or* in a forward direction)
On Wed, Jun 13, 2018 at 10:56:32AM -0600, Keith Busch wrote:
> On Wed, Jun 13, 2018 at 05:37:35PM +0100, Ben Hutchings wrote:
> > On Wed, 2018-06-13 at 10:30 -0600, Keith Busch wrote:
> > > Thank you very much the catching that. This particular patch is indeed
> > > not correct without the
On Wed, Jun 13, 2018 at 7:42 AM, Valentin Schneider
wrote:
> On 13/06/18 05:13, Tony Lindgren wrote:
>> * John Stultz [180612 22:15]:
>>> Hey Folks,
>>> I noticed with linus/master wifi wasn't coming up on HiKey960. I
>>> bisected it down and it seems to be due to:
>>>
>>> 60f36637bbbd
Hi Linus,
Please pull the following Kselftest update 2 for 4.18-rc1
This second Kselftest update for Linux 4.18-rc1:
- fixes a signedness bug in cgroups test
- adds ppc support for kprobe args tests
diff is attached.
thanks,
-- Shuah
Improve readability of comedi_nsamples_left:
a) Reduce nesting by using more return statements.
b) Declare variables scans_left and samples_left at start of function.
c) Change type of scans_Left to unsigned long long to avoid cast.
Signed-off-by: Chris Opperman
---
Changes v5:
a) Moved
Thanks for the clean up, Shuah. Looks good to me.
Tom
On 06/12/2018 05:24 PM, Shuah Khan (Samsung OSG) wrote:
Delete RUN_TESTS and EMIT_TESTS overrides and use common defines in
lib.mk. Common defines work just fine and there is no need to define
custom overrides.
Signed-off-by: Shuah Khan
If the test_printf module is loaded before the crng is initialized, the
plain 'p' tests will fail because the printed address will not be hashed
and the buffer will contain "(ptrval)" or "(ptrval)" instead
(64-bit vs 32-bit).
Since we cannot wait for the crng to be initialized for an
Thanks, Shuah!
Tom
On 06/12/2018 05:23 PM, Shuah Khan (Samsung OSG) wrote:
sparc64 test fails with the following errors on non-sparc64 systems. Fix
the Makefile to do nothing on non-sparc64 systems to suppress the errors:
make run_tests
adi-test.c: Assembler messages:
adi-test.c:302: Error:
blem found by an experimental cocinelle script
Patch was compile tested with: multi_v7_defconfig + ARCH_ZYNQ=y,
COMPILE_TEST=y, PCIE_XILINX=y
(with one sparse warning though not related to the change proposed)
Patch is against 4.17.0 (localversion-next is next-20180613)
drivers/pci/controller/pcie-xilinx.
On 06/12/2018 10:40 PM, Keerthy wrote:
Currently the driver assumes that the interrupts are continuous
and does platform_get_irq only once and assumes the rest are continuous,
instead call platform_get_irq for all the interrupts and store them
in an array for later use.
Signed-off-by:
Hi,
On Tue, Jun 12, 2018 at 10:09 AM, Karthikeyan Ramasubramanian
wrote:
> From: Rajendra Nayak
>
> Add the qup uart node and geni se instance needed to
> support the serial console on the MTP.
>
> Signed-off-by: Rajendra Nayak
> Signed-off-by: Karthikeyan Ramasubramanian
> ---
>
Hi Linus,
2018-06-14 1:03 GMT+09:00 Linus Torvalds :
> On Wed, Jun 13, 2018 at 8:55 AM Linus Torvalds
> wrote:
>>
>> On Wed, Jun 13, 2018 at 7:47 AM Masahiro Yamada
>> wrote:
>> >
>> > Please pull more Kbuild updates.
>>
>> Pulled. However, I notice a few oddities.
>
> Oh, and one actual bug:
Hi,
On Tue, Jun 12, 2018 at 10:09 AM, Karthikeyan Ramasubramanian
wrote:
> Add one instance of GENI based I2C master controller to enable testing
> I2C driver using EEPROM slave.
>
> Signed-off-by: Karthikeyan Ramasubramanian
> Reviewed-by: Douglas Anderson
> ---
>
On Wed, Jun 13, 2018 at 05:34:02AM -0700, Matthew Wilcox wrote:
> Allow users of the IDR to use the XArray lock for their own
> synchronisation purposes. The IDR continues to rely on the caller to
> handle locking, but this lets the caller use the lock embedded in the
> IDR data structure instead
Subject: [PATCH v3] staging: rts5208: add error handling into rtsx_probe
If rtsx_probe() fails to allocate dev->chip, then release_everything()
will crash on uninitialized dev->cmnd_ready complete.
Patch adds error handling into rtsx_probe.
Found by Linux Driver Verification project
On 13/06/18 19:26, Chris Opperman wrote:
Hi Dan/Ian,
Noted your comments regarding additional text, thanks! Just curious whether
the "scissors" format given at the link below is valid?
https://kernelnewbies.org/PatchTipsAndTricks
It is given as an alternative to placing additional text below
Hi,
On 13/06/18 16:13, Ryan Grachek wrote:
> These properties are required for compatibility with runtime PM.
> Without these properties, MMC host controller will not be aware
> of power capabilities. When the wlcore driver attempts to power
> on the device, it will erroneously fail with -EACCES.
If rtsx_probe() fails to allocate dev->chip, then release_everything()
will crash on uninitialized dev->cmnd_ready complete.
Patch adds error handling into rtsx_probe.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Anton Vasilyev
---
v3: fix subject and commit
Punit Agrawal writes:
[...]
>
> CONFIG_HAVE_MEMORYLESS node is not enabled on arm64 which means we end
> up returning the original node in the fallback path.
>
> Xie, does the below patch help? I can submit a proper patch if this
> fixes the issue for you.
>
> -- >8 --
> Subject: [PATCH]
On Wed, Jun 13, 2018 at 04:58:15PM +0200, Greg Kroah-Hartman wrote:
> On Wed, Jun 13, 2018 at 04:09:57PM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jun 13, 2018 at 06:48:05AM -0700, Guenter Roeck wrote:
> > > On 06/12/2018 09:51 AM, Greg Kroah-Hartman wrote:
> > > > This is the start of the
On 13/06/18 18:14, Chris Opperman wrote:
Improve readability of comedi_nsamples_left:
a) Reduce nesting by using more return statements.
b) Declare variables scans_left and samples_left at start of function.
c) Change type of scans_Left to unsigned long long to avoid cast.
Signed-off-by: Chris
Hi.
2018-06-12 20:50 GMT+09:00 Nadav Amit :
> Using macros for inline assembly improves both readability and
> compilation decisions that are distorted by big assembly blocks that use
> alternative sections. Compile macros.S and use it to assemble all C
> files. Currently, only x86 will use it.
On 06/12/2018 07:38 AM, Kirill A. Shutemov wrote:
> VMAs with different KeyID do not mix together. Only VMAs with the same
> KeyID are compatible.
>
> Signed-off-by: Kirill A. Shutemov
> ---
> include/linux/mm.h | 7 +++
> mm/mmap.c | 3 ++-
> 2 files changed, 9 insertions(+), 1
On Wed, Jun 13, 2018 at 10:29 AM Masahiro Yamada
wrote:
>
> I cannot come up with a name better than CC_STACKPROTECTOR_STRONG.
How about just calling it STACKPROTETOR_STRONG and leaving it at that?
Make the "CC_HAVE_xyz" model for compiler feature tests, but when
actually picking an actual
In an early version of the I2C patch that was posted to the list the
default I2C frequency (if none was specified) was 400 kHz. There was
debate on the list and we decided that it would be more consistent
with the rest of i2c if we defaulted to 100 kHz. ...but we never
updated the bindings.
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Pages for encrypted VMAs have to be allocated in a special way:
> we would need to propagate down not only desired NUMA node but also
> whether the page is encrypted.
>
> It complicates not-so-trivial routine of huge page allocation in
>
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Pages encrypted with different encryption keys are not subject to KSM
> merge. Otherwise it would cross security boundary.
This needs a much stronger explanation. Which KeyID would be used for
access in the new direct mappings? What actually
On 6/12/18 10:58 AM, Tadeusz Struk wrote:
Currently the TPM driver only supports blocking calls, which doesn't allow
asynchronous IO operations to the TPM hardware.
This patch changes it and adds support for nonblocking write and a new poll
function to enable applications, which want to take
These properties are required for compatibility with runtime PM.
Without these properties, MMC host controller will not be aware
of power capabilities. When the wlcore driver attempts to power
on the device, it will erroneously fail with -EACCES. This fixes
a regression found here:
On 06/13/2018 10:55 AM, J Freyensee wrote:
>> + /*
>> + * If in nonblocking mode schedule an async job to send
>> + * the command return the size.
>> + * In case of error the err code will be returned in
>> + * the subsequent read call.
>> + */
>> + if (file->f_flags &
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> For encrypted memory, we need to allocated pages for a specific
> encryption KeyID.
"allocate" ^
> There are two cases when we need to allocate a page for encryption:
>
> - Allocation for an encrypted VMA;
>
> -
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Encrypted VMA will have KeyID stored in vma->vm_page_prot. This way we
"An encrypted VMA..."
> don't need to do anything special to setup encrypted page table entries
> and don't need to reserve space for KeyID in a VMA.
>
> This patch changes
Hello Sudeep,
Thanks for review comments.
On 6/13/2018 4:56 PM, Sudeep Holla wrote:
On 12/06/18 12:02, Taniya Das wrote:
Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
SoCs. This is required for managing the cpu frequency transitions which are
controlled by
Hi Linus,
2018-06-14 2:49 GMT+09:00 Linus Torvalds :
> On Wed, Jun 13, 2018 at 10:29 AM Masahiro Yamada
> wrote:
>>
>> I cannot come up with a name better than CC_STACKPROTECTOR_STRONG.
>
> How about just calling it STACKPROTETOR_STRONG and leaving it at that?
Good idea!
> Make the
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> +bool vma_is_encrypted(struct vm_area_struct *vma)
> +{
> + return pgprot_val(vma->vm_page_prot) & mktme_keyid_mask;
> +}
> +
> +int vma_keyid(struct vm_area_struct *vma)
> +{
> + pgprotval_t prot;
> +
> + if (!vma_is_anonymous(vma))
Removing the paragraph about writing to the Free Software Foundation's
mailing address from the sample GPL notice according to checkpatch
request.
In addition, updating the year and adding a license tag.
Reviewed-by: Xavier Deguillard
Signed-off-by: Nadav Amit
---
drivers/misc/vmw_balloon.c |
Currently, when all modules, including VMCI and VMware balloon are built
into the kernel, the initialization of the balloon happens before the
VMCI is probed. As a result, the balloon fails to initialize the VMCI
doorbell, which it uses to get asynchronous requests for balloon size
changes.
The
This patch-set addresses minor issues and bugs in the VMware balloon
driver. Patches 3-7 address bugs that were not reported by customers,
but we would like to get them to 4.18 if possible.
We will send separately later a patch-set with new features to be set on
top of this set.
Nadav Amit (7):
When balloon batching is not supported by the hypervisor, the guest
frame number (GFN) must fit in 32-bit. However, due to a bug, this check
was mistakenly ignored. In practice, when total RAM is greater than
16TB, the balloon does not work currently, making this bug unlikely to
happen.
Fixes:
When vmballoon_vmci_init() sets a doorbell using VMCI_DOORBELL_SET, for
some reason it does not consider the status and looks at the result.
However, the hypervisor does not update the result - it updates the
status.
Fixes: 48e3d668b790 ("VMware balloon: Enable notification via VMCI")
If the hypervisor sets 2MB batching is on, while batching is cleared,
the balloon code breaks. In this case the legacy mechanism is used with
2MB page. The VM would report a 2MB page is ballooned, and the
hypervisor would only take the first 4KB.
While the hypervisor should not report such
> +int page_keyid(const struct page *page)
> +{
> + if (mktme_status != MKTME_ENABLED)
> + return 0;
> +
> + return lookup_page_ext(page)->keyid;
> +}
> +EXPORT_SYMBOL(page_keyid);
Please start using a proper X86_FEATURE_* flag for this. It will give
you all the fancy static
Philip Moltman is no longer a maintainer of the VMware balloon. Setting
Nadav Amit as one instead.
Reviewed-by: Xavier Deguillard
Signed-off-by: Nadav Amit
---
MAINTAINERS| 2 +-
drivers/misc/vmw_balloon.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Valentin,
On Wed, Jun 13, 2018 at 12:34 PM, Valentin Schneider
wrote:
> Hi,
>
> On 13/06/18 16:13, Ryan Grachek wrote:
>> These properties are required for compatibility with runtime PM.
>> Without these properties, MMC host controller will not be aware
>> of power capabilities. When the
Since commit 33d268ed0019 ("VMware balloon: Do not limit the amount of
frees and allocations in non-sleep mode."), the allocations are not
increased, and therefore balloon inflation rate limiting is in practice
broken.
While we can restore rate limiting, in practice we see that it can
result in
On Wed, Jun 13, 2018 at 04:03:53AM -0700, Nadav Amit wrote:
> Removing the paragraph about writing to the Free Software Foundation's
> mailing address from the sample GPL notice according to checkpatch
> request.
>
> In addition, updating the year and adding a license tag.
>
> Reviewed-by:
On Wed, Jun 13, 2018 at 04:03:55AM -0700, Nadav Amit wrote:
> When balloon batching is not supported by the hypervisor, the guest
> frame number (GFN) must fit in 32-bit. However, due to a bug, this check
> was mistakenly ignored. In practice, when total RAM is greater than
> 16TB, the balloon
at 11:20 AM, Greg Kroah-Hartman wrote:
> On Wed, Jun 13, 2018 at 04:03:53AM -0700, Nadav Amit wrote:
>> Removing the paragraph about writing to the Free Software Foundation's
>> mailing address from the sample GPL notice according to checkpatch
>> request.
>>
>> In addition, updating the year
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> prep_encrypted_page() also takes care about zeroing the page. We have to
> do this after KeyID is set for the page.
This is an implementation detail that has gone unmentioned until now but
has impacted at least half a dozen locations in previous
at 11:21 AM, Greg Kroah-Hartman wrote:
> On Wed, Jun 13, 2018 at 04:03:55AM -0700, Nadav Amit wrote:
>> When balloon batching is not supported by the hypervisor, the guest
>> frame number (GFN) must fit in 32-bit. However, due to a bug, this check
>> was mistakenly ignored. In practice, when
On Fri, May 25 2018 at 19:08 -0600, David Collins wrote:
Hello Rajendra,
On 05/25/2018 03:01 AM, Rajendra Nayak wrote:
+
+ to_active_sleep(pd, pd->corner, _corner, _sleep_corner);
+
+ if (peer && peer->enabled)
+ to_active_sleep(peer, peer->corner, _corner,
+
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Separate MKTME enumaration from enabling. We need to postpone enabling
> until initialization is complete.
^ enumeration
> The new helper mktme_disable() allows to disable MKTME even if it's
s/to disable/disabling/
>
On Wed, Jun 13, 2018 at 8:13 AM, Ryan Grachek wrote:
> These properties are required for compatibility with runtime PM.
> Without these properties, MMC host controller will not be aware
> of power capabilities. When the wlcore driver attempts to power
> on the device, it will erroneously fail
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Kernel need to have a way to access encrypted memory. We are going to
"The kernel needs"...
> use per-KeyID direct mapping to facilitate the access with minimal
> overhead.
What are the security implications of this approach?
> Direct mapping
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> arch/x86/include/asm/mktme.h | 6 +
> arch/x86/mm/init_64.c| 6 +
> arch/x86/mm/mktme.c | 444 +++
> 3 files changed, 456 insertions(+)
Can we not do any better than 400 lines of new
> diff --git a/arch/x86/include/asm/mktme.h b/arch/x86/include/asm/mktme.h
> index efc0d4bb3b35..d6edcabacfc7 100644
> --- a/arch/x86/include/asm/mktme.h
> +++ b/arch/x86/include/asm/mktme.h
> @@ -43,6 +43,9 @@ void mktme_disable(void);
> void setup_direct_mapping_size(void);
> int
Make calculation of the size of the inline name in struct proc_dir_entry
automatic, rather than having to manually encode the numbers and failing to
allow for lockdep.
Require a minimum inline name size of 33+1 to allow for names that look
like two hex numbers with a dash between.
Reported-by:
The current logic incorrectly calculates the LLC ID from the APIC ID.
Unless specified otherwise, the LLC ID should be calculated from
the count order of the number of threads sharing cache.
Fixes: 68091ee7ac3c ("Calculate last level cache ID from number of sharing
threads")
Signed-off-by:
On Tue, 12 Jun 2018 10:39:14 +1000
"Tobin C. Harding" wrote:
> +/* Make pointers available for printing early in the boot sequence. */
> +static int debug_boot_weak_hash __ro_after_init;
> +EXPORT_SYMBOL(debug_boot_weak_hash);
> +
> +static int __init debug_boot_weak_hash_enable(char *str)
> +{
Allow users of the IDR to use the XArray lock for their own
synchronisation purposes. The IDR continues to rely on the caller to
handle locking, but this lets the caller use the lock embedded in the
IDR data structure instead of allocating their own lock.
Signed-off-by: Matthew Wilcox
---
On 06/12/2018 07:39 AM, Kirill A. Shutemov wrote:
> Add new config option to enabled/disable Multi-Key Total Memory
> Encryption support.
>
> MKTME uses MEMORY_PHYSICAL_PADDING to reserve enough space in per-KeyID
> direct mappings for memory hotplug.
Isn't it really *the* direct mapping
On Wed, Jun 13, 2018 at 11:30:57AM -0600, Jason Gunthorpe wrote:
> Hmm, what do I need to apply this?
>
> drivers/infiniband/core/mad.c: In function ‘ib_register_mad_agent’:
> drivers/infiniband/core/mad.c:387:34: error: ‘struct idr’ has no member named
> ‘idr_xa’; did you mean ‘idr_rt’?
>
On Wed, 2018-02-28 at 09:19 +, Roger Pau Monne wrote:
> From: Roger Pau Monne
>
> [ Upstream commit 910f8befdf5bccf25287d9f1743e3e546bcb7ce0 ]
>
> Current cleanup in the error path of xen_bind_pirq_msi_to_irq is
> wrong. First of all there's an off-by-one in the cleanup loop, which
> can
Fixed style line length warning detected by checkpatch.pl in the file
ssv_dnp.c.
Signed-off-by: Javier Martinez
---
drivers/staging/comedi/drivers/ssv_dnp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/ssv_dnp.c
Rob Herring writes:
> On Mon, Jun 11, 2018 at 10:22:10PM +0200, Robert Jarzmik wrote:
>> This adds a binding for the Marvell PXA audio complex, available in
>> pxa2xx and pxa3xx variants.
>> +Required properties:
>> + - compatible: "marvell,pxa2xx-ac97"
>
> Don't use wildcards in compatible
Fixed style line length warning detected by checkpatch.pl in the file
ssv_dnp.c.
Signed-off-by: Javier Martinez
---
drivers/staging/comedi/drivers/ssv_dnp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/comedi/drivers/ssv_dnp.c
On Tue, 12 Jun 2018 10:39:14 +1000
"Tobin C. Harding" wrote:
> diff --git a/lib/vsprintf.c b/lib/vsprintf.c
> index c445f9f28760..6d2479eb7c2b 100644
> --- a/lib/vsprintf.c
> +++ b/lib/vsprintf.c
> @@ -1651,6 +1651,18 @@ char *device_node_string(char *buf, char *end, struct
> device_node *dn,
On Wed, Jun 13, 2018 at 08:26:43PM +0200, Chris Opperman wrote:
> Hi Dan/Ian,
>
> Noted your comments regarding additional text, thanks! Just curious whether
> the "scissors" format given at the link below is valid?
>
> https://kernelnewbies.org/PatchTipsAndTricks
>
> It is given as an
On Tue, Jun 12, 2018 at 6:44 PM, Linus Torvalds
wrote:
> On Tue, Jun 12, 2018 at 4:36 PM Kees Cook wrote:
>>
>> - Treewide conversions of allocators to use either 2-factor argument
>> variant when available, or array_size() and array3_size() as needed (Kees)
>
> Ok, some of this smells just a
Hi Borys,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.17 next-20180613]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Linus,
The following changes since commit 29dcea88779c856c7dc92040a0c01233263101d4:
Linux 4.17 (2018-06-03 14:15:21 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.18-rc1
for you to fetch changes up to
On 06/12/2018 03:54 PM, Rob Herring wrote:
> On Thu, Jun 7, 2018 at 12:53 PM, Scott Branden
> wrote:
>> Hi Rob,
>>
>> Could you please kindly comment on change below.
>>
>> It allows board variants to be added easily via a simple define for
>> different number of SATA ports.
>>
>>
>>
>> On
Bus recovery should reset the engine and force clock the bus 9 times
to recover most situations.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/i2c/busses/i2c-fsi.c b/drivers/i2c/busses/i2c-fsi.c
index
Since there are many ports per master, each with it's own adapter and
chardev, we need some locking to prevent transfers from changing the
master state while other transfers are in progress.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 16
1 file changed, 12
Add register definitions for FSI-attached I2C master and functions to
access those registers over FSI. Add an FSI driver so that our I2C bus
is probed up during an FSI scan.
Signed-off-by: Eddie James
---
drivers/i2c/busses/Kconfig | 11 ++
drivers/i2c/busses/Makefile | 1 +
Execute I2C transfers from the FSI-attached I2C master. Use polling
instead of interrupts as we have no hardware IRQ over FSI.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 195 ++-
1 file changed, 193 insertions(+), 2 deletions(-)
diff
Document the bindings.
Signed-off-by: Eddie James >
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/i2c/i2c-fsi.txt | 40 +++
1 file changed, 40 insertions(+)
create mode 100644 Documentation/devicetree/bindings/i2c/i2c-fsi.txt
diff --git
Add abort procedure for failed transfers. Add engine and bus reset
procedures to recover from as many faults as possible.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 179 +++
1 file changed, 179 insertions(+)
diff --git
This series adds an algorithm for an I2C master physically located on an FSI
slave device. The I2C master has multiple ports, each of which may be connected
to an I2C slave. Access to the I2C master registers is achieved over FSI bus.
Due to the multi-port nature of the I2C master, the driver
Add and initialize I2C adapters for each port on the FSI-attached I2C
master. Ports for each master are defined in the devicetree.
Signed-off-by: Eddie James
---
drivers/i2c/busses/i2c-fsi.c | 90
1 file changed, 90 insertions(+)
diff --git
On Tue, Jun 12, 2018 at 9:33 PM, Roman Gushchin wrote:
> On Tue, Jun 12, 2018 at 09:08:27PM -0700, John Stultz wrote:
>> On Tue, Jun 12, 2018 at 6:02 PM, John Stultz wrote:
>> > Hey Tejun,
>> > With the current linus/master, I'm able to fairly regularly trip
>> > OOPSes (two examples below) in
On 13 June 2018 at 11:07, Suzuki K Poulose wrote:
> Hi Matt,
>
> On 13/06/18 16:47, Matt Sealey wrote:
>>
>> Hi Suzuki,
>>
Why not use “unit”?
I believe we had this discussion years ago about numbering serial ports
and sdhci (i.e. how do you know it’s UART0 or UART1 from just
On Tue, 12 Jun 2018, Vlastimil Babka wrote:
> The __alloc_pages_slowpath() function has for a long time contained code to
> ignore node restrictions from memory policies for high priority allocations.
> The current code that resets the zonelist iterator however does effectively
> nothing after
GENERIC_ASHLDI3, GENERIC_ASHRDI3, and GENERIC_LSHRDI3 were renamed to
GENERIC_LIB_ASHLDI3, GENERIC_LIB_ASHRDI3, and GENERIC_LIB_LSHRDI3
without making the matching changes in arch/nds32. This results in
the following build errors.
nds32le-linux-ld: kernel/time/timekeeping.o:
in function
On 06/12/2018 01:21 PM, Ray Jui wrote:
> Fix I2C controller interrupt to use IRQ_TYPE_LEVEL_HIGH for Broadcom
> Cygnus SoC
>
> Fixes: b51c05a331ff ("ARM: dts: add I2C device nodes for Broadcom Cygnus")
This appears to be the only one that is truly needed here, the two
others below probably just
On 06/12/2018 01:21 PM, Ray Jui wrote:
> Fix PCIe controller interrupt to use IRQ_TYPE_LEVEL_HIGH for Broadcom
> Cygnus SoC
>
> Fixes: cd590b50a936 ("ARM: dts: enable PCIe support for Cygnus")
This one is valid
> Fixes: 0f0b21a83ad2 ("ARM: dts: Move all Cygnus peripherals into axi
> bus")
>
On Wed, Jun 13, 2018 at 12:40:23PM -0700, John Stultz wrote:
> On Tue, Jun 12, 2018 at 9:33 PM, Roman Gushchin wrote:
> > On Tue, Jun 12, 2018 at 09:08:27PM -0700, John Stultz wrote:
> >> On Tue, Jun 12, 2018 at 6:02 PM, John Stultz
> >> wrote:
> >> > Hey Tejun,
> >> > With the current
[ adding Andrew, Christoph, and linux-mm ]
On Wed, Jun 13, 2018 at 12:33 PM, Joe Gorse wrote:
> Greetings,
>
> Please CC answers & comments to this email. Thanks! =)
>
> Our build is breaking as of
> commit e7638488434415aa478e78435cac8f0365737638
> Author: Dan Williams
> Date: Wed May 16
- On Jun 13, 2018, at 12:14 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Jun 13, 2018, at 7:48 AM, heiko carstens heiko.carst...@de.ibm.com
> wrote:
[...]
>>
>> Is there any documentation available of what is the exact semantics of the
>> functions that have to be
Em Mon, Jun 11, 2018 at 09:31:52AM +0200, Thomas Richter escreveu:
> On s390 the socket identifier assigned to a CPU identifier is
> random and (depending on the configuration of the LPAR) may be higher
> than the CPU identifier. This is currently not supported.
>
> Fix this by allowing arbitrary
Em Tue, Jun 12, 2018 at 09:28:09AM +0530, Ravi Bangoria escreveu:
> On 06/11/2018 04:10 PM, Sandipan Das wrote:
> > For some cases, the callchain provided by the kernel may be
> > empty. So, the callchain ip filtering code will cause a crash
> > if we do not check whether the struct ip_callchain
On 13/06/2018 17:54, Pandruvada, Srinivas wrote:
> On Tue, 2018-06-12 at 14:00 +0200, Daniel Lezcano wrote:
>> Initially, the cpu_cooling device for ARM was changed by adding a new
>> policy inserting idle cycles. The intel_powerclamp driver does a
>> similar action.
>>
>> Instead of implementing
Em Mon, Jun 11, 2018 at 11:34:22AM +0200, Jiri Olsa escreveu:
> Adding optional 'valid' callback for events tests in
> parse-events object, so we don't try to parse PMUs,
> which are not supported.
>
> Following line is displayed for skipped test:
>
> running test 52 'intel_pt//u'... SKIP
801 - 900 of 1044 matches
Mail list logo
