All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: davinci: mityomapl138: Enable I2C1 master
Date: Mon, 28 Sep 2020 08:51:02 +0200	[thread overview]
Message-ID: <87h7ri75t5.fsf@geanix.com> (raw)
In-Reply-To: <f9ea6545-38c3-0634-5510-83a1c51ce908@ti.com> (Sekhar Nori's message of "Thu, 24 Sep 2020 19:11:21 +0530")

Sekhar Nori <nsekhar@ti.com> writes:

> Hi Esben,
>
> On 31/08/20 5:33 PM, Esben Haabendal wrote:
>> The I2C1 master is available at the SOM connector, and as such should be
>> available for applications where SOM module is connected to a board with
>> I2C chips connected to it.
>> 
>> Signed-off-by: Esben Haabendal <esben@geanix.com>
>
> If you are actively using this hardware, can you instead convert this
> over to device-tree? I would prefer that than keep the board file upto date.

Hi

Yes, I could instead convert this entire board to device-tree.  But on
the short-term, I am afraid I won't have time to do that.  I hope we can
find a way to merge this rather small change for now.  It should not
cause any problems for the future work to move to device-tree.

Thanks,
Esben

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

  reply	other threads:[~2020-09-28  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 12:03 [PATCH 1/2] ARM: davinci: mityomapl138: Enable I2C1 master Esben Haabendal
2020-08-31 12:03 ` [PATCH 2/2] ARM: davinci: mityomapl138: Ensure pinmux setup of I2C pins Esben Haabendal
2020-09-24 13:41 ` [PATCH 1/2] ARM: davinci: mityomapl138: Enable I2C1 master Sekhar Nori
2020-09-28  6:51   ` Esben Haabendal [this message]
2020-09-28 17:48     ` Sekhar Nori

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=87h7ri75t5.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=nsekhar@ti.com \
    /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.