Re: [PATCH v4 2/4] spi: Split spi message into max_dma_len size chunks

2019-04-12 Thread Mark Brown
On Fri, Apr 12, 2019 at 12:54:48PM +0200, Lukas Wunner wrote: > On Fri, Apr 12, 2019 at 10:47:21AM +0100, Mark Brown wrote: > > I *think* we managed to fix all the architectures to at least stub out > > the DMA interfaces, it's such a pointless thing to have conditional - >

Re: [PATCH v4 2/4] spi: Split spi message into max_dma_len size chunks

2019-04-12 Thread Mark Brown
On Fri, Apr 12, 2019 at 12:03:35PM +0200, ker...@martin.sperl.org wrote: > > On 12.04.2019, at 11:47, Mark Brown wrote: > >> In a previous version of this I suggested to Meghana to put this in the > >> driver, but Mark wanted it in the core. > > If we want to do

Re: [PATCH 1/2] spi: Add spi_is_bpw_supported()

2019-04-12 Thread Mark Brown
On Fri, Apr 12, 2019 at 11:41:30AM +0200, Noralf Trønnes wrote: > This let SPI clients check if the controller supports a particular word > width. drivers/gpu/drm/tinydrm/mipi-dbi.c will use this to determine if > the controller supports 16-bit for RGB565 pixels. If it doesn't it will > swap the by

Re: [PATCH v4 2/4] spi: Split spi message into max_dma_len size chunks

2019-04-12 Thread Mark Brown
On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote: > +++ b/drivers/spi/spi.c > @@ -1299,6 +1299,11 @@ static void __spi_pump_messages(struct spi_controller > *ctlr, bool in_kthread) > > trace_spi_message_start(ctlr->cur_msg); > > + ret = spi_split_transfers_maxsize(ctlr

Re: [PATCH v4 2/4] spi: Split spi message into max_dma_len size chunks

2019-04-12 Thread Mark Brown
On Thu, Apr 11, 2019 at 11:02:26PM +0200, Noralf Trønnes wrote: > Den 11.04.2019 20.18, skrev Lukas Wunner: > > On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote: > >> @@ -1299,6 +1299,11 @@ static void __spi_pump_messages(struct > >> spi_controller *ctlr, bool in_kthread) > >>tr

Re: [RFC PATCH 1/2] ASoC: simple-card: add support for bclk_ratio

2019-02-27 Thread Mark Brown
On Tue, Feb 26, 2019 at 05:03:49PM +, Russell King - ARM Linux admin wrote: > On Tue, Feb 26, 2019 at 11:31:15AM -0500, Sven Van Asbroeck wrote: > > There is talk in the manual about "network mode", which could work by > > changing > > the LRCLK only at the first slot - thereby allowing clien

Re: [RFC PATCH 1/2] ASoC: simple-card: add support for bclk_ratio

2019-02-26 Thread Mark Brown
On Tue, Feb 26, 2019 at 11:31:15AM -0500, Sven Van Asbroeck wrote: > That's a very good point too. In light of this, I struggle to understand how > the ssl_ssi can specify this: > static struct snd_soc_dai_driver fsl_ssi_dai_template = { > .playback = { > .stream_name = "C

Re: [RFC PATCH 1/2] ASoC: simple-card: add support for bclk_ratio

2019-02-26 Thread Mark Brown
On Tue, Feb 26, 2019 at 03:45:19PM +, Russell King - ARM Linux admin wrote: > Adding more WS signals makes the bus deviate from the I2S standard, > thereby making it impossible to connect a set of standard DACs to > such a source, whereas adding more I2S data lines, you just connect > each DAC

Re: [RFC PATCH 1/2] ASoC: simple-card: add support for bclk_ratio

2019-02-26 Thread Mark Brown
On Tue, Feb 26, 2019 at 09:53:22AM -0500, Sven Van Asbroeck wrote: > On Tue, Feb 26, 2019 at 4:11 AM Russell King - ARM Linux admin > > If the signal continues toggling, what does it do for the inactive > > channel - is that just one BCLK period long or does it assume there > > is still the second

Re: next/master boot bisection: Oops in nouveau driver on jetson-tk1

2018-12-10 Thread Mark Brown
On Mon, Dec 10, 2018 at 05:26:22PM +0100, Thierry Reding wrote: > On Mon, Dec 10, 2018 at 02:25:59PM +0000, Mark Brown wrote: > > This has been broken for a considerable time now with no response from > > Ben - is there some other path we can use to get the fix merged? > I s

Re: next/master boot bisection: Oops in nouveau driver on jetson-tk1

2018-12-10 Thread Mark Brown
On Mon, Dec 10, 2018 at 10:00:08AM +, Guillaume Tucker wrote: > On 08/12/2018 00:08, Lyude Paul wrote: > > uh > > didn't we fix this weeks ago? with "drm/nouveau: tegra: Call > > nouveau_drm_device_init()" > > Yes here's the fix from Thierry: > > https://patchwork.freedesktop.or

Re: next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)

2018-11-29 Thread Mark Brown
On Thu, Nov 29, 2018 at 12:54:13PM +0100, Thierry Reding wrote: > This looks like the same issue that I was seeing a couple of weeks ago. > There's a fix for this here: > http://patchwork.ozlabs.org/patch/993812/ > Not sure if Ben's picked that up yet, though. It's certainly not visible i

Re: next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)

2018-11-29 Thread Mark Brown
On Thu, Nov 29, 2018 at 03:23:59AM -0800, kernelci.org bot wrote: Today's -next crashes on Jetson TK1 when the Nouveau module is loaded if it can't find firmware: [7.617291] nouveau 5700.gpu: Linked as a consumer to regulator.33 [7.624037] nouveau 5700.gpu: NVIDIA GK20A (0ea000a1)

Re: [RFC] drm/bridge/sii902x: Fix EDID readback

2018-11-01 Thread Mark Brown
On Wed, Oct 31, 2018 at 04:55:53PM +, Fabrizio Castro wrote: > Having the option of using "unlocked" flavours of reads and writes > is what we need here, but looking at drivers/base/regmap/regmap-i2c.c > I couldn't find anything suitable for my case, maybe Mark could advise > on this one? I am

Applied "spi: pic32-sqi: don't pass GFP_DMA32 to dma_alloc_coherent" to the spi tree

2018-10-17 Thread Mark Brown
decisions based on the coherent_dma_mask. Signed-off-by: Christoph Hellwig Signed-off-by: Mark Brown --- drivers/spi/spi-pic32-sqi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/spi/spi-pic32-sqi.c b/drivers/spi/spi-pic32-sqi.c index 62e6bf1f50b1..d7e4e18ec3df 10

Applied "ASoC: intel: don't pass GFP_DMA32 to dma_alloc_coherent" to the asoc tree

2018-10-17 Thread Mark Brown
decisions based on the coherent_dma_mask. Signed-off-by: Christoph Hellwig Reviewed-by: Takashi Iwai Signed-off-by: Mark Brown --- sound/soc/intel/common/sst-firmware.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/soc/intel/common/sst-firmware.c b/sound/soc/intel/

Re: next-20180911 build: 1 failures 15 warnings (next-20180911)

2018-09-12 Thread Mark Brown
On Wed, Sep 12, 2018 at 04:02:22PM +0200, Maxime Ripard wrote: > On Tue, Sep 11, 2018 at 10:18:01PM +0200, Daniel Vetter wrote: > > Patch seems to have been stuck on dri-devel. I smashed an r-b onto it > > so Maxime can apply. > It's done now. Thanks! signature.asc Description: PGP signature _

Re: next-20180911 build: 1 failures 15 warnings (next-20180911)

2018-09-11 Thread Mark Brown
On Tue, Sep 11, 2018 at 08:47:28PM +0100, Build bot for Mark Brown wrote: Today's -next fails to build an arm64 defconfig due to: > arm64-defconfig > ERROR: "sun8i_tcon_top_de_config" [drivers/gpu/drm/sun4i/sun4i-tcon.ko] > undefined! > ERROR: "sun8i_tco

Re: [PATCH] [RFC v2] Drop all 00-INDEX files from Documentation/

2018-09-04 Thread Mark Brown
On Tue, Sep 04, 2018 at 12:15:23AM +0200, Henrik Austad wrote: > This is a respin with a wider audience (all that get_maintainer returned) > and I know this spams a *lot* of people. Not sure what would be the correct > way, so my apologies for ruining your inbox. Acked-by: M

Boot failures in -next on Jetson TK1

2018-05-26 Thread Mark Brown
Currently -next is failing to boot on Jetson TK1. The problem looks to be the Nouveau driver, during initialization it reports an address decode error then starts printing error messages saying "nouveau 5700.gpu: fifo: SCHED_ERROR 20 []" over and over again. I've pasted the start of the error

Re: [PATCH v7 1/2] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

2018-04-09 Thread Mark Brown
with no regulator at all :) > I don't like the dummy regulator much, as it generates a dev_warn(), which > makes me believe that it's a hack rather than a proper solution. You might > want to ask Mark Brown for his opinion. The DT should describe the physical supplies the device

Re: [PATCH v2 01/10] regmap: mmio: Add function to attach a clock

2018-02-26 Thread Mark Brown
On Wed, Feb 21, 2018 at 10:20:25AM +0100, Maxime Ripard wrote: > From: Maxime Ripard > > regmap_init_mmio_clk allows to specify a clock that needs to be enabled > while accessing the registers. The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: Linux 4.16-rc1 (2018-0

Applied "regmap: mmio: Add function to attach a clock" to the regmap tree

2018-02-26 Thread Mark Brown
stored in another node. Let's add a function that allows to attach a clock that has already been retrieved to a regmap in order to fix this. Signed-off-by: Maxime Ripard Signed-off-by: Mark Brown --- drivers/base/regmap/regmap-mmio.c | 24 include/linux/reg

Re: [PATCH] drm/tinydrm: Remove chunk splitting in tinydrm_spi_transfer

2018-02-19 Thread Mark Brown
On Mon, Feb 19, 2018 at 11:47:23AM +, Meghana Madhyastha wrote: > -Remove chunk splitting in tinydrm_spi_transfer in tinydrm-helpers as The spi > core will split a buffer into max_dma_len chunks for the > spi controller driver to handle. > -Remove automatic byte swapping in tinydrm_spi_transf

Applied "spi: kconfig: Remove AVR32 dep. from SPI_ATMEL" to the spi tree

2018-02-12 Thread Mark Brown
emove support for AVR32 architecture"). Signed-off-by: Ulf Magnusson Signed-off-by: Mark Brown --- drivers/spi/Kconfig | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig index 603783976b81..6fb0347a24f2 100644 --- a/drivers/spi/Kco

Re: [PATCH v3 03/20] kconfig: Remove leftover references to AVR32 symbol

2018-02-06 Thread Mark Brown
can't tell if there's any dependencies, I'm guessing not but just in case Acked-by: Mark Brown signature.asc Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-11-28 Thread Mark Brown
On Tue, Nov 28, 2017 at 06:28:38PM +0100, Greg KH wrote: > On Tue, Nov 28, 2017 at 05:12:23PM +0000, Mark Brown wrote: > > I think it's reasonable to ask for userspace, I'm querying why it needs > > to specifically be Android. > Does anyone other than Android use thi

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-11-28 Thread Mark Brown
On Tue, Nov 28, 2017 at 06:08:22PM +0100, Greg KH wrote: > On Tue, Nov 28, 2017 at 04:26:20PM +0000, Mark Brown wrote: > > On Tue, Nov 28, 2017 at 02:32:17PM +0100, Greg KH wrote: > > > call you added? What did you do to test this out? Where are the AOSP > > > patc

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-11-28 Thread Mark Brown
On Tue, Nov 28, 2017 at 02:32:17PM +0100, Greg KH wrote: > Where is the documentation for the new sysfs files and the new ioctl Didn't see any sysfs files in there? > call you added? What did you do to test this out? Where are the AOSP > patches to use this? Happen to have a VTS test for it?

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-11-27 Thread Mark Brown
On Mon, Nov 27, 2017 at 05:12:23PM +0100, Daniel Vetter wrote: > commit model ftw, we have 400+ patches for 4.16 already merged and tested > and all ready, right when -rc1 gets tagged. Makes the merge window the > most relaxed time of all, because all the other maintainers are drowning > and wont

Applied "ASoC: AMD: Make the driver name consistent across files" to the asoc tree

2017-11-16 Thread Mark Brown
//chromium-review.googlesource.com/678278 Tested-by: Jason Clinton Reviewed-by: Jason Clinton Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd/Makefile | 4 ++-- sound/soc/amd/acp-pcm-dma.c | 6 -- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/sou

Applied "ASoC: amd: use do_div rather than 64 bit division to fix 32 bit builds" to the asoc tree

2017-11-08 Thread Mark Brown
Reviewed-on: https://chromium-review.googlesource.com/678919 Reviewed-by: Jason Clinton Reviewed-on: https://chromium-review.googlesource.com/681618 Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd/acp-pcm-dma.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) di

Re: [PATCH] ASoC: amd: fix report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 02:35:05PM -0500, Alex Deucher wrote: > On Wed, Nov 8, 2017 at 2:30 PM, Guenter Roeck wrote: > > On Wed, Nov 8, 2017 at 11:18 AM, Deucher, Alexander > >> > Is this different to "ASoC: amd: Report accurate hw_ptr during dma" > >> > which was applied at 16:07? > >> Yes, thi

Re: [PATCH] ASoC: amd: fix report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 11:13:50AM -0800, Guenter Roeck wrote: > On Wed, Nov 8, 2017 at 10:47 AM, Mark Brown wrote: > > Is this different to "ASoC: amd: Report accurate hw_ptr during dma" > > which was applied at 16:07? > I suspect we may be getting hit by chromeos-

Re: [PATCH] ASoC: amd: fix report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 01:40:32PM -0500, Alex Deucher wrote: > On Wed, Nov 8, 2017 at 1:22 PM, Mark Brown wrote: > > Like I said in reply to your other mail please don't resubmit already > > applied patches. The current tip of my topic/amd branch appears to be > > t

Applied "ASoC: amd: Make the driver name consistent across files" to the asoc tree

2017-11-08 Thread Mark Brown
ned-off-by: Akshu Agrawal Tested-by: Jason Clinton Reviewed-by: Jason Clinton Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd/Makefile | 4 ++-- sound/soc/amd/acp-pcm-dma.c | 6 -- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/sound/soc/amd/

Re: [PATCH 1/3] ASoC: AMD: Make the driver name consistent across files

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 06:12:34PM +, Deucher, Alexander wrote: > This didn't not appear to be in your tree yet and I never got any > confirmation it being > applied. Apologies. Ah, sorry - my bad. This was one that I tried to apply but which didn't apply. signature.asc Description: PGP

Re: [PATCH] ASoC: amd: fix report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 01:18:41PM -0500, Alex Deucher wrote: > From: Guenter Roeck > > ERROR: "__aeabi_uldivmod" [sound/soc/amd/snd-soc-acp-pcm.ko] undefined! > > 64-bit divides require special operations to avoid build errors on 32-bit > systems. Like I said in reply to your other mail please

Re: [PATCH v2 2/3] ASoC: rt5645: Wait for 400msec before concluding on value of RT5645_VENDOR_ID2

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 12:24:03PM -0500, Alex Deucher wrote: > regmap_read(regmap, RT5645_VENDOR_ID2, &val); > > + /* > + * Read after 400msec, as it is the interval required between > + * read and power On. > + */ > + msleep(TIME_TO_POWER_MS); > + regmap_read(r

Re: [PATCH 1/3] ASoC: AMD: Make the driver name consistent across files

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 12:24:02PM -0500, Alex Deucher wrote: > From: Akshu Agrawal > > This fixes the issue of driver not getting auto loaded with > MODULE_ALIAS. Please don't resubmit patches that have already been applied, you should submit patches against current code in the tree you're expe

Re: [PATCH 3/3] FIXUP: FROMLIST: ASoC: amd: Report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Wed, Nov 08, 2017 at 12:45:16PM -0500, Alex Deucher wrote: > On Wed, Nov 8, 2017 at 12:42 PM, Alex Deucher wrote: > > I'm not familiar with which are chromium specific (TEST, BUG, FIXUP, > > FROMLIST I guess?). The info seems useful to have in the bug, but I > > can respin if it's a big deal.

Applied "ASoC: amd: Report accurate hw_ptr during dma" to the asoc tree

2017-11-08 Thread Mark Brown
accordingly the hw pointer. TEST= modprobe snd-soc-acp-pcm.ko modprobe snd-soc-acp-rt5645.ko aplay Signed-off-by: Vijendar Mukunda Signed-off-by: Akshu Agrawal Tested-by: Akshu Agrawal Reviewed-by: Jason Clinton Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd/acp-pcm-dma.c

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

2017-11-08 Thread Mark Brown
On Tue, Nov 07, 2017 at 09:34:35PM +0530, Agrawal, Akshu wrote: > On 11/7/2017 5:07 PM, Mark Brown wrote: > > > > These two URLs are different, what was being reviewed here? What is > > > > Commit-Ready supposed to mean? > Same patch is reviewed, once on 4.4 ke

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

2017-11-07 Thread Mark Brown
On Tue, Nov 07, 2017 at 07:26:03PM +0530, Mukunda,Vijendar wrote: > Removing URL links and commit-ready description in v2. This doesn't really answer my question: > > These two URLs are different, what was being reviewed here? What is > > Commit-Ready supposed to mean? Please don't top post, re

Re: [PATCH 3/3] ASoC: rt5645: Wait for 400msec before concluding on value of RT5645_VENDOR_ID2

2017-11-06 Thread Mark Brown
On Fri, Nov 03, 2017 at 04:35:45PM -0400, Alex Deucher wrote: > Minimum time required between power On of codec and read > of RT5645_VENDOR_ID2 is 400msec. We should wait and attempt > before erroring out. So the description says we have to wait 400ms before attempting a read... > BUG=b:66978383

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

2017-11-06 Thread Mark Brown
On Fri, Nov 03, 2017 at 04:35:43PM -0400, Alex Deucher wrote: > Signed-off-by: Vijendar Mukunda > Signed-off-by: Akshu Agrawal > Reviewed-on: https://chromium-review.googlesource.com/659699 > Commit-Ready: Akshu Agrawal > Tested-by: Akshu Agrawal > Reviewed-by: Jason Clinton > Reviewed-on: ht

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-11-02 Thread Mark Brown
On Thu, Nov 02, 2017 at 11:44:07AM +0100, Greg KH wrote: > On Tue, Oct 31, 2017 at 07:11:53PM +0000, Mark Brown wrote: > > There was a discussion a while ago in the context of I2C/SPI MFDs > > which concluded that if you need a bus and it's going to be effectively > >

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

2017-10-31 Thread Mark Brown
On Tue, Oct 31, 2017 at 12:03:35PM -0700, Laura Abbott wrote: > I'm not a fan of the platform bus but I have mixed feelings about > creating a dedicated bus type. I guess if we really need a bus > type we can do it later? There was a discussion a while ago in the context of I2C/SPI MFDs which con

Re: linux-next: manual merge of the sound-asoc tree with the drm-misc tree

2017-10-18 Thread Mark Brown
On Wed, Oct 18, 2017 at 02:33:37PM +, Deucher, Alexander wrote: Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to. > Your conflict change affectively reverted 1e444864833

Re: linux-next: manual merge of the sound-asoc tree with the drm-misc tree

2017-10-18 Thread Mark Brown
On Wed, Oct 18, 2017 at 02:30:50PM +, Deucher, Alexander wrote: > The patch below effectively reverts 1e4448648333a. If you drop the patch > below, you should be fine. As I said in my followup mail I've dropped all these patches due to build failures, please resend both the pull request and

Re: linux-next: manual merge of the sound-asoc tree with the drm-misc tree

2017-10-18 Thread Mark Brown
On Wed, Oct 18, 2017 at 10:57:33AM +0100, Mark Brown wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is s

linux-next: manual merge of the sound-asoc tree with the drm-misc tree

2017-10-18 Thread Mark Brown
Hi all, Today's linux-next merge of the sound-asoc tree got a conflict in: drivers/gpu/drm/amd/include/amd_shared.h between commit: cfa289fd4986c ("drm/amdgpu: rename amdgpu_dpm_funcs to amd_pm_funcs") from the drm-misc tree and commit: 1e4448648333a ("drm/amdgpu Moving amdgpu asic type

linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

2017-10-18 Thread Mark Brown
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/i915_gem_evict.c between commit: 99b169d3c2052 ("drm/i915: Fix eviction when the GGTT is idle but full") from the drm-intel-fixes tree and commit: 9c1477e83e629 ("drm/i915/selftests: Exercise

Applied "ASoC: AMD: DMA driver changes for Stoney Platform" to the asoc tree

2017-10-17 Thread Mark Brown
ank 4 will be used for Capture scenario. Acked-by: Mark Brown Reviewed-by: Alex Deucher Signed-off-by: Vijendar Mukunda Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd/acp-pcm-dma.c | 87 + sound/soc/amd/acp.h |

Applied "drm/amdgpu Moving amdgpu asic types to a separate file" to the asoc tree

2017-10-17 Thread Mark Brown
The patch drm/amdgpu Moving amdgpu asic types to a separate file has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: AMD: Add machine driver for cz rt5650" to the asoc tree

2017-10-17 Thread Mark Brown
Deucher Signed-off-by: Akshu Agrawal Signed-off-by: Alex Deucher Signed-off-by: Dylan Reid Signed-off-by: Mark Brown --- sound/soc/amd/Kconfig | 7 ++ sound/soc/amd/Makefile | 2 + sound/soc/amd/acp-rt5645.c | 199 + 3 files changed, 208

Applied "ASoC: AMD: disabling memory gating in stoney platform" to the asoc tree

2017-10-17 Thread Mark Brown
SRAM Banks won't be turned off. By Default, SRAM Bank state set to ON. Added condition checks to skip SRAM Bank state set logic for Stoney platform. Acked-by: Mark Brown Reviewed-by: Alex Deucher Signed-off-by: Vijendar Mukunda Signed-off-by: Alex Deucher Signed-off-by: Mark Brown ---

Applied "ASoC: AMD: Audio buffer related changes for Stoney" to the asoc tree

2017-10-17 Thread Mark Brown
capture.Modified Max buffer size to have the correct mapping between System Memory and SRAM. Added snd_pcm_hardware structures for playback and capture for Stoney. Reviewed-by: Alex Deucher Signed-off-by: Vijendar Mukunda Signed-off-by: Alex Deucher Signed-off-by: Mark Brown --- sound/soc/amd

Re: linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

2017-10-17 Thread Mark Brown
On Tue, Oct 17, 2017 at 10:11:53AM +0200, Arnd Bergmann wrote: > This merge seems fine, but it seems there was another merge > against the akpm tree that introduced a build error by reintroducing > the spin_lock_irqsave() without restoring the local variable: > drivers/gpu/drm/i915/i915_gem.c: In

linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

2017-10-16 Thread Mark Brown
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/i915_gem.c between commit: b85577b72837e ("drm/i915: Order two completing nop_submit_request") from the drm-intel-fixes tree and commit: 5d031f4e1618b ("drm/i915: Stop asserting on set-wedged

linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

2017-10-12 Thread Mark Brown
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/i915_gem.c between commit: b85577b72837ee ("drm/i915: Order two completing nop_submit_request") from the drm-intel-fixes tree and commit: af7a8ffad9c58d ("drm/i915: Use rcu instead of stop_mac

linux-next: manual merge of the drm-intel tree with the drm-intel-fixes tree

2017-10-12 Thread Mark Brown
Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/intel_display.c between commit: 7b50f7b24cd6c ("rm/i915: Read timings from the correct transcoder in intel_crtc_mode_get()") from the drm-intel-fixes tree and commit: de330815677d8 ("drm/i9

Re: linux-next: build failure after merge of the drm-intel-fixes tree

2017-10-11 Thread Mark Brown
On Tue, Oct 10, 2017 at 08:03:00AM +0100, Mark Brown wrote: > Hi all, > > After merging the drm-misc-fixes tree, today's linux-next build > (x86_allmodconfig) failed like this: > > CC [M] drivers/gpu/drm/i915/i915_gem_evict.o > drivers/gpu/drm/i915/i91

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

2017-10-10 Thread Mark Brown
On Mon, Oct 09, 2017 at 05:10:37PM -0700, Laura Abbott wrote: > On 10/09/2017 03:08 PM, Mark Brown wrote: > > On Mon, Oct 09, 2017 at 02:25:47PM -0700, Laura Abbott wrote: > >> Anyway, to move this forward I think we need to see a proof of concept > >> of using s

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

2017-10-09 Thread Mark Brown
On Mon, Oct 09, 2017 at 02:25:47PM -0700, Laura Abbott wrote: > Anyway, to move this forward I think we need to see a proof of concept > of using selinux to protect access to specific heaps. Aren't Unix permissions enough with separate files or am I misunderstanding what you're looking to see a p

Re: [alsa-devel] [PATCH 0/6 v4] Add ASoC support for AMD Stoney APUs

2017-10-04 Thread Mark Brown
On Thu, Sep 28, 2017 at 07:21:07PM +, Deucher, Alexander wrote: > > Any updates with the pull requests? > Sorry travelling last week and swamped this week. I'm going to try > and get it done tomorrow, otherwise, probably the week after. No worries, it's only -rc3 so we've got 3-4 weeks. s

Applied "regmap: add iopoll-like polling macro for regmap_field" to the regmap tree

2017-10-04 Thread Mark Brown
regmap_field_read_poll_timeout that works similar to the readx_poll_timeout defined in linux/iopoll.h, except that this can also return the error value returned by a failed regmap_field_read. Signed-off-by: Chen-Yu Tsai Signed-off-by: Mark Brown --- include/linux/regmap.h | 39 +++ 1

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

2017-10-04 Thread Mark Brown
On Tue, Oct 03, 2017 at 04:08:30PM -0700, Sandeep Patil wrote: > It is entirely possible and easy in android/ueventd to create those nodes > under "/dev/ion/". (assuming the heap 'subsystem' for these new devices will > point to 'ion'). The reason I didn't say /dev/ion/foo initially is that if p

Re: [PATCH v3 09/14] regmap: add iopoll-like polling macro for regmap_field

2017-10-04 Thread Mark Brown
On Fri, Sep 29, 2017 at 04:23:01PM +0800, Chen-Yu Tsai wrote: > This patch adds a macro regmap_field_read_poll_timeout that works > similar to the readx_poll_timeout defined in linux/iopoll.h, except > that this can also return the error value returned by a failed > regmap_field_read. The followin

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

2017-10-03 Thread Mark Brown
On Mon, Oct 02, 2017 at 11:07:48AM -0700, Laura Abbott wrote: > Thinking about this a bit more, I'm not 100% sure if this > will allow the security rules we want. Heap ids are assigned > dynamically and therefore so will the /dev/ionX designation. > From my understanding, security rules like selin

Re: [alsa-devel] [PATCH 0/6 v4] Add ASoC support for AMD Stoney APUs

2017-09-28 Thread Mark Brown
On Thu, Sep 14, 2017 at 10:42:28AM -0700, Mark Brown wrote: > On Wed, Sep 13, 2017 at 02:49:08PM -0400, Alex Deucher wrote: > > I'm not quite sure what you mean by the cross merge. There are no > > dependencies outside this patch set. The only patches that touch drm >

Re: [PATCH v4 2/2] staging: ion: create one device entry per heap

2017-09-26 Thread Mark Brown
On Tue, Sep 26, 2017 at 02:07:05PM +0200, Benjamin Gaignard wrote: > version 4: > - add a configuration flag to switch between legacy Ion misc device > and one device per heap version. Should this be a switch or should it just be enabling and disabling the legacy device with the per heap ones a

Re: [PATCH 0/6 v4] Add ASoC support for AMD Stoney APUs

2017-09-14 Thread Mark Brown
On Wed, Sep 13, 2017 at 02:49:08PM -0400, Alex Deucher wrote: > On Wed, Sep 13, 2017 at 2:12 PM, Mark Brown wrote: > > No, send me a pull request for the dependencies so we can do a cross > > merge. I want to make sure that when this gets reviewed it actually > > gets mer

Re: [PATCH 0/6 v4] Add ASoC support for AMD Stoney APUs

2017-09-13 Thread Mark Brown
On Wed, Sep 13, 2017 at 01:57:49PM -0400, Alex Deucher wrote: > I just need acks from audio on the remaining patches that touch audio > (1, 5, 6), and then I can send a pull request. No, send me a pull request for the dependencies so we can do a cross merge. I want to make sure that when this ge

Re: [PATCH 3/6 v3] ASoC: AMD: disabling memory gating in stoney platform

2017-08-31 Thread Mark Brown
or > Stoney platform. Acked-by: Mark Brown signature.asc Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PATCH 4/6 v2] ASoC: AMD: DMA driver changes for Stoney Platform

2017-08-31 Thread Mark Brown
On Fri, Aug 18, 2017 at 02:10:28PM -0400, Alex Deucher wrote: > From: Vijendar Mukunda > > Added DMA driver changes for Stoney platform. > Below are the key differences between Stoney and CZ Acked-by: Mark Brown signature.asc Description: P

Re: [PATCH 6/6 v3] ASoC: AMD: Add machine driver for cz rt5650

2017-08-31 Thread Mark Brown
On Fri, Aug 18, 2017 at 02:10:30PM -0400, Alex Deucher wrote: > +++ b/sound/soc/amd/Kconfig > @@ -2,3 +2,10 @@ config SND_SOC_AMD_ACP > tristate "AMD Audio Coprocessor support" > help >This option enables ACP DMA support on AMD platform. > +config SND_SOC_AMD_CZ_RT5645_MACH > +

Re: [PATCH 5/6 v3] ASoC: AMD: Audio buffer related changes for Stoney

2017-08-31 Thread Mark Brown
On Fri, Aug 18, 2017 at 02:10:29PM -0400, Alex Deucher wrote: > +#define ST_PLAYBACK_MAX_PERIOD_SIZE 8192 > +#define ST_CAPTURE_MAX_PERIOD_SIZE 8192 > +#define ST_MAX_BUFFER (ST_PLAYBACK_MAX_PERIOD_SIZE * > PLAYBACK_MAX_NUM_PERIODS) These defines will go wrong if the capture size is changed ind

Re: [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs

2017-08-31 Thread Mark Brown
On Wed, Aug 30, 2017 at 09:40:07PM +, Deucher, Alexander wrote: Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to. > I sent one patch in the v2 patch set that had already

Re: [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs

2017-08-30 Thread Mark Brown
On Wed, Aug 30, 2017 at 11:49:02AM -0700, Eric Anholt wrote: > Mark Brown writes: > > You need to get someone from the DRM side to pay attention to the second > > patch and you need to stop resending the first patch since as has been > > pointed out a few times now you nee

Re: [PATCH 0/6 v3] Add ASoC support for AMD Stoney APUs

2017-08-30 Thread Mark Brown
On Wed, Aug 30, 2017 at 09:33:35AM -0400, Alex Deucher wrote: > Any comments? Can this patch set go in? This is the second time I've > resent it since the addressing the initial feedback. Does anyone have > a preference on which tree? You need to get someone from the DRM side to pay attention

Re: [alsa-devel] [PATCH v2 2/2] drm/bridge: adv7511: restrict audio sample sizes

2017-08-01 Thread Mark Brown
On Tue, Aug 01, 2017 at 01:52:35PM +0100, Srinivas Kandagatla wrote: > On 01/08/17 13:28, Mark Brown wrote: > > > And it's a false indication that we are supporting 32bit samples. > > > Which am not very happy with. > > This is what the sample_bits field in the

Re: [PATCH 1/9] ASoC: dwc: Added a quirk DW_I2S_QUIRK_16BIT_IDX_OVERRIDE to dwc driver

2017-08-01 Thread Mark Brown
On Fri, Jul 28, 2017 at 03:31:26PM -0400, Alex Deucher wrote: > This patch is already applied to the audio tree, I'm just > including it here for completeness since it's not yet in > the drm tree. It's in mainline, please don't resubmit already applied patches. signature.asc Description: PGP si

Re: [alsa-devel] [PATCH v2 2/2] drm/bridge: adv7511: restrict audio sample sizes

2017-08-01 Thread Mark Brown
On Tue, Aug 01, 2017 at 01:24:03PM +0100, Srinivas Kandagatla wrote: > On 01/08/17 09:42, Arnaud Pouliquen wrote: > > On 08/01/2017 12:49 AM, srinivas.kandaga...@linaro.org wrote: > > I already used ADV7513 and i did not observe this limitation. > > I had a look to ADV7533 data-sheet. it should s

Re: [PATCH 01/18] regmap: mmio: Add function to attach a clock

2017-07-18 Thread Mark Brown
On Mon, Jul 17, 2017 at 11:01:07AM +0200, Maxime Ripard wrote: > On Thu, Jul 13, 2017 at 05:01:42PM +0100, Mark Brown wrote: > > > This might be problematic if the clock to enable is stored in another > > > node. > > > Let's add a function that allows to a

Re: [PATCH 01/18] regmap: mmio: Add function to attach a clock

2017-07-13 Thread Mark Brown
On Thu, Jul 13, 2017 at 04:12:56PM +0200, Maxime Ripard wrote: > This might be problematic if the clock to enable is stored in another node. > Let's add a function that allows to attach a clock that has already been > retrieved to a regmap in order to fix this. What is the use case for this? si

Applied "drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id" to the asoc tree

2017-06-30 Thread Mark Brown
-card-graph. Credit to Kuninori Morimoto who's patch to dw-hdmi-i2s-audio.c was what this was mostly copy-pasted from. Cc: Kuninori Morimoto Cc: Archit Taneja Cc: Mark Brown Cc: Rob Herring Cc: David Airlie Cc: Lars-Peter Clausen Cc: Linux-ALSA Cc: dri-devel@lists.freedesktop.org Signed-off

Re: [PATCH 4/8] ASoC: AMD: added condition checks for CZ specific code

2017-06-30 Thread Mark Brown
On Thu, Jun 29, 2017 at 12:58:02PM +, Mukunda, Vijendar wrote: > -Original Message- > From: Mark Brown [mailto:broo...@kernel.org] > Sent: Wednesday, June 28, 2017 11:36 PM > To: Alex Deucher Please fix your mail client to quote mails in a more normal fashion, this

Applied "drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC" to the asoc tree

2017-06-28 Thread Mark Brown
; port@1 { reg = <1>; /* HDMI OUT */ }; port@2 { reg = <2>; /* HDMI Sound IN */ }; }; Signed-off-by: Kuninori Morimoto Acked-by

Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id

2017-06-28 Thread Mark Brown
On Mon, Jun 26, 2017 at 09:31:34AM -0700, John Stultz wrote: > Hey Mark, > Just wanted to check on this to make sure it didn't slip by. I've > not seen it show up in -next yet. Please don't send content free pings and please allow a reasonable time for review. People get busy, go on holiday, a

Applied "ASoC: dwc: Added a quirk DW_I2S_QUIRK_16BIT_IDX_OVERRIDE to dwc driver" to the asoc tree

2017-06-28 Thread Mark Brown
DW_I2S_QUIRK_16BIT_IDX_OVERRIDE to Designware driver. This quirk will set idx value to 1. By setting this quirk, it will override supported format as 16 bit resolution and bus width as 2 Bytes. Reviewed-by: Alex Deucher Signed-off-by: Vijendar Mukunda Signed-off-by: Alex Deucher Signed-off-by: Mark

Re: [PATCH 4/8] ASoC: AMD: added condition checks for CZ specific code

2017-06-28 Thread Mark Brown
On Fri, Jun 23, 2017 at 12:35:02PM -0400, Alex Deucher wrote: > Reviewed-by: Alex Deucher > index dcbf997..e48ae5d 100644 > --- a/sound/soc/amd/acp-pcm-dma.c > +++ b/sound/soc/amd/acp-pcm-dma.c > @@ -34,6 +34,8 @@ > > #define MAX_BUFFER (PLAYBACK_MAX_PERIOD_SIZE * PLAYBACK_MAX_NUM_PERIODS) >

Re: [PATCH 3/8] drm/amd/amdgpu: Added a dwc quirk for Stoney platform

2017-06-28 Thread Mark Brown
On Fri, Jun 23, 2017 at 12:35:01PM -0400, Alex Deucher wrote: > + if (adev->asic_type == CHIP_STONEY) { > + i2s_pdata[1].quirks = DW_I2S_QUIRK_COMP_REG_OFFSET | > + DW_I2S_QUIRK_COMP_PARAM1 | > + DW_I2S_QUIRK_16BIT_IDX_OVERRIDE; > + } els

Re: [PATCH 1/8] drm/amd/amdgpu: Added asic_type as ACP DMA driver platform data

2017-06-28 Thread Mark Brown
On Fri, Jun 23, 2017 at 01:05:37PM -0400, Alex Deucher wrote: > On Fri, Jun 23, 2017 at 12:43 PM, Christian König > > Have the painkillers jellyfied my brain or are you setting a pointer in the > > amdgpu device structure to some variable on the stack? > > If it's just for initialization then tha

Re: [PATCH] drm: adv7511_audio: Add .get_dai_id callback to map port number to dai id

2017-06-13 Thread Mark Brown
On Tue, Jun 13, 2017 at 02:59:49PM -0700, John Stultz wrote: > ALSA SoC needs to know connected DAI ID for probing. Using > the new audio-card-graph approach, ports/endpoints are used > to describe how the links are connected. Unfortunately, since Unless someone objects in the next week or so I in

Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

2017-05-26 Thread Mark Brown
On Wed, May 24, 2017 at 11:34:46PM +, Kuninori Morimoto wrote: > > As far as I understand what's going on with the graph code this seems to > > make sense to me. How do we want to go about handling the patch? > This is comment to me ? or DRM maintainer ? > If to me, any case (pickup by Mark

Applied "ASoC: hdmi-codec: add .get_dai_id support" to the asoc tree

2017-05-24 Thread Mark Brown
problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. To solve this issue, this patch adds new .get_dai_id callback on hdmi_codec_ops Signed-off-by: Kuninori Morimoto Signed-off-by: Mark Brown --- include/sound/hdmi-codec.h

Applied "ASoC: hdmi-codec: remove multi detection support" to the asoc tree

2017-05-24 Thread Mark Brown
: ...) Signed-off-by: Kuninori Morimoto Signed-off-by: Mark Brown --- sound/soc/codecs/hdmi-codec.c | 88 ++- 1 file changed, 3 insertions(+), 85 deletions(-) diff --git a/sound/soc/codecs/hdmi-codec.c b/sound/soc/codecs/hdmi-codec.c index a3f15149afcf..8659b7

Applied "ASoC: simple-card-utils: support snd_soc_get_dai_id()" to the asoc tree

2017-05-24 Thread Mark Brown
handle Sound port (= port@2) as ID = 0 if .of_xlate_dai_id has its support. hdmi { port@0 { /* VIDEO */ }; port@1 { /* VIDEO */ }; port@2 { /* SOUND */ }; }; Signed-off-by: Kuninori Morimoto Signed-off-by: Mark Brown --- sound/soc

Applied "ASoC: add snd_soc_get_dai_id() function" to the asoc tree

2017-05-24 Thread Mark Brown
) as ID = 0 if .of_xlate_dai_id has its support. hdmi { port@0 { /* VIDEO */ }; port@1 { /* VIDEO */ }; port@2 { /* SOUND */ }; }; Signed-off-by: Kuninori Morimoto Signed-off-by: Mark Brown --- include/sound/soc.h | 3 +++ sound/soc

<    1   2   3   4   5   6   7   8   9   >