On Thu, Sep 26, 2019 at 01:49:09PM +0200, Maciej Falkowski wrote:
>
> On 9/24/19 5:20 PM, Krzysztof Kozlowski wrote:
> > On Tue, Sep 24, 2019 at 05:01:46PM +0200, Marek Szyprowski wrote:
> >> From: Maciej Falkowski
> >>
> >> Convert Samsung Exynos5433 TM2(E) audio complex with WM5110 codec to
On Wed, Sep 25, 2019 at 08:49:17PM -0500, Eric W. Biederman wrote:
> Frederic Weisbecker writes:
>
> > On Sat, Sep 14, 2019 at 07:35:02AM -0500, Eric W. Biederman wrote:
> >> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> >> index 69015b7c28da..668262806942 100644
> >> ---
On Thu, Sep 26, 2019 at 01:03:29AM +0200, Aleksa Sarai wrote:
> A common pattern for syscall extensions is increasing the size of a
> struct passed from userspace, such that the zero-value of the new fields
> result in the old kernel behaviour (allowing for a mix of userspace and
> kernel vintages
On Wed, 2019-09-25 at 18:45 +0200, Peter Zijlstra wrote:
> On Wed, Sep 25, 2019 at 11:18:47AM -0400, Qian Cai wrote:
> > On Wed, 2019-09-25 at 11:31 +0200, Peter Zijlstra wrote:
> > > On Fri, Sep 13, 2019 at 12:27:44PM -0400, Qian Cai wrote:
> > > > -> #3 (batched_entropy_u32.lock){-.-.}:
> > > >
On Tue 24-09-19 08:20:22, Alexander Duyck wrote:
> On Tue, Sep 24, 2019 at 7:23 AM Michal Hocko wrote:
> >
> > On Wed 18-09-19 10:52:25, Alexander Duyck wrote:
> > [...]
> > > In order to try and keep the time needed to find a non-reported page to
> > > a minimum we maintain a "reported_boundary"
On 9/26/19 11:56 AM, Vincenzo Frascino wrote:
> On 9/26/19 9:06 AM, Catalin Marinas wrote:
>> On Thu, Sep 26, 2019 at 07:03:50AM +0100, Vincenzo Frascino wrote:
>>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>>> index 37c610963eee..afe8c948b493 100644
>>> --- a/arch/arm64/Kconfig
>>> +++
> -Original Message-
> From: Colin King
> Sent: Thursday, September 26, 2019 2:23 PM
> To: Belgazal, Netanel ; Bshara, Saeed
> ; Machulsky, Zorik ; David S .
> Miller ; Kiyanovski, Arthur ;
> Jubran, Samih ; net...@vger.kernel.org
> Cc: kernel-janit...@vger.kernel.org;
Runtime powermanagement is added for PCI driver.
When there is no activity for at least 10 secs driver
suspends automatically.Runtime- Suspend and resume Stub functions
are added.
Signed-off-by: Ravulapati Vishnu vardhan rao
Reviewed-by: Vijendar Mukunda
---
sound/soc/amd/raven/pci-acp3x.c |
RAVEN has multiple I2S instances:BT and SP.But only BT is enabled.
Now I2S SP instance also gets enabled with this patch.
Signed-off-by: Ravulapati Vishnu vardhan rao
Reviewed-by: Vijendar Mukunda
---
sound/soc/amd/raven/acp3x-i2s.c | 216 +---
ACP power gating should be handled by ACP-PCI driver.
This patch moves the power gating logic into ACP-PCI driver.
This Power gating helps ACP to enter into D3 when there
is no activity on I2S.
Signed-off-by: Ravulapati Vishnu vardhan rao
Signed-off-by: Vijendar Mukunda
---
Use of_device_get_match_data() since all platforms should now use DT
bindings. AVR32 architecture has been removed in
commit 26202873bb51 ("avr32: remove support for AVR32 architecture").
Signed-off-by: Claudiu Beznea
---
drivers/rtc/Kconfig | 1 +
drivers/rtc/rtc-at91rm9200.c | 19
DMA driver should have only dma ops.Removed all DAI related.
Refactoring the code added new file contianing only DAI ops.
Signed-off-by: Ravulapati Vishnu vardhan rao
Reviewed-by: Vijendar Mukunda
---
sound/soc/amd/raven/Makefile| 2 +
sound/soc/amd/raven/acp3x-i2s.c | 289
On Thu, 26 Sep 2019 01:37:29 +0200
Dávid Bolvanský wrote:
> GCC C frontend does not warn, GCC C++ FE does. https://godbolt.org/z/_sczyM
>
> So I (we?) think there is something weird in gcc frontends.
>
> >> I can't think of a case that this warning is a bug (maybe David can
> explain more),
Removed platform based endpoint registering.
Now Registering DMA and multiple I2S BT playback
endpoint devices automatically by using MFD framework.
Signed-off-by: Ravulapati Vishnu vardhan rao
Reviewed-by: Vijendar Mukunda
---
sound/soc/amd/raven/acp3x.h | 54 ---
On Wed 2019-09-18 17:25:55, Jean-Jacques Hiblot wrote:
> Use the managed API of the LED class (devm_led_classdev_register()
> instead of led_classdev_register()).
> This allows us to remove the code used to track-and-destroy the LED devices
>
> Signed-off-by: Jean-Jacques Hiblot
> Reviewed-by:
On Wed 2019-09-18 17:25:56, Jean-Jacques Hiblot wrote:
> Use devm_led_classdev_register_ext() to pass the fwnode to the LED core.
> The fwnode can then be used by the firmware core to create meaningful
> names.
>
> Signed-off-by: Jean-Jacques Hiblot
Acked-by: Pavel Machek
On Thu, Sep 26, 2019 at 09:54:37AM +0200, Hans Andersson wrote:
> From: Hans Andersson
>
> The Micrel KSZ9031 PHY may fail to establish a link when the Asymmetric
> Pause capability is set. This issue is described in a Silicon Errata
> (DS8691D or DS8692D), which advises to always
On 26/09/19 12:43 PM, Baolin Wang wrote:
> Hi Adrian and Ulf,
>
> On Thu, 19 Sep 2019 at 13:59, Baolin Wang wrote:
>>
>> Hi All,
>>
>> Now the MMC read/write stack will always wait for previous request is
>> completed by mmc_blk_rw_wait(), before sending a new request to hardware,
>> or queue a
On Thu, Sep 26, 2019 at 10:23 AM Simon Horman wrote:
> On Wed, Sep 25, 2019 at 04:03:53PM -0500, Navid Emamdoost wrote:
> > In rcar_sysc_pd_init when looping over info->areas errors may happen but
> > the error handling path does not clean up the intermediate allocated
> > memories.
> >
> > This
Alexander Shishkin writes:
> Peter Zijlstra writes:
>
>> On Tue, Jun 19, 2018 at 01:47:25PM +0300, Alexander Shishkin wrote:
>>> Right, the SW stuff may then race with event_function_call() stuff. Hmm.
>>> For the HW stuff, I'm hoping that some kind of a sleight of hand may
>>> suffice. Let me
On Thu, 2019-09-26 at 14:00 +0200, Rafał Miłecki wrote:
> > You can't seriously be suggesting that the driver doesn't *have* enough
> > information - everything passed through it :)
>
> Precisely: it doesn't store (cache) enough info.
But nothing stops it (the driver) from doing so!
> In
Pavel
On 9/26/19 6:10 AM, Pavel Machek wrote:
Hi!
diff --git a/Documentation/leds/leds-class-multicolor.rst
b/Documentation/leds/leds-class-multicolor.rst
new file mode 100644
index ..87a1588d7619
--- /dev/null
+++ b/Documentation/leds/leds-class-multicolor.rst
@@ -0,0 +1,96 @@
From: Maciej Falkowski
Convert Samsung Exynos5433 TM2(E) audio complex with WM5110 codec to
newer dt-schema format.
Signed-off-by: Maciej Falkowski
Signed-off-by: Marek Szyprowski
---
v2:
- Added type and description and removed number of items from 'model' property.
Best regards,
Maciej
From: Maciej Falkowski
Convert Samsung Exynos Odroid XU3/XU4 audio complex with MAX98090 codec
to newer dt-schema format.
'clocks' property is unneeded in the bindings and is left undefined in
'properties'.
'samsung,audio-widgets' and 'samsung,audio-routing' are optional from driver
On 26.09.2019 13:55, Johannes Berg wrote:
On Thu, 2019-09-26 at 13:52 +0200, Rafał Miłecki wrote:
Indeed my main concert is AP mode. I'm afraid that cfg80211 doesn't
cache all settings, consider e.g. nl80211_start_ap(). It builds
struct cfg80211_ap_settings using info from nl80211 message and
On 20.09.2019 16:01, Jouni Malinen wrote:
On Fri, Sep 20, 2019 at 03:37:08PM +0200, Rafał Miłecki wrote:
Hardware or firmware instability may result in unusable wiphy. In such
cases usually a hardware reset is needed. To allow a full recovery
kernel has to indicate problem to the user space.
Jacek
On 9/25/19 5:00 PM, Jacek Anaszewski wrote:
Dan,
On 9/25/19 7:46 PM, Dan Murphy wrote:
Update the lp5523 to allow the use of the multi color framework.
Signed-off-by: Dan Murphy
---
drivers/leds/Kconfig | 1 +
drivers/leds/leds-lp5523.c| 13
From: Colin Ian King
The goto statement is indented incorrectly, remove the extraneous tab.
Signed-off-by: Colin Ian King
---
drivers/scsi/csiostor/csio_mb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/scsi/csiostor/csio_mb.c b/drivers/scsi/csiostor/csio_mb.c
Resending from my subscribed e-mail
On 20.09.2019 16:01, Jouni Malinen wrote:
> On Fri, Sep 20, 2019 at 03:37:08PM +0200, Rafał Miłecki wrote:
>> Hardware or firmware instability may result in unusable wiphy. In such
>> cases usually a hardware reset is needed. To allow a full recovery
>> kernel
Jacek
On 9/25/19 4:34 PM, Jacek Anaszewski wrote:
Dan,
On 9/25/19 7:46 PM, Dan Murphy wrote:
Update the DT binding to include the properties to use the
multicolor framework for the devices that use the LP55xx
framework.
Signed-off-by: Dan Murphy
CC: Tony Lindgren
CC: "Benoît Cousson"
CC:
On Thu, 2019-09-26 at 13:52 +0200, Rafał Miłecki wrote:
>
> Indeed my main concert is AP mode. I'm afraid that cfg80211 doesn't
> cache all settings, consider e.g. nl80211_start_ap(). It builds
> struct cfg80211_ap_settings using info from nl80211 message and
> passes it to the driver
Jacek
On 9/25/19 4:27 PM, Jacek Anaszewski wrote:
Dan,
On 9/25/19 7:46 PM, Dan Murphy wrote:
+
+static int lp50xx_brightness_set(struct led_classdev *cdev,
+enum led_brightness brightness)
+{
+ struct lp50xx_led *led = container_of(cdev, struct
Jacek
On 9/25/19 4:31 PM, Jacek Anaszewski wrote:
Dan,
On 9/25/19 7:46 PM, Dan Murphy wrote:
Update the document to be consistent in case when using LED.
s/LED/"LED"/.
ACK
This should be capital throughout the document.
Signed-off-by: Dan Murphy
---
On Thu 26-09-19 07:19:27, Qian Cai wrote:
>
>
> > On Sep 26, 2019, at 3:26 AM, Michal Hocko wrote:
> >
> > OK, this is using for_each_online_cpu but why is this a problem? Have
> > you checked what the code actually does? Let's say that online_pages is
> > racing with cpu hotplug. A new CPU
From: Lars-Peter Clausen
The PGA Slew Time control allows to configure the rate with which the PGA
gain control ramps up/down to the target setting.
The PGA slew control is done via the ALC Control 0 register. There are 2
bits on that reg, that control PGA slew time, while the other bits
From: Lars-Peter Clausen
The adau1761 has a automatic level control block that can adjust the gain
for the differential input PGA. This patch adds ALSA controls for enabling
and changing the parameter settings for the ALC.
Signed-off-by: Lars-Peter Clausen
Signed-off-by: Alexandru Ardelean
[Hmm, this one somehow slipped through. sorry about that]
On Tue 16-07-19 13:24:59, Johannes Weiner wrote:
> On Mon, Jul 15, 2019 at 03:35:27PM -0700, Andrew Morton wrote:
> > On Mon, 28 Jan 2019 21:52:40 + Roman Gushchin wrote:
> >
> > > > Hmm, this isn't really a common situation that I'd
On 9/24/19 5:20 PM, Krzysztof Kozlowski wrote:
> On Tue, Sep 24, 2019 at 05:01:46PM +0200, Marek Szyprowski wrote:
>> From: Maciej Falkowski
>>
>> Convert Samsung Exynos5433 TM2(E) audio complex with WM5110 codec to newer
>> dt-schema format.
>>
>> Signed-off-by: Maciej Falkowski
>>
On 9/25/2019 10:45 AM, Navid Emamdoost wrote:
In sdma_init if rhashtable_init fails the allocated memory for
tmp_sdma_rht should be released.
Signed-off-by: Navid Emamdoost
---
drivers/infiniband/hw/hfi1/sdma.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Jacek
On 9/25/19 4:12 PM, Jacek Anaszewski wrote:
Dan,
On 9/25/19 7:46 PM, Dan Murphy wrote:
Introduce a multicolor class that groups colored LEDs
within a LED node.
The multi color class groups monochrome LEDs and allows controlling two
aspects of the final combined color: hue and
On 19-09-26 10:17, Adam Thomson wrote:
> On 26 September 2019 09:10, Marco Felsch wrote:
>
> > On 19-09-25 16:18, Adam Thomson wrote:
> > > On 25 September 2019 16:52, Marco Felsch wrote:
> > >
> > > > Hi Adam,
> > > >
> > > > On 19-09-24 09:23, Adam Thomson wrote:
> > > > > On 17 September 2019
From: Colin Ian King
The complete call is indented incorrectly, remove the extraneous tabs.
Signed-off-by: Colin Ian King
---
drivers/spi/spi-fsl-lpspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-fsl-lpspi.c b/drivers/spi/spi-fsl-lpspi.c
index
On Thu, Sep 26, 2019 at 11:06:39AM +, Ardelean, Alexandru wrote:
> On Thu, 2019-09-26 at 11:10 +0300, Dan Carpenter wrote:
> > [External]
> >
> > The "t" variable is unsigned so it can't be less than zero. We really
> > are just trying to prevent divide by zero bugs so just checking against
> --- a/include/linux/entry-common.h
> +++ b/include/linux/entry-common.h
[...]
> +#define EXIT_TO_GUESTMODE_WORK
> \
> + (_TIF_NEED_RESCHED | _TIF_SIGPENDING | _TIF_NOTIFY_RESUME | \
> + ARCH_EXIT_TO_GUESTMODE_WORK)
[...]
> ---
Add pci_epc_ops to map physical address to MSI address and return MSI
data. The physical address is an address in the outbound region. This is
required to implement doorbell functionality of NTB (non transparent
bridge) wherein EPC on either side of the interface (primary and
secondary) can
Remove unused pci_epf_match_device() function added in pci-epf-core.c
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/endpoint/pci-epf-core.c | 16
include/linux/pci-epf.h | 2 --
2 files changed, 18 deletions(-)
diff --git
> On 25 Sep 2019, at 19:34, Paolo Bonzini wrote:
>
> KVM was incorrectly checking vmcs12->host_ia32_efer even if the "load
> IA32_EFER" exit control was reset. Also, some checks were not using
> the new CC macro for tracing.
>
> Cleanup everything so that the vCPU's 64-bit mode is
Add device tree bindings for PCI endpoint NTB function device.
Signed-off-by: Kishon Vijay Abraham I
---
.../bindings/pci/endpoint/pci-epf-ntb.txt | 31 +++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetree/bindings/pci/endpoint/pci-epf-ntb.txt
In the case of standard endpoint functions, only one endpoint
controller (EPC) will be associated with an endpoint function
(EPF). However for providing NTB (non transparent bridge)
functionality, two EPCs should be associated with a single EPF.
Add support to associate secondary EPC with EPF.
On Wed, 2019-09-25 at 16:46 -0700, Ira Weiny wrote:
> On Tue, Sep 24, 2019 at 08:26:20AM +1000, Dave Chinner wrote:
> > On Mon, Sep 23, 2019 at 12:08:53PM -0700, Ira Weiny wrote:
> > > Since the last RFC patch set[1] much of the discussion of supporting RDMA
> > > with
> > > FS DAX has been
From: Colin Ian King
There memset is indented incorrectly, remove the extraneous tabs.
Signed-off-by: Colin Ian King
---
drivers/net/ethernet/amazon/ena/ena_eth_com.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/amazon/ena/ena_eth_com.c
Like paRAM slots, channels could be used by other cores and in this case
we need to make sure that the driver do not alter these channels.
Handle the generic dma-channel-mask property to mark channels in a bitmap
which can not be used by Linux and convert the legacy rsv_chans if it is
provided by
> On Sep 26, 2019, at 3:26 AM, Michal Hocko wrote:
>
> OK, this is using for_each_online_cpu but why is this a problem? Have
> you checked what the code actually does? Let's say that online_pages is
> racing with cpu hotplug. A new CPU appears/disappears from the online
> mask while we are
Make the dma-channel-mask to be usable for controllers with more than 32
channels.
Signed-off-by: Peter Ujfalusi
---
Documentation/devicetree/bindings/dma/dma-common.yaml | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git
Signed-off-by: Alexandru Ardelean
---
drivers/iio/imu/adis.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/iio/imu/adis.c b/drivers/iio/imu/adis.c
index 7468294d1776..5e28464ea05b 100644
--- a/drivers/iio/imu/adis.c
+++ b/drivers/iio/imu/adis.c
@@ -404,15
Hi,
Changes since v2:
- Fix dma-common.yaml documentation patch and extend the description of the
dma-channel-mask array
- The edma documentation now includes information on the dma-channel-mask array
size for EDMAs with 32 or 64 channels
Changes since v1:
- Extend the common
This change removes the use of indio_dev's mlock in favor using the state
lock from the ADIS library.
The set_freq() & get_freq() hooks are unlocked, so they require specific
locking. That is because in some cases the get_freq() hook is used in
combination with adis16400_set_filter().
In cases
The reset routine may also be important to be protected by the state-lock
and grouped with other operations, so create an unlocked version, so that
this can be done.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/imu/adis.c | 8
include/linux/iio/imu/adis.h | 19
The initial startup routine is called by some ADIS drivers during probe,
and before registering with IIO. Normally, userspace should not be able to
do any access to the device (as there shouldn't be any available).
This change extends the state lock to the entire initial-startup routine.
This replaces indio_dev's mlock with the state lock/mutex from the ADIS
library.
The __adis16136_get_freq() function has been prefixed to mark it as
unlocked. The adis16136_{set,get}_filter() functions now hold the state
lock for all the ops that they do.
Signed-off-by: Alexandru Ardelean
---
It's the only operation that does 2 operations (a read & a write), so the
unlocked functions can be used under a single state lock.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/imu/adis16480.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git
Similarly to paRAM slots, channels can be used by other cores.
The common dma-channel-mask property can be used for specifying the
available channels.
Signed-off-by: Peter Ujfalusi
---
Documentation/devicetree/bindings/dma/ti-edma.txt | 8
1 file changed, 8 insertions(+)
diff --git
There is a general effort for cleaning up `indio_dev->mlock` usage in IIO
drivers. As part of that some ADIS drivers also need to do that.
This changeset does a little more, by reworking the `txrx_lock` from the
ADIS library to be used as a general `state_lock` to protect state between
This one also gets re-used in certain operations, so it makes sense to
have an unlocked version of this to group it with other
reads/writes/operations to have a single lock for the whole state change.
Signed-off-by: Alexandru Ardelean
---
drivers/iio/imu/adis.c | 8
The adis_enable_irq() does a read & a write. This change keeps a lock for
the duration of both operations vs for each op.
The change is also needed in adis16480, since that has it's own
implementation for adis_enable_irq().
Signed-off-by: Alexandru Ardelean
---
drivers/iio/imu/adis.c | 17
The lock can be extended a bit to protect other elements that are not
particular to just TX/RX. Another idea would have been to just add a new
`state_lock`, but that would mean 2 locks which would be redundant, and
probably cause more potential for dead-locks.
What will be done in the next
This will allow more flexible control to group reads & writes into a single
lock (particularly the state_lock).
The end-goal is to remove the indio_dev->mlock usage, and the simplest fix
would have been to just add another lock, which would not be a good idea on
the long-run.
Signed-off-by:
On 9/26/19 1:46 PM, Robin Murphy wrote:
> On 2019-09-26 11:17 am, Oleksandr Andrushchenko wrote:
>>
>> On 9/26/19 12:49 PM, Julien Grall wrote:
>>> Hi Rob,
>>>
>>>
>>> On 9/25/19 10:50 PM, Rob Herring wrote:
As the comment says, this isn't a DT based device. of_dma_configure()
is going
On Wed, Sep 25, 2019 at 09:32:35PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> We already had evsel_fprintf.c, add its counterpart, so that we can
> reduce evsel.h a bit more.
>
> We needed a new perf_event_attr_fprintf.c file so as to have a separate
> object to
From: Colin Ian King
The return statement is indented incorrectly, add in a missing
tab and remove an extraneous space after the return
Signed-off-by: Colin Ian King
---
drivers/nfc/st95hf/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nfc/st95hf/core.c
On 25/09/19 23:37, Sebastian Andrzej Siewior wrote:
> I was surprised to see that the guest reported `fxsave_leak' while the
> host did not. After digging deeper I noticed that the bits are simply
> masked out during enumeration.
> The XSAVEERPTR feature is actually a bug fix on AMD which means
Hi!
> diff --git a/Documentation/leds/leds-class-multicolor.rst
> b/Documentation/leds/leds-class-multicolor.rst
> new file mode 100644
> index ..87a1588d7619
> --- /dev/null
> +++ b/Documentation/leds/leds-class-multicolor.rst
> @@ -0,0 +1,96 @@
>
On 9/25/19 15:26, Marek Szyprowski wrote:
> From: Maciej Falkowski
>
> Convert Samsung I2S controller to newer dt-schema format.
>
> Signed-off-by: Maciej Falkowski
> Signed-off-by: Marek Szyprowski
> ---
Thanks Maciej, it looks good to me, I just think it might make sense
to improve the
On Thu, 2019-09-26 at 11:10 +0300, Dan Carpenter wrote:
> [External]
>
> The "t" variable is unsigned so it can't be less than zero. We really
> are just trying to prevent divide by zero bugs so just checking against
> zero is sufficient.
>
> Signed-off-by: Dan Carpenter
> ---
>
On Thu, Sep 26, 2019 at 03:58:36PM +0800, Yunfeng Ye wrote:
> On 2019/9/25 23:20, Alexander Duyck wrote:
> > On Wed, 2019-09-25 at 20:52 +0800, Yunfeng Ye wrote:
> > It probably wouldn't hurt to update the patch description to mention that
> > async_schedule_node_domain does the allocation outside
On 9/26/19 9:32 AM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 07:03:52AM +0100, Vincenzo Frascino wrote:
>> diff --git a/arch/arm64/include/asm/memory.h
>> b/arch/arm64/include/asm/memory.h
>> index b61b50bf68b1..b1c8c43234c5 100644
>> --- a/arch/arm64/include/asm/memory.h
>> +++
From: Maciej Falkowski
Document clocks macros with their description
from 'Documentation/devicetree/bindings/sound/samsung-i2s.txt'
Signed-off-by: Maciej Falkowski
Signed-off-by: Marek Szyprowski
---
v2:
- Added proper commit message and description
- Moved comments to the right side
Best
On 9/26/19 11:56 AM, Vincenzo Frascino wrote:
> On 9/26/19 9:06 AM, Catalin Marinas wrote:
>> On Thu, Sep 26, 2019 at 07:03:50AM +0100, Vincenzo Frascino wrote:
>>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>>> index 37c610963eee..afe8c948b493 100644
>>> --- a/arch/arm64/Kconfig
>>>
On 9/26/19 9:30 AM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 07:03:51AM +0100, Vincenzo Frascino wrote:
>> diff --git a/arch/arm64/include/asm/vdso/compat_barrier.h
>> b/arch/arm64/include/asm/vdso/compat_barrier.h
>> index fb60a88b5ed4..3fd8fd6d8fc2 100644
>> ---
Hello Pasi,
Unfortunately, I am not able to continue the work on the Xen patches in
the foreseeable future.
For what it's worth: the xen-pciback workaround from this thread solves
my current issue as confirmed by internal testing.
-- Stanislav
(apologies for ugly footer injected below by
On 9/26/19 9:06 AM, Catalin Marinas wrote:
> On Thu, Sep 26, 2019 at 07:03:50AM +0100, Vincenzo Frascino wrote:
>> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
>> index 37c610963eee..afe8c948b493 100644
>> --- a/arch/arm64/Kconfig
>> +++ b/arch/arm64/Kconfig
>> @@ -110,7 +110,7 @@ config
The Spreadtrum SPI driver is the only user of the `word_delay` field in
the `spi_transfer` struct.
This change converts the field to use the `spi_delay` struct. This also
enforces the users to specify the delay unit to be `SPI_DELAY_UNIT_SCK`.
Signed-off-by: Alexandru Ardelean
---
There are plenty of delays that have been introduced in SPI core. Most of
them are in micro-seconds, some need to be in nano-seconds, and some in
clock-cycles.
For some of these delays (related to transfers & CS timing) it may make
sense to have a `spi_delay` struct that abstracts these a bit.
The `word_delay` field had it's type changed to `struct spi_delay`.
This allows users to specify nano-second or clock-cycle delays (if needed).
Converting to use `word_delay` is straightforward: it's just assigning the
value to `word_delay.value` and hard-coding the `word_delay.unit` to
The driver errors out if `delay_usecs` is non-zero. This error condition
should be extended to the new `delay` field, to account for when it will be
used.
Signed-off-by: Alexandru Ardelean
---
drivers/spi/spi-bcm63xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The WARN_ON macro prints a warning in syslog if `delay_usecs` is non-zero.
However, with the new intermediate `delay`, the warning should also be
printed.
Signed-off-by: Alexandru Ardelean
---
drivers/spi/spi-falcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The AXI SPI engine driver uses the `delay_usecs` field from `spi_transfer`
to configure delays, which the controller will execute.
This change extends the logic to also include the `delay` value, in case it
is used (instead if `delay_usecs`).
Signed-off-by: Alexandru Ardelean
---
The way the max delay is computed for this controller, it looks like it is
searching for the max delay from an SPI message a using that.
No idea if this is valid. But this change should support both `delay_usecs`
and the new `delay` data which is of `spi_delay` type.
Signed-off-by: Alexandru
The `delay` field has type `struct spi_delay`.
This allows users to specify nano-second or clock-cycle delays (if needed).
Converting to use `delay` is straightforward: it's just assigning the
value to `delay.value` and hard-coding the `delay.unit` to
`SPI_DELAY_UNIT_USECS`.
This keeps the uapi
Hi Kevin,
On Thu, 26 Sep 2019 at 03:34, Kevin Hilman wrote:
>
> Anand Moon writes:
>
> > Some time ago I had tired to enable usb bus 1 for Odroid C2/C1
> > but it's look like some more work is needed to u-boot and
> > usb_phy driver to initialize this port.
> >
> > Below patches tries to
The `word_delay` field had it's type changed to `struct spi_delay`.
This allows users to specify nano-second or clock-cycle delays (if needed).
Converting to use `word_delay` is straightforward: it just uses the new
`spi_delay_exec()` routine, that handles the `unit` part.
Signed-off-by:
The initial version of `spi_set_cs_timing()` was implemented with
consideration only for clock-cycles as delay.
For cases like `CS setup` time, it's sometimes needed that micro-seconds
(or nano-seconds) are required, or sometimes even longer delays, for cases
where the device needs a little
This change replaces the use of the `delay_usecs` field with the new
`delay` field. The code/test still uses micro-seconds, but they are now
configured and used via the `struct spi_delay` format of the `delay` field.
Signed-off-by: Alexandru Ardelean
---
drivers/spi/spi-loopback-test.c | 12
This change implements CS control for setup, hold & inactive delays.
The `cs_setup` delay is completely new, and can help with cases where
asserting the CS, also brings the device out of power-sleep, where there
needs to be a longer (than usual), before transferring data.
The `cs_hold` time can
For many places in the spi drivers, using the new `spi_transfer_delay`
helper is straightforward.
It's just replacing:
```
if (t->delay_usecs)
udelay(t->delay_usecs);
```
with `spi_transfer_delay(t)` which handles both `delay_usecs` and the new
`delay` field.
This change replaces in all
This conversion to the spi_transfer_delay_exec() helper is not
straightforward, as it seems that when a delay is present, the controller
issues a command, and then a delay is followed.
This change adds support for the new `delay` field which is of type
`spi_delay` and keeps backwards
The tegra114 driver has a weird/separate `tegra_spi_transfer_delay()`
function that does 2 delays: one mdelay() and one udelay().
This was introduced via commit f4fade12d506e14867a2b0a5e2f7aaf227297d8b
("spi/tegra114: Correct support for cs_change").
There doesn't seem to be a mention in that
The change introduces the `delay` field to the `spi_transfer` struct as an
`struct spi_delay` type.
This intends to eventually replace `delay_usecs`.
But, since there are many users of `delay_usecs`, this needs some
intermediate work.
A helper called `spi_transfer_delay_exec()` is also added,
Initially, I started this patchset thinking: "we need a new delay for
something-something" (in case someone is curios, we needed a CS-hold-time
when CS is asserted, because the CS wakes a chip from sleep-mode).
Then I added the delay, and felt a bit dirty-inside about adding a new one
(just like
The `cs_change_delay` backwards compatibility value could be moved outside
of the switch statement.
The only reason to do it, is to make the next patches easier to diff.
Signed-off-by: Alexandru Ardelean
---
drivers/spi/spi.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
401 - 500 of 679 matches
Mail list logo
