From: Jagan Teki
Add support for Sound card and related codec(via i2c1) nodes
on Engicam GEAM6UL variant module boards.
Signed-off-by: Jagan Teki
---
Changes for v4:
- keep sound and related i2c1 on dts
Changes for v3:
- Replace fsl,imx-audio-sgtl5000 and use simple-audio-card
Changes for v2:
-
From: Jagan Teki
GEAM6UL SOM does have single module, it doesn't come with
any variants. Maintaining imx6ul-geam.dtsi make no sense
so move all devices from .dtsi into dts file and drop the same.
Signed-off-by: Jagan Teki
---
Changes for v4:
- New patch
arch/arm/boot/dts/imx6ul-geam-kit.dts |
From: Jagan Teki
usdhc1 is enabled and assigned pinctrl-0 on imx6ul-geam.dtsi
but same thing done on imx6ul-geam-kit.dts, so remove this
re-enabled node from the same.
Signed-off-by: Jagan Teki
---
Changes for v4:
- New patch
arch/arm/boot/dts/imx6ul-geam-kit.dts | 6 --
1 file changed, 6
From: Jagan Teki
Engicam SOM's with mounted on starter kits like icorem6(rqs), isiot
usually not explicitly named with -kit in dts file names and
instead Model has mentioned 'Starter kit' So apply the same rule
for geam SOM as well.
Signed-off-by: Jagan Teki
---
Changes for v4:
- New patch
ar
This way allocations like the NVMe HMB don't consume iomap space
Signed-off-by: Christoph Hellwig
---
Note: compile tested only, I stumbled over this when researching dma api
quirks for HMB support.
arch/arc/mm/dma.c | 42 +-
1 file changed, 29 insertion
On Fri, Jun 16, 2017 at 10:01:37AM +0530, Sumit Semwal wrote:
>
> make headers_install was missing, but it still didn't improve the
> build - here's the pastebin: https://paste.debian.net/971652/
>
Last time I saw similar kinds of errors gcc libraries were missing.
Can you try rerunning after
Hi Magnus,
On Thu, Jun 15, 2017 at 12:29 PM, Magnus Damm wrote:
> From: Magnus Damm
>
> The 32-bit ARM code gets updated to make use of ->of_xlate() and the
> code is shared between 64-bit and 32-bit ARM. The of_device_is_available()
> check gets dropped since it is included in of_iommu_xlate().
This way we can always pass DMA_ATTR_NON_CONSISTENT, the SNI mips version
will simply ignore the flag.
Signed-off-by: Christoph Hellwig
---
drivers/net/ethernet/i825xx/lasi_82596.c | 6 ++
drivers/net/ethernet/i825xx/lib82596.c | 9 +
drivers/net/ethernet/i825xx/sni_82596.c | 6 ++
No users left, everyone switched to the _attrs versions.
Signed-off-by: Christoph Hellwig
---
Documentation/DMA-API.txt| 30 --
arch/metag/include/asm/dma-mapping.h | 2 +-
arch/nios2/include/asm/dma-mapping.h | 2 +-
arch/tile/include/asm/dma-mapping.h
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
drivers/scsi/53c700.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/53c700.c b/drivers/scsi/53c700.c
index 95e32a47face..4b3b08025ef6 100644
dmam_alloc_noncoherent is a trivial wrapper around dmam_alloc_attrs,
that hardcodes one particular flag. Make the devres code more
flexible by allowing the callers to pass arbitrary flags.
Signed-off-by: Christoph Hellwig
---
Documentation/driver-model/devres.txt | 2 +-
drivers/base/dma-mappi
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
drivers/net/ethernet/amd/au1000_eth.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/drivers/net/ethernet/amd/au1000_eth.c
b/drivers/net/ether
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
drivers/tty/serial/mpsc.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/tty/serial/mpsc.c b/drivers/tty/serial/mpsc.c
index 1a60a2063e75..67ffe
Hi Magnus,
On Thu, Jun 15, 2017 at 12:29 PM, Magnus Damm wrote:
> Now when both 32-bit and 64-bit code inside the driver is using
> fwspec it is possible to replace the utlb handling with fwspec ids
> that get populated from ->of_xlate().
Thanks for your patch!
> --- 0013/drivers/iommu/ipmmu-vm
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
drivers/net/ethernet/seeq/sgiseeq.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/ethernet/seeq/sgiseeq.c
b/drivers/net/ethernet/seeq/sgiseeq
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
drivers/scsi/sgiwd93.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/sgiwd93.c b/drivers/scsi/sgiwd93.c
index 71b4b91d2215..80cfa93e407c 1
au1100fb is using managed dma allocations, so it doesn't need to
explicitly free the dma memory in the error path (and if it did
it would have to use the managed version).
Signed-off-by: Christoph Hellwig
---
drivers/video/fbdev/au1100fb.c | 4
1 file changed, 4 deletions(-)
diff --git a/d
On 06/16/2017 08:36 AM, Kishon Vijay Abraham I wrote:
On Friday 09 June 2017 01:34 AM, Rafał Miłecki wrote:
From: Rafał Miłecki
As explained in the commit 9200c6f177638 ("Revert "phy: Add USB3 PHY support
for Broadcom NSP SoC"") this module should be modified to use MDIO bus as
this is how PHY
Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
Signed-off-by: Christoph Hellwig
---
sound/mips/hal2.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/sound/mips/hal2.c b/sound/mips/hal2.c
index 00fc9241d266..17a78a93e885 1006
For many years we've had the dma_alloc_attrs API that is more flexible
than dma_alloc_noncoherent. This series moves the remaining users over
to the attrs API.
This function was never used since it was added.
Signed-off-by: Christoph Hellwig
---
Documentation/driver-model/devres.txt | 1 -
drivers/base/dma-mapping.c| 20
include/linux/dma-mapping.h | 2 --
3 files changed, 23 deletions(-)
diff --git a/Docum
Hi Jerome,
I'm just getting back to this; sorry for the late responses.
Your description of HMM talks about blocking CPU accesses when a page has been
migrated to device memory, and you treat that as a "given" in the HMM design.
Other than BAR limits, coherency between CPU and device caches a
On Jun 16 2017 or thereabouts, Zheng, Lv wrote:
> Hi,
>
> > From: linux-acpi-ow...@vger.kernel.org
> > [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Peter
> > Hutterer
> > Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID
> > switch exported by ACPI
> >
> > On Thu,
On Fri, 16 Jun 2017, Christoph Hellwig wrote:
> can you take a look at the generic patches as they are the required
> base for the block work?
It's next on my ever growing todo list
This patch makes use of ALIGN() to remove duplicate round-up code.
Signed-off-by: Canjiang Lu
---
mm/slab.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/mm/slab.c b/mm/slab.c
index 807d86c..69e08a4 100644
--- a/mm/slab.c
+++ b/mm/slab.c
@@ -2040,17 +2040,13 @@ stat
The setting of clocks and presets is currently done in probe only but
once deep PM support is added, it'll be needed in the resume function.
Let's create a function for this setting.
Signed-off-by: Quentin Schulz
---
drivers/mmc/host/sdhci-of-at91.c | 147 ++-
This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2
SoC's SDHCI controller.
When resuming from deepest state, it is required to restore preset
registers as the registers are lost since VDD core has been shut down
when entering deepest state on the SAMA5D2. The clocks need to be
On Thu, Jun 15 2017, Christoph Hellwig wrote:
> On Fri, Jun 16, 2017 at 03:54:30PM +1000, NeilBrown wrote:
>> Hi Jens,
>> I didn't hear back ... have you had a chance to look?
>> In case it helps, you can pull the full set, based on a recent Linus tree,
>> from
>> git://neil.brown.name/lin
On Fri, Jun 16, 2017 at 05:30:50PM +1000, NeilBrown wrote:
> I've pushed the new version to the same place. Do you actually want
> me to re-post all the patches?
I personally prefer to always have patches on the list, but I can't
speak for Jens of course.
perf/core: use context tstamp_data for skipped events on mux interrupt
By default, the userspace perf tool opens per-cpu task-bound events
when sampling, so for N logical events requested by the user, the tool
will open N * NR_CPUS events.
In the kernel, we mux events with a hrtimer, periodicall
Dell Latitude 3160 does not have keyboard backlight, but there is a
sysfs interface for it, which does nothing at all.
KBD_LED_OFF_TOKEN is the only token can be found. Since it doesn't have
KBD_LED_ON_TOKEN or KBD_LED_AUTO_*_TOKEN, it should be safe to assume it
does not support keyboard backligh
why isn't loop using kthread_create_worker()? Why isn't the less
throttle a flag to kthread_create_worker()? I hate all this open
coding..
Looks good,
Reviewed-by: Christoph Hellwig
Hi Alexander,
On 16 June 2017 at 12:44, Alexander Alemayhu wrote:
> Last time I saw similar kinds of errors gcc libraries were missing.
> Can you try rerunning after
>
> apt-get install -y gcc-multilib g++-multilib
Thanks, this was quite helpful, and so now bpf tests build on x86_64
with curre
Thanks!
You could remove
intstatus &= ~MASK_HDMI_INT;
in line 1289 as well.
Regards,
Mats Randgaard
On 15/06/2017, 18:49, "Gustavo A. R. Silva" wrote:
Remove useless variable assignment in function tc358743_isr().
The value stored in variable _intstatus_ at line 1299 is
overw
> On 15 Jun 2017, at 22:48, Eric Biggers wrote:
>
> On Thu, Jun 15, 2017 at 01:41:29PM -0700, Michael Halcrow wrote:
>>> static int validate_user_key(struct fscrypt_info *crypt_info,
>>> struct fscrypt_context *ctx, u8 *raw_key,
>>> - const char *prefix)
>>>
Hi, Benjamin
Let me just say something one more time.
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch
> exported by ACPI
>
> On Jun 16 2017 or thereabouts, Zheng, Lv wrote:
> > Hi,
> >
> > > From:
Ping for review
On 06/13/2017 02:27 PM, Wang Yafei wrote:
> V2 changes:
>
> - replace touchscreen properties according to the description in
> Documentation/devicetree/bindings/input/touchscreen/touchscreen.txt
>
> - Droped all compat stuff for older kernels
>
> - Removed Android stuff (EARLY_S
Hi!
On Friday 16 June 2017 15:35:39 Kai-Heng Feng wrote:
> Dell Latitude 3160 does not have keyboard backlight, but there is a
> sysfs interface for it, which does nothing at all.
>
> KBD_LED_OFF_TOKEN is the only token can be found. Since it doesn't have
> KBD_LED_ON_TOKEN or KBD_LED_AUTO_*_TOKE
Hi,
On Friday 16 June 2017 12:44 PM, Rafał Miłecki wrote:
> On 06/16/2017 08:36 AM, Kishon Vijay Abraham I wrote:
>> On Friday 09 June 2017 01:34 AM, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> As explained in the commit 9200c6f177638 ("Revert "phy: Add USB3 PHY support
>>> for Broadcom
On Friday 09 June 2017 01:34 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> As explained in the commit 9200c6f177638 ("Revert "phy: Add USB3 PHY support
> for Broadcom NSP SoC"") this module should be modified to use MDIO bus as
> this is how PHY is really attached.
>
> This should allow r
On 6/15/2017 5:57 PM, Horia Geantă wrote:
> On 6/2/2017 3:25 PM, David Gstir wrote:
>> Hi!
>>
>> While testing fscrypt's filename encryption, I noticed that the
>> implementation
>> of cts(cbc(aes)) is broken when the CAAM hardware crypto driver is enabled.
>> Some digging showed that the refactor
On Fri, Jun 16, 2017 at 07:57:00AM +, Horia Geantă wrote:
>
> Commit 0605c41cc53ca ("crypto: cts - Convert to skcipher") appends
> CRYPTO_TFM_REQ_MAY_BACKLOG to the original crypto request flags for the
> last block - when calling cts_cbc_encrypt().
> Is it really needed?
Yes, because at this
On 06/16/2017 12:23 AM, Pavel Machek wrote:
Fix compilation of isp.c
Signed-off-by: Pavel Machek
diff --git a/drivers/media/platform/omap3isp/isp.c
b/drivers/media/platform/omap3isp/isp.c
index 4ca3fc9..b80debf 100644
--- a/drivers/media/platform/omap3isp/isp.c
+++ b/drivers/media/plat
[Please try to trim the context you are replying to]
On Fri 16-06-17 12:20:58, Wei Yang wrote:
> On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
[...]
> > /*
> >+ * Return true if [start_pfn, start_pfn + nr_pages) range has a non-empty
> >+ * intersection with the given zone
> >+ */
On Thu 15-06-17 15:42:23, David Rientjes wrote:
> On Fri, 16 Jun 2017, Michal Hocko wrote:
>
> > I am sorry but I have really hard to make the oom reaper a reliable way
> > to stop all the potential oom lockups go away. I do not want to
> > reintroduce another potential lockup now.
>
> Please sho
* Adrian Hunter wrote:
> On 15/06/17 20:55, Kim Phillips wrote:
> >
> > Signed-off-by: Kim Phillips
>
> Looks like defines for sampling support that got mixed in with earlier
> patches. We can always put them back when we need them, so:
>
> Acked-by: Adrian Hunter
The non-existent changel
On Jun 16 2017 or thereabouts, Zheng, Lv wrote:
> Hi, Benjamin
>
> Let me just say something one more time.
>
> > From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
[snip]
> > > > >
> > > > > We can see:
> > > > > "logind" has already implemented a timeout, and will not respond lid
Well, I love this patch a lot. We don't need to put the hotadd memory in one
zone and move it to another. This looks great!
On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
>From: Michal Hocko
>
[...]
+
>+void move_pfn_range_to_zone(struct zone *zone,
>+ unsigned long st
From: Joerg Roedel
When booting into a kdump kernel, suppress IO_PAGE_FAULTs by
default for all devices. But allow the faults again when a
domain is assigned to a device.
Signed-off-by: Joerg Roedel
---
drivers/iommu/amd_iommu.c | 3 ++-
drivers/iommu/amd_iommu_init.c | 9 +
dri
* kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit c88d71508e36b514413464bd2e01f96f34583a0e
> Author: Kirill A. Shutemov
> AuthorDa
Hi Kishon/Bjorn,
What is correct Setting for these two PCIECTRL_DRA7XX_CONF_IRQSTATUS_MSI
and
PCIECTRL_DRA7XX_CONF_IRQSTATUS_MAIN register.
Value of register After change:
register[PCIECTRL_DRA7XX_CONF_IRQSTATUS_MSI] = LEG_EP_INTERRUPTS | MSI
= 0x1f
On 06/15/2017 06:31 PM, Christoph Hellwig wrote:
> On Wed, Jun 07, 2017 at 11:45:27AM +0200, Johannes Thumshirn wrote:
>> A patch for nvmetcli and nvme-cli will follow shortly.
>
> Can you send them out? Especially as I want to debug why I don't seem
> to get a uuid attribute with nvme-loop despi
Recent change to use cpuhp_setup_state_cpuslocked() with commit
fe2a5cd8aa03 ("ARM/hw_breakpoint: Use cpuhp_setup_state_cpuslocked()")
missed to change the related paired cpuhp_remove_state_nocalls_cpuslocked().
Now if arch_hw_breakpoint_init() fails, we get "WARNING: possible recursive
locking de
On Jun 16 2017 or thereabouts, Masaki Ota wrote:
> From: Masaki Ota
> - Support PTP Stick and Touchpad device.
> - This Touchpad is Precision Touchpad(PTP),
> and Stick Pointer data is the same as Mouse.
> - Stick Pointer works as Mouse.
>
> Signed-off-by: Masaki Ota
> ---
Looks godd to me:
Re
The description of tracepoint_probe_register duplicates
with tracepoint_probe_register_prio. This patch cleans up
the description.
Cc: Steven Rostedt
Cc: Ingo Molnar
Signed-off-by: "Lee, Chun-Yi"
---
kernel/tracepoint.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kern
On 2017-06-15 00:33:12 [+0200], Jason A. Donenfeld wrote:
> There's a potential race that I fixed in my v5 of that patch set, but
> Ted only took v4, and for whatever reason has been to busy to submit
> the additional patch I already posted showing the diff between v4&v5.
> Hopefully he actually ge
* Florian Fainelli [170615 16:27]:
> On 06/15/2017 04:21 PM, Florian Fainelli wrote:
> > ARM's fncpy implementation is actually suitable for a large number of
> > platforms since the only assumption it makes is just the function's
> > alignment (8 bytes) which also happens to fulfil other architec
On Thu, Jun 15, 2017 at 06:01:02PM +, Gabriele Paoloni wrote:
> Hi Mika
>
> > -Original Message-
> > From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> > ow...@vger.kernel.org] On Behalf Of Mika Westerberg
> > Sent: 13 June 2017 21:04
> > To: Gabriele Paoloni
> > Cc: Lorenzo Pi
On Thu, Jun 08, 2017 at 02:59:07PM +0100, Robin Murphy wrote:
> Hi Christoph,
>
> On 08/06/17 14:25, Christoph Hellwig wrote:
> > DMA_ERROR_CODE is not a public API and will go away soon. dma dma-iommu
> > driver already implements a proper ->mapping_error method, so it's only
> > using the value
On Fri, Jun 09, 2017 at 02:20:42PM +0200, Geert Uytterhoeven wrote:
> Hi Christoph,
>
> On Thu, Jun 8, 2017 at 3:25 PM, Christoph Hellwig wrote:
> > This implementation is simply bogus - hexagon only has a simple
>
> openrisc?
Yeah.
On Fri 16-06-17 09:54:34, Tetsuo Handa wrote:
[...]
> And the patch you proposed is broken.
Thanks for your testing!
> --
> [ 161.846202] Out of memory: Kill process 6331 (a.out) score 999 or
> sacrifice child
> [ 161.850327] Killed process 6331 (a.out) total-vm:4172kB, anon-rss:84kB,
On Thu, Jun 08, 2017 at 03:43:14PM +0100, Russell King - ARM Linux wrote:
> BOn Thu, Jun 08, 2017 at 03:25:50PM +0200, Christoph Hellwig wrote:
> > +static int dmabounce_mapping_error(struct device *dev, dma_addr_t dma_addr)
> > +{
> > + if (dev->archdata.dmabounce)
> > + return 0;
>
>
On Thu, Jun 15, 2017 at 11:44 PM, Andy Lutomirski wrote:
> On Tue, May 30, 2017 at 9:05 AM, Paolo Bonzini wrote:
>>
>>
>> On 30/05/2017 17:58, Roman Penyaev wrote:
>>> Indeed, what is left is eventually take it from SS.RPL. J.
>>
>> Ahah! :) But I only suggested that in specific cases.
>>
>>> Bu
On Mon, Jun 12, 2017 at 10:06:26AM +0200, Andreas Larsson wrote:
> Yes, it is needed. LEON systems are AMBA bus based. The common case here is
> DMA over AMBA buses. Some LEON systems have PCI bridges, but in general
> CONFIG_PCI is not a given.
Ok, and even for AMBA we use the pci ops, so I'll
On Fri 16-06-17 16:11:42, Wei Yang wrote:
> Well, I love this patch a lot. We don't need to put the hotadd memory in one
> zone and move it to another. This looks great!
>
> On Mon, May 15, 2017 at 10:58:24AM +0200, Michal Hocko wrote:
> >From: Michal Hocko
> >
> [...]
> +
> >+void move_pfn_range
On 15/06/17 17:17, Jerome Brunet wrote:
> This patch series adds support for the GPIO interrupt controller found on
> Amlogic's meson SoC families.
>
> Unlike what the name suggests, this controller is not part of the SoC
> GPIO subsystem. It is a separate controller from which can watch almost
>
On Fri, Jun 09, 2017 at 12:22:48AM +1000, Julian Calaby wrote:
> I'm guessing there's a few places that have DMA ops but DMA isn't
> actually supported. Why not have a common method for this, maybe
> "dma_not_supported"?
It's not common at all. Except for sbus all dma API user first
call set_dma_
On Fri, 16 Jun 2017 09:17:09 +0200,
Christoph Hellwig wrote:
>
> Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
>
> Signed-off-by: Christoph Hellwig
Should I take this one through sound git tree, or would you prefer
taking all through another?
In the latter case,
On Fri, Jun 16, 2017 at 10:49:56AM +0200, Takashi Iwai wrote:
> On Fri, 16 Jun 2017 09:17:09 +0200,
> Christoph Hellwig wrote:
> >
> > Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
> >
> > Signed-off-by: Christoph Hellwig
>
> Should I take this one through sound git
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID switch
> exported by ACPI
>
> On Jun 16 2017 or thereabouts, Zheng, Lv wrote:
> > Hi, Benjamin
> >
> > Let me just say something one more time.
> >
> > >
This patch fixes the phy loopback self_test failed issue. when
Marvell Phy Module is loaded, it will powerdown fiber when doing
phy loopback self test, which cause phy loopback self_test fail.
Signed-off-by: Lin Yun Sheng
---
drivers/net/ethernet/hisilicon/hns/hns_ethtool.c | 16 ++--
On Fri, 16 Jun 2017 10:51:47 +0200,
Christoph Hellwig wrote:
>
> On Fri, Jun 16, 2017 at 10:49:56AM +0200, Takashi Iwai wrote:
> > On Fri, 16 Jun 2017 09:17:09 +0200,
> > Christoph Hellwig wrote:
> > >
> > > Use dma_alloc_attrs directly instead of the dma_alloc_noncoherent wrapper.
> > >
> > > S
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-qup.c b/drivers/spi/spi-qup.c
index d3ccf53..363bd43 100644
--- a/drivers/spi/spi-qup.c
+++ b/drivers/spi/spi-qup.c
@@ -336,6 +336
Signed-off-by: Andy Gross
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/spi/spi-qup.c b/drivers/spi/spi-qup.c
index 272e48e..d3ccf53 100644
--- a/drivers/spi/spi-qup.c
+++ b/drivers/spi/sp
This let's you write more to the SPI bus than 64K-1 which is important
if the block size of a SPI device is >= 64K or some other device wants
to do something larger.
This has the benefit of completely removing spi_message from the spi-qup
transactions
Signed-off-by: Matthew McClintock
Signed-off
Add output-enable generic pin configuration property.
This properties allows enabling/disabling pin's output capabilities
without actually driving any value on the line.
Signed-off-by: Jacopo Mondi
---
So, after that many discussions I'm now sending this, that only adds a new
flag used to enable
Much like the block mode changes, we are breaking up DMA transactions
into 64K chunks so we can reset the QUP engine.
Signed-off-by: Matthew McClintock
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 104 --
1 file changed, 76 ins
This is in preparation for handling transactions larger than
64K-1 bytes in block mode, which is currently unsupported and
quietly fails.
We need to break these into two functions 1) prep is
called once per spi_message and 2) io_config is called
once per spi-qup bus transaction
This is just refac
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-qup.c b/drivers/spi/spi-qup.c
index 363bd43..2124815 100644
--- a/drivers/spi/spi-qup.c
+++ b/drivers/spi/spi-qup.c
@@ -310,8 +310,8 @@ static int
Currently the QUP Version v1 does not work with DMA so added
the support for the same.
1. It uses ADM DMA which requires TX and RX CRCI
2. DMA channel initialization need to be done after setting
block size for having valid values in maxburst
3. QUP mode should be DMOV instead of BAM.
Signed-o
This patch fixes an issue where a SPI transaction has completed, but the
done condition is missed. This occurs because at the time of interrupt the
MAX_INPUT_DONE_FLAG is not asserted. However, in the process of reading
blocks of data from the FIFO, the last portion of data comes in.
The opflags
Take specific sgl and nent to be prepared. This is in
preparation for splitting DMA into multiple transacations, this
contains no code changes just refactoring.
Signed-off-by: Matthew McClintock
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 25 ++---
1 fi
DMA transactions should only only need to call io_config only once, but
block mode might call it several times to setup several transactions so
it can handle reads/writes larger than the max size per transaction, so
we move the call to the do_ functions.
This is just refactoring, there should be n
This patch corrects the behavior of the BLOCK
transactions. During block transactions, the controller
must be read/written to in block size transactions.
Signed-off-by: Andy Gross
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 151 +++--
Wait to signal done until we get all of the interrupts we are expecting
to get for a transaction. If we don't wait for the input done flag, we
can be in between transactions when the done flag comes in and this can
mess up the next transaction.
While here cleaning up the code which sets controlle
To operate in DMA mode, the buffer should be aligned and
the size of the transfer should be a multiple of block size
(for v1). And the no. of words being transferred should
be programmed in the count registers appropriately.
Signed-off-by: Andy Gross
Signed-off-by: Varadarajan Narayanan
---
dri
Use different 'completion' structures to track the completion
of DMA Tx/Rx and PIO.
Signed-off-by: Andy Gross
Signed-off-by: Varadarajan Narayanan
---
drivers/spi/spi-qup.c | 41 -
1 file changed, 24 insertions(+), 17 deletions(-)
diff --git a/drivers/sp
> "Serge E. Hallyn" hat am 15. Juni 2017 um 05:05
> geschrieben:
>
>
> On Wed, Jun 14, 2017 at 08:27:40AM -0400, Stefan Berger wrote:
> > On 06/13/2017 07:55 PM, Serge E. Hallyn wrote:
> > >Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
> > >> If all extended
> > >>attributes were to supp
Enable chip select support for QUP versions later than v1.
The chip select support was broken in QUP version 1. Hence
the chip select support was removed earlier in commit
4a8573abe965115bc5b064401fd669b74e985258. Since the chip
select support is functional in recent versions of QUP,
re-enabling it
Commit-ID: 92b0a1416be587b87c8ff489b6a74fd929048ca7
Gitweb: http://git.kernel.org/tip/92b0a1416be587b87c8ff489b6a74fd929048ca7
Author: Kees Cook
AuthorDate: Thu, 15 Jun 2017 08:20:35 -0500
Committer: Ingo Molnar
CommitDate: Fri, 16 Jun 2017 10:50:59 +0200
objtool: Add fortify_panic as
v2:
Incorporate feedback from Andy Gross, Sricharan, Stanimir Varbanov
Modified the QUP-v1 dma completion sequence to QUP-v2 as per feedback.
Removed code that used controller->xfer to identify extra interrupts,
since with the fixes done to handle i/o completion we
The following changes since commit b29794ec95c6856b316c2295904208bf11ffddd9:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2017-06-06
14:30:17 -0700)
are available in the git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-for-4.12
for you to fe
On Fri, Jun 16, 2017 at 10:59 AM, Jacopo Mondi
wrote:
> Add output-enable generic pin configuration property.
> This properties allows enabling/disabling pin's output capabilities
> without actually driving any value on the line.
>
> Signed-off-by: Jacopo Mondi
Acked-by: Geert Uytterhoeven
Gr{
On Thu, Jun 15, 2017 at 01:03:41PM -0700, Moritz Fischer wrote:
> > +static int machxo2_write(struct fpga_manager *mgr, const char *buf,
> > +size_t count)
> > +{
> > + struct spi_device *spi = mgr->priv;
> > + struct spi_message msg;
> > + struct spi_trans
FYI, this patch didn't seem to make it through to the list, probably
because it was too large.
It might be good to just introduce the internal flags field first,
populate it with the translated flags, then switch users over to
it, and last but not least remove the old flags field and the MS_*
valu
> On 16 Jun 2017, at 10:53, Zheng, Lv wrote:
>
> Hi,
>
>> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
>> Subject: Re: [systemd-devel] [WIP PATCH 0/4] Rework the unreliable LID
>> switch exported by ACPI
>>
>>> On Jun 16 2017 or thereabouts, Zheng, Lv wrote:
>>> Hi, Benjam
On 13 June 2017 at 16:49, Eric Anholt wrote:
> Daniel Stone writes:
>> I posted a DRI3 v1.1 patch series which can advertise and also transit
>> modifiers directly under X11, and have also typed up the support for
>> Wayland which is working just fine with Weston from git. If you
>> implement DRI
On Fri, Jun 16, 2017 at 01:10:10AM +0300, Alexey Budankov wrote:
> On 15.06.2017 22:56, Mark Rutland wrote:
> >On Thu, Jun 15, 2017 at 08:41:42PM +0300, Alexey Budankov wrote:
> >>This series of patches continues v2 and addresses captured comments.
> >>Specifically this patch replaces pinned_group
On Thu, Jun 8, 2017 at 3:09 PM, Jerome Brunet wrote:
> Add Tsin A pins to bank DV and X.
> We don't have a driver for the tsin yet but since the tsin A pinmux is
> enabled by default at boot time, declaring this pinmux is required to
> properly operate on GPIOX.
>
> Without this change, GPIOX 8,
1 - 100 of 798 matches
Mail list logo
