* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
@ 2015-09-17 4:47 ` Kuninori Morimoto
2015-09-17 7:37 ` Simon Horman
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Kuninori Morimoto @ 2015-09-17 4:47 UTC (permalink / raw)
To: linux-sh
Hi Simon, again
> Kuninori Morimoto (18):
(snip)
> 8) arm64: renesas: r8a7795: add Renesas sound SRC support
I noticed this patch is not needed at this point.
I didn't send it this time. Please ignore it.
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
2015-09-17 4:47 ` Kuninori Morimoto
@ 2015-09-17 7:37 ` Simon Horman
2015-09-17 9:47 ` Kuninori Morimoto
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Simon Horman @ 2015-09-17 7:37 UTC (permalink / raw)
To: linux-sh
Hi Morimoto-san,
On Thu, Sep 17, 2015 at 04:19:09AM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> These are v2 of Salvator-X sound support patches.
>
> These are based on renesas-drivers-2015-09-15-v4.3-rc1
> and my previous PFC patch-set
> pinctrl: sh-pfc: r8a7795: add I2C pin support
> pinctrl: sh-pfc: r8a7795: add Audio clock pin support
> pinctrl: sh-pfc: r8a7795: add Audio SSI pin support
>
> These is including non SH-ARM patches which are
> posted to other ML, but still not yet merged.
>
> 1): posted to ML, not yet merged
> 2): posted to ML, not yet merged
> 3): posted to ML, not yet merged
> 4): not yet posted, since 3) is not merged yet
4) It is semi-posted now :^)
> 5) - 14): for Salvator-X
> 15) - 17): for Salvator-X
> 18): based on 2)
>
> 19) 20): posted by Wolfram
Do you have any thoughts the above patches going into topic branches?
It seems a bit messy but possible from my light analysis so far.
> Kuninori Morimoto (18):
> 1) dmaengine: OF DMAEngine API based on CONFIG_DMA_OF instead of CONFIG_OF
> 2) clk: add CS2000 Fractional-N driver
> 3) ASoC: add ak4613 support
> 4) ASoC: ak4613: add Digital Playback Volume support
> 5) arm64: renesas: tidyup MSTP9 reverse definition order
> 6) arm64: renesas: r8a7795: add I2C support
> 7) arm64: renesas: r8a7795: add PIO sound support
> 8) arm64: renesas: r8a7795: add Renesas sound SRC support
> 9) arm64: renesas: add AUDIO_DMAC support
> 10) arm64: renesas: r8a7795: add SSI DMA support
> 11) arm64: renesas: salvator-x: enable I2C
> 12) arm64: renesas: salvator-x: add PIO sound support
> 13) arm64: renesas: salvator-x: Sound DMA support on DTS
> 14) arm64: renesas: salvator-x: Sound DMA support via BUSIF on DTS
> 15) arm64: defconfig: Enable Renesas R-Car I2C Controller
> 16) arm64: defconfig: add Renesas sound and AK4613 support
> 17) arm64: defconfig: add Renesas R-Car DMAC driver support
> 18) arm64: defconfig: add CS2000 driver support
>
> Wolfram Sang (2):
> 19) i2c: rcar: add support for r8a7795 (R-Car H3)
> 20) i2c: sh_mobile: add support for r8a7795 (R-Car H3)
>
> Documentation/devicetree/bindings/clock/cs2000-cp.txt | 24 +++++
> Documentation/devicetree/bindings/i2c/i2c-rcar.txt | 1 +
> Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt | 1 +
> Documentation/devicetree/bindings/sound/ak4613.txt | 17 ++++
> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 102 ++++++++++++++++++++
> arch/arm64/boot/dts/renesas/r8a7795.dtsi | 306 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> arch/arm64/configs/defconfig | 10 ++
> drivers/clk/Kconfig | 6 ++
> drivers/clk/Makefile | 1 +
> drivers/clk/clk-cs2000-cp.c | 530 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> drivers/i2c/busses/i2c-rcar.c | 3 +
> drivers/i2c/busses/i2c-sh_mobile.c | 1 +
> include/dt-bindings/clock/r8a7795-clock.h | 49 ++++++++--
> include/linux/of_dma.h | 2 +-
> sound/soc/codecs/Kconfig | 5 +
> sound/soc/codecs/Makefile | 2 +
> sound/soc/codecs/ak4613.c | 497 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 17 files changed, 1548 insertions(+), 9 deletions(-)
>
>
> Best regards
> ---
> Kuninori Morimoto
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
2015-09-17 4:47 ` Kuninori Morimoto
2015-09-17 7:37 ` Simon Horman
@ 2015-09-17 9:47 ` Kuninori Morimoto
2015-09-17 23:25 ` Simon Horman
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Kuninori Morimoto @ 2015-09-17 9:47 UTC (permalink / raw)
To: linux-sh
Hi Simon
> > 5) - 14): for Salvator-X
> > 15) - 17): for Salvator-X
> > 18): based on 2)
> >
> > 19) 20): posted by Wolfram
>
> Do you have any thoughts the above patches going into topic branches?
> It seems a bit messy but possible from my light analysis so far.
what does it mean ?
What/Which is messy ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
` (2 preceding siblings ...)
2015-09-17 9:47 ` Kuninori Morimoto
@ 2015-09-17 23:25 ` Simon Horman
2015-09-17 23:43 ` Kuninori Morimoto
2015-09-18 0:08 ` Simon Horman
5 siblings, 0 replies; 7+ messages in thread
From: Simon Horman @ 2015-09-17 23:25 UTC (permalink / raw)
To: linux-sh
On Thu, Sep 17, 2015 at 09:47:41AM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > 5) - 14): for Salvator-X
> > > 15) - 17): for Salvator-X
> > > 18): based on 2)
> > >
> > > 19) 20): posted by Wolfram
> >
> > Do you have any thoughts the above patches going into topic branches?
> > It seems a bit messy but possible from my light analysis so far.
>
> what does it mean ?
> What/Which is messy ?
Sorry for my poor choice of words. I was not referring to the code
itself, rather that the patchset doesn't appear to map well
to a single topic branch.
What I see is something like this:
1) dmaengine core topic
2,3) ak4613 driver topic
5-18) i2c+sound integration topics
19,20) i2c driver topic
I think the above can be constructed if you think it is worthwhile.
There are of course other possibilities.
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
` (3 preceding siblings ...)
2015-09-17 23:25 ` Simon Horman
@ 2015-09-17 23:43 ` Kuninori Morimoto
2015-09-18 0:08 ` Simon Horman
5 siblings, 0 replies; 7+ messages in thread
From: Kuninori Morimoto @ 2015-09-17 23:43 UTC (permalink / raw)
To: linux-sh
Hi Simon
> > > Do you have any thoughts the above patches going into topic branches?
> > > It seems a bit messy but possible from my light analysis so far.
> >
> > what does it mean ?
> > What/Which is messy ?
>
> Sorry for my poor choice of words. I was not referring to the code
> itself, rather that the patchset doesn't appear to map well
> to a single topic branch.
>
> What I see is something like this:
>
> 1) dmaengine core topic
> 2,3) ak4613 driver topic
> 5-18) i2c+sound integration topics
> 19,20) i2c driver topic
>
> I think the above can be constructed if you think it is worthwhile.
> There are of course other possibilities.
Ahh, OK I see
I need to send v3 patch-set. Then, I will separate these for each topics
Does it clear for you ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support
2015-09-17 4:19 [PATCH 0/20 v2][RFC] arm64: Salvator-X sound support Kuninori Morimoto
` (4 preceding siblings ...)
2015-09-17 23:43 ` Kuninori Morimoto
@ 2015-09-18 0:08 ` Simon Horman
5 siblings, 0 replies; 7+ messages in thread
From: Simon Horman @ 2015-09-18 0:08 UTC (permalink / raw)
To: linux-sh
On Thu, Sep 17, 2015 at 11:43:48PM +0000, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > > > Do you have any thoughts the above patches going into topic branches?
> > > > It seems a bit messy but possible from my light analysis so far.
> > >
> > > what does it mean ?
> > > What/Which is messy ?
> >
> > Sorry for my poor choice of words. I was not referring to the code
> > itself, rather that the patchset doesn't appear to map well
> > to a single topic branch.
> >
> > What I see is something like this:
> >
> > 1) dmaengine core topic
> > 2,3) ak4613 driver topic
> > 5-18) i2c+sound integration topics
> > 19,20) i2c driver topic
> >
> > I think the above can be constructed if you think it is worthwhile.
> > There are of course other possibilities.
>
> Ahh, OK I see
> I need to send v3 patch-set. Then, I will separate these for each topics
> Does it clear for you ?
Thanks, I think that would help.
^ permalink raw reply [flat|nested] 7+ messages in thread