From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Linux-OMAP <linux-omap@vger.kernel.org>,
"Adam Ford-BE" <aford@beaconembedded.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Paul Walmsley" <paul@pwsan.com>,
"Russell King" <linux@armlinux.org.uk>,
devicetree <devicetree@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2
Date: Sat, 13 Jun 2020 08:50:46 -0700 [thread overview]
Message-ID: <20200613155046.GV37466@atomide.com> (raw)
In-Reply-To: <CAHCN7xJnBkihY0XwNw+7xj5qZhwz_Up-b_LEt3PY8aFWVYsnrQ@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200613 11:11]:
> Through trial and error, I think I have the right IRQ for OMAP3630 for
> the 2nd instance.
OK great.
> > > I assume the second engine uses different interrupts. I don't suppose
> > > anyone know what it should be?
> >
> > Sorry no idea, usually the secure accelerator documentation is just
> > left out it seems. My guess the values are the same as on omap3.
>
> Tony - Could you review the hwmod transition I did for the first
> engine to make sure I did it right?
Yeah that's about all there is to it :)
> If you think I did it right, I'll post my V2.
Yes please do.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
"Paul Walmsley" <paul@pwsan.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Adam Ford-BE" <aford@beaconembedded.com>,
"Russell King" <linux@armlinux.org.uk>,
"Rob Herring" <robh+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2
Date: Sat, 13 Jun 2020 08:50:46 -0700 [thread overview]
Message-ID: <20200613155046.GV37466@atomide.com> (raw)
In-Reply-To: <CAHCN7xJnBkihY0XwNw+7xj5qZhwz_Up-b_LEt3PY8aFWVYsnrQ@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200613 11:11]:
> Through trial and error, I think I have the right IRQ for OMAP3630 for
> the 2nd instance.
OK great.
> > > I assume the second engine uses different interrupts. I don't suppose
> > > anyone know what it should be?
> >
> > Sorry no idea, usually the secure accelerator documentation is just
> > left out it seems. My guess the values are the same as on omap3.
>
> Tony - Could you review the hwmod transition I did for the first
> engine to make sure I did it right?
Yeah that's about all there is to it :)
> If you think I did it right, I'll post my V2.
Yes please do.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-13 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 23:01 [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2 Adam Ford
2020-05-04 23:01 ` Adam Ford
2020-05-05 18:42 ` Tony Lindgren
2020-05-05 18:42 ` Tony Lindgren
2020-05-05 21:17 ` Adam Ford
2020-05-05 21:17 ` Adam Ford
2020-05-05 23:34 ` Tony Lindgren
2020-05-05 23:34 ` Tony Lindgren
2020-06-13 11:10 ` Adam Ford
2020-06-13 11:10 ` Adam Ford
2020-06-13 15:50 ` Tony Lindgren [this message]
2020-06-13 15:50 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2020-06-17 10:58 Adam Ford
2020-06-17 10:58 ` Adam Ford
2020-06-17 17:26 ` kernel test robot
2020-06-17 17:26 ` kernel test robot
2020-06-29 18:12 ` Tony Lindgren
2020-06-29 18:12 ` Tony Lindgren
2020-06-30 0:29 ` Rong Chen
2020-07-01 14:44 ` Tony Lindgren
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=20200613155046.GV37466@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=paul@pwsan.com \
--cc=robh+dt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.