linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
	Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: reset: meson: add gxl internal dac reset
Date: Wed, 06 May 2020 17:04:57 +0200	[thread overview]
Message-ID: <1jv9l9f6jq.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <05e51534c3d6284f555fd262b666c94d12cbd010.camel@pengutronix.de>


On Wed 06 May 2020 at 16:54, Philipp Zabel <p.zabel@pengutronix.de> wrote:

> Hi Jerome,
>
> On Wed, 2020-05-06 at 15:50 +0200, Jerome Brunet wrote:
>> On Tue 14 Apr 2020 at 10:28, Jerome Brunet <jbrunet@baylibre.com> wrote:
>> 
>> > On Thu 23 Jan 2020 at 11:13, Philipp Zabel <p.zabel@pengutronix.de> wrote:
>> > 
>> > > On Wed, 2020-01-22 at 10:25 +0100, Jerome Brunet wrote:
>> > > > Add the reset line of the internal DAC found on the amlogic gxl SoC family
>> > > > 
>> > > > Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
>> > > > ---
>> > > >  include/dt-bindings/reset/amlogic,meson-gxbb-reset.h | 2 +-
>> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
>> > > > 
>> > > > diff --git a/include/dt-bindings/reset/amlogic,meson-gxbb-reset.h b/include/dt-bindings/reset/amlogic,meson-gxbb-reset.h
>> > > > index ea5058618863..883bfd3bcbad 100644
>> > > > --- a/include/dt-bindings/reset/amlogic,meson-gxbb-reset.h
>> > > > +++ b/include/dt-bindings/reset/amlogic,meson-gxbb-reset.h
>> > > > @@ -69,7 +69,7 @@
>> > > >  #define RESET_SYS_CPU_L2		58
>> > > >  #define RESET_SYS_CPU_P			59
>> > > >  #define RESET_SYS_CPU_MBIST		60
>> > > > -/*					61	*/
>> > > > +#define RESET_ACODEC			61
>> > > >  /*					62	*/
>> > > >  /*					63	*/
>> > > >  /*	RESET2					*/
>> > > 
>> > > Thank you, applied to reset/next.
>> > 
>> > Hi Philip,
>> > 
>> > It seems reset/next has not made it to v5.7-rc1
>> > 
>> > Would it be possible to provide an immutable branch with this change, or
>> > maybe let Kevin apply this change through the amlogic tree ?
>> > 
>> > It would allow us to progress on some DT changes during this new cycle.
>> > 
>> > Thanks
>> > Jerome
>> 
>> Hi Philip, how can we move forward on this ?
>
> Sorry for the delay, I have missed the last window. I've now created an
> immutable branch:
>
>   git://git.pengutronix.de/pza/linux.git reset/meson-gxl-dac

Thx !

>
> which I will be included in the next reset pull request.
>
> regards
> Philipp


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      reply	other threads:[~2020-05-06 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22  9:25 [PATCH] dt-bindings: reset: meson: add gxl internal dac reset Jerome Brunet
2020-01-23  9:51 ` Neil Armstrong
2020-01-23 10:13 ` Philipp Zabel
2020-04-14  8:28   ` Jerome Brunet
2020-05-06 13:50     ` Jerome Brunet
2020-05-06 14:54       ` Philipp Zabel
2020-05-06 15:04         ` Jerome Brunet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1jv9l9f6jq.fsf@starbuckisacylon.baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).